Tuesday, June 12, 2007

VMWare, Vista and VPNs are vividly vulgar

Well, I just upgraded to a new work laptop. It came with vista business and so far I'm duly impressed with Vista. All development at work is done inside virtual machines, using VMWare workstation 6. So far so good. I connected vista to our domain, loaded workstation 6, and connected my external drive.

No probs so far. I load up my VMs, and I'm back in business! I spend the rest of the day working, and head home.

And home is where the troubles began. I have a wireless network at home. No prob. I get vista connected, and can surf like normal. However, when I go to start up my VMs to check on work stuff, I can't connect to the VPN inside the VM (which is Windows XP). Hmmm. So I connect to the VPN through Vista. No problem. So I startup the VM again, and try to connect to the network. No can do. It will get an IP from my dhcp server, but not make it anywhere over the VPN.

So I turn on the Microsoft Firewall client in Vista. Still can't get anywhere in the Virtual Machine.

I eventually was able to have the VPN connected in Vista, and the vpn connecting in the Virtual machine, but it wouldn't authenticate that "nested" vpn connection.

Trying just about every combination, I finally gave up and went upstairs. It was there I happened to notice my lone network port in the wall of my bedroom. Hmmmm. It couldn't be that simple. I grabbed a network cable, plugged it in the laptop, and now I'm connected to the VPN, inside the Virtual Machine, working once again.

Bummer that I can't use wireless for it, but someone else may have the answer to that.


Monday, June 4, 2007

Could not find resource assembly

I'm currently working on PDA app for our inventory program. I'm tweaking the program to point to a different webservice.

After deploying the app to the PDA, it started the connection to the webservice, when the following error popped up:

Could not find resource assembly

Hmmm. . . After some researching I found an msdn blog that mentioned that this error isn't an error that occurs in the apps resource assembly, but because the PDA does't have the resource assembly that contains the error codes that are used for display.

The blog contained a link to msdn to read through the issue, but alas, that pointed to a File Not Found error on the msdn. Oh well.

After searching, you need to copy the System_SR_enu.cab file to your PDA and install it.

Once I did that, the correct error message appeared and I moved on to debugging it. yeah!