Software runs my life

Category: Microsoft Page 3 of 10

"COM 17 is used , please verify" in Cellular Emulator

When starting the Cellular Emulator included in the Windows Mobile 6 SDK I received an error “Com17 is used please verify”. This is a particularly annoying error because it completely prevents the program from even starting. Where is the setting to manually select a COM port?

Anyway I managed to stumble upon a solution on the MSDN forums and I am reposting it here so other people find it a bit more easily:

Disabling modem devices in Device Manager

Disabling modem devices in Device Manager

  1. Open Device Manager and disable any Bluetooth, Modem or other devices that use a COM port (see picture to the right)
  2. Open a new command prompt and execute the following commands:
    “C:\Program Files\Windows Mobile 6 SDK\Tools\Cellular Emulator\InstallXPVCom.exe” UnInstall
    “C:\Program Files\Windows Mobile 6 SDK\Tools\Cellular Emulator\InstallXPVCom.exe” Install
  3. Start the Cellular Emulator
  4. Re-enable any devices you disabled

The best part about this fix is that it is permanent. No need to disable the devices every time you start the Cellular Emulator, it remembers how to make everything work properly. Why couldn’t it do that in the first place?

FRS Error 13508 without 13509

error_13508Hand a few problems with this error on a new hosted domain controller that uses a VPN to connect back to the head office. Got some tips from Expert Exchange, but to summarise the various steps you should check are simple but effective (and as usual mostly DNS related):

  • Check there are no external DNS servers listed
  • Checked the localhost DNS server is not listed
  • Check that NETBIOS is only enabled over the internal NIC
  • Check that the other domain controllers FQDN’s are pingable
  • Check that the SRV records under the domain and _msdcs forward lookup zones include all your domain controllers (and only their internal IP addresses)
  • Manually trigger the domain controller replication connections through “Active Directory Sites and Services”, expand the server, right click “NTDS Settings” and do “All Tasks” and then “Check Replication Topology”. Make sure you click the Refresh button to see if all the replication links are listed.
  • Use netdiag -v and dcdiag -v to isolate any other problems
  • Keep restarting the Netlogon service 🙂

I really wish the DNS lookup that Active Directory did was a little more resilient (i.e. if the first DNS server lookup fails then use the secondary).

Live Mesh now Windows 7 Compatible

Live Mesh Beta LogoLive Mesh is getting a getting the Service Update that was promised before the holiday release blackout period today. The key bug fix that everyone is hanging out for is that it will now not kick Windows 7 into it’s non-Aero interface. This will soon include me, because I have a freshly burned copy of Windows 7 sitting on my desk ready to be installed tonight. I guess I will be completing the Windows Connect install survey tomorrow, fingers crossed they give out valid licence keys at the end of the beta program like they did for Vista.

One interesting point I noted was that the Live Mesh Blog no longer appears to be labelled “Beta” or “Tech Preview”. The version update appears to only be a minor one (0.9.3424.5 to 0.9.3424.14), however it looks as though some subtle steps towards a debut are occurring. Perhaps one of these will be matching Skydrive‘s 25 GB storage limit? I live in hope.

Page 3 of 10

Powered by WordPress & Theme by Anders Norén