DCOM Server exe Issue

Hi there,

We're having a few issues with the entries that are appearing in DCOM once our server exe is registered. It all works ok and our test app can call our API functions ok. It's called EMS-WASP API Server.exe and we use this context to install it.

clireg32.exe "C:\Program Files\EMS\Bin\EMS-WASP API Server.VBR" -s SERVERNAME -nologo -t “C:\Program Files\EMS\Bin\EMS-WASP API Server.TLB" -d

The problem is, when we look at DCOM Config in Component Services we are getting 2 entries for our server. One that has our configured name, and another that has the GUID as the name.

These are the 2 entries that appear in DCOM Config.

Name Application ID
{00050EBA-149A-11D3-8E11-00902721D56B} {00050EBA-149A-11D3-8E11-00902721D56B}
EMS-WASP API Server {00050EC1-149A-11D3-8E11-00902721D56B}

Our .vbr file is attached below. Would our problem be caused by something in here? This is the file that is putting the information into DCOM isn't it?

Attachment 90731

I should say here that we have added the 4th line in the .vbr file (the AppID line) as it was not there when the EMS-WASP API Server.exe was compiled. And when installed the API was only appearing in DCOM under its GUID, which made locating it difficult. It was one of our developers that has since left the company that suggested doing it this way, so we're not sure if that is right or not. If this AppID line is not included our API appears under DCOM Config as a big GUID not "EMS-WASP API Server" like we want.

What are we doing wrong?! Does anyone have any ideas?

Regards,
Pete.

Attached Files

• EMS-WASP API Server.VBR.txt‎ (20.5 KB)