AGAIN: server registration timeout with DCOM

[almoes]

Hi all!

I have seen that this error appears in different places but still I don't get a solution.
I run a simple client/server apllication in VB6 and the DCOM is not working. This is the error I get in the event log of the server:

Source: DCOM
EventID: 10010
Description: The server <clsid> did not register with DCOM within the required timeout.

And this is the error on the event log of the client:

Source: DCOM
EventID: 10006
Description: DCOM got error &quot;Server execution failed &quot; from the computer MyServerName when attempting to activate the server: <clsid>

I checked all the DCOM settings and read through tones of microsoft papers on fixing bugs, but still dont get an answer. Any ideas?

Thanxs a lot!

 

[almoes]

Just find the solution for the running locally, and it works now locally. I discovered in the net that VB has a bug and doesn't support Myserver.exe -regserver, it has to be Myserver.exe /regserver !!!!!
Anyway, remotely still doesn't work, now for sure I know its DCOM, but again, what?

 

[Rick1972]

Are you now still getting any messages on the server machine (in the log I mean)?

And maybe this is a redundant question, but did you now also execute MyServer.exe /regserver on the server machine?

 

[almoes]

yes, I get the same messages in both logs as before.
And yes, I registered the Myserver.exe on the server.

 

[Rick1972]

I am sorry then, I would have to see for myself then...
But I cannot create the project right now (I think my boss would not like this very much doing that in his time).

It seems to me that somehow the DCOM configuration on your server computer has gotten messed up...

What if you tried to create a completely new project from scratch (new name, different interface etc.) and not listen to what thos microsoft dudes wrote you about configuring DCOM, but doing it all yourself:
Register the exe on both the client and the server machine, configure DCOM on the client to use your component remotely etc....

 

[almoes]

ok thats what I was trying to do now. Thanks a lot anyway!!

 

[notes4fr]

I just had a similar error message when I changed my server's domain. The task I was trying to start (MQ Series) was using a user account in startup.

I had to run dcomcnfg (dcom config) (did Start->Run - dcomcnfg), select the application, then properties and under the Identity tab, had to re-select the user name, and I entered the password again just to make sure everything was cool.

It started right up.

Hope this gives you something new to try!

 

[almoes]

Right! That was the key to it! The basic example I was trying works now. There were different things going wrong. One is the Identity tab, I had to give a user and password to run the object on the server, and the other problem is that the package wizard doesn't configure the path to the server exe properly. You can modify this in the registry. Ah! and dont use spaces in the folder path to the exe. It took a while to discover this. Hope it helps!