Emulator communications error

Emulator used to work, but now I no longer can communicate to it from VS2005. Reinstalling VS2005 didn't help.

Using DMA transport

When I try to connect to the emulated device I get the following error message:

To 'Windows Mobile 5.0 Pocket PC Emulator'

Connection failed. a specified communication resource (port) is already in use by another application.

Answer this question

Emulator communications error

Lourdes
This didn't change the problem at all. Same symptoms and behavior as before.
MartinBrill
Hello,

1. Can you please try clearing the save-state Go to Device Emulator Manager->Right Click->Clear Save state for the emulator for which you are obtaining this problem.

2. Are you obtaining this problem with each of the emulator or with a specific emulator

-Thanks,

Mohit
Carver42
Hello,

There looks to be a DMA connectivity problem between the VS2005 transport and Emulator in your case. The workaround is to use TCP transport for the connectivity for the time being.

We would like to investigate more on the issue. Can you please help us in identifying the root cause of the problem by sending us the log file You need to follow the following steps in order to generate the log

Step 1: Install the Trace Utility. http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/tracelog-o.asp. Tracelog.exe will be installed to "%ProgramFiles%\Resource Kit"

Step 2: Enable Tracing: run
```
tracelog.exe -start EmulatorLog -guid guid.txt -flag 5 -level 6 -f c:\trace.etl -ls
```
```
All going well, the first few lines of output should be: 
```
```
Logger Started...
Enabling trace to logger 3
Operation Status:    0L   The operation completed successfully.

Logger Name:      EmulatorLog
```
```
where guid.txt contains following lines
```
```
F836FFA2-9211-487E-9563-79426ED635A3
430BD66C-512B-47a9-BFF0-FEB6D4E361B5
1BDDA574-153F-4CF4-BC7E-D59ABD31214F
15d01673-8e69-427d-9e77-a776d9a0b2e8
49304836-A8F8-40ae-B02D-40828D2E9625
5014fc9f-df83-4091-a3b9-7fccea0b6939
594ca356-bfed-4fc6-bf5c-c64456cc2688
8D49EE18-C545-41d5-BB46-6F89B7F348D7
C1F08368-AD71-4f16-B990-D141D9001B42
2B6D1D05-E62A-498b-B2F8-7152A2159754
F6171749-7397-4aa5-A03A-13B5C8FCBE94
69C891A5-1CD8-48f5-BAF2-E6C22363D847
```
Step 3: Run the scenario - In your case try connect to device from VS.
Step 4: Disable Tracing: run
```
tracelog.exe -stop EmulatorLog
```
All going well, the first few lines of output should be:
```
Operation Status:    0L   The operation completed successfully.

Logger Name:      EmulatorLog
```
Step 5: Send c:\trace.etl to me (mohit.gogia[AT]microsoft.com) as an email attachment. The file should be small - no more than a few hundred kilobytes in length.

-Thanks,

Mohit
Lars Breiter
Based on the testing I have been doing I am guessing something besides VS2005 is holding the serial port. Anyone know of any way to determine what is holding the serial port I still can't find what application is doing so on my desktop machine.

This seems to be a real defect in the VS2005 as I am seeing all sorts of modest applications (like the little application on my laptop that I use to program my remote control) that block use of the VS2005 emulator.

The thing that is really confusing is that other applications can use the serial ports just fine.
Bard7
I have tried that. I uninstalled both things that reasonably could have had impact and those that wouldn't. No effect.

Does anyone know what ports are made available to the emulator
nd_ramesh
Hello,

Since you mentioned that it used to work but no longer works now, do you recall any events after which it stopped working like some crash, install of some other product etc.

-Thanks,

Mohit
SpencerInLa
Hello,

Thanks for providing us with the log file. It appears that somehow DMA transport got into incosistent state, the root cause of which we are not able to identify yet.

Can you please try the following. There are two saved-states

1. Local -> Inside c:\Documents and Settings\<username>\Application Data\Microsoft\Device Emulator\*.dess

2. Global -> Inside c:\Documents and Settings\All users\Application Data\Microsoft\Device Emulator\*.dess

Please rename all the save-state images, both local and global. This will cause the emulator to cold-boot.

-Thanks,

Mohit
Matthew Hoover - MSFT

Clearing the save state was one of the first things I tried. It had no effect.

Problem is with all emulators.
Mark Levison

Can you try deleting the local datastore,

Close all instances of VS, emulator and emuator manager.

Go to , SysDrive:\Documents and settings\<User>\Local Settings\Aplication Data\Corecon

Delete the 1.0 directory.

open VS.

Now try connecting to the emulator.
Emulator communications error

Answer this question