Slink-e / CDJ Discussion Archive #7
Re: Getting DCOM to work
Posted By: Jon Young <Slinke@J...> In Response To: Re: Getting DCOM to work (Barry Dacks)
In Response To: Re: Getting DCOM to work (Barry Dacks)
I have had varying success with this. I have it working between a W2K workstation and an NT4 workstation. The whole thing is incredibly flakey. I set up a W98 machine with it to run locally, it ran standalone for a while, then I put it back on the network and set the server to run on the NT4 workstation again. It worked instantly and was fine for about three days. I came home to find it had crashed and it hasn't worked between those two machines since. Noone used the network while I was out, let alone altered the security, protocol or DCOM settings, so I don't understand why it went from working to not working. Although potentially a great tool, this method of accessing the slinkeserver just isn't any good. It's not generally reliable. More people seem to have trouble with it than don't. The other issue with it is that CDJ is not multiuser, so if you want the screen savers and run cdj on all the PC's on the network, if any two of them save changes to the database, only one of their changes stick. Here is a list of com errors and their codes :- CO_E_BAD_SERVER_NAME 80004014 Appears with RPC_S_SERVER_UNAVAILABLE CO_E_CANT_REMOTE 80004013 Programmatic problem - Uncommon. CO_E_NOTINITIALIZED 800401f0 Programmatic problem - Uncommon. CO_E_SERVER_EXEC_FAILURE 80080005 Set the 'Remote connect' flag to Y and reboot. E_ACCESSDENIED 80070005 Security problem. W95/8 cant launch servers. E_FAIL 80004005 Something bad happened! E_NOINTERFACE 80004002 Try re-registering the server. E_OUTOFMEMORY 80000002 Default access needs the SYSTEM account. E_POINTER 80000005 Something bad happened! Corruption. ERROR_INVALID_PARAMETER 80070057 Programmatic problem - Uncommon. ERROR_SUCCESS 0 Woopee!!!! Oxymoron. REGDB_E_CLASSNOTREG 80040154 Re-register the server. RPC_S_SERVER_UNAVAILABLE 800706ba This is more common, anything could be wrong. Test connection with PING, check through all the setup instructions again. Make sure everything works locally on both machines. Make sure TCP/IP works. Bang head against wall.
I wish there was a general 'do this and itll work' sort of thing, but there isn't. When you have problems, they tend to persist. It takes effort to get this working on all machines all of the time.