You're right, Process Explorer says it is using my client's version of the DLLs.
The culprit entry in the registry is: HKCU\Software\Valve\Steam\ActiveProcess\SteamClientDll When I delete that entry from the registry (and reboot), my server comes up without the nasty dialogs. However, I noticed that if I start my Steam client, the entry returns to the registry. Is there a way for my server and client to peacefully coexist? Thanks! From: Fletcher Dunn <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [hlds] TF2 srcds Failed to load Steam Service Content-Type: text/plain; charset="us-ascii" This output: Failed to load Steam Service. ServiceStart: failed to start Is actually normal and not the problem. (I know, it's weird and confusing.) It looks like your server is using Steam DLL's from somewhere else on your computer, besides where you have installed on your server. Look for registry keys under HKCU\Software\Valve\Steam that might have a path, and delete the keys and/or the old directories. You can also use Process Explorer to figure out which DLL it is loading. - Fletch From: [email protected] [mailto: [email protected]] On Behalf Of quigonjoe Sent: Wednesday, May 16, 2012 6:48 PM To: [email protected] Subject: Re: [hlds] TF2 srcds Failed to load Steam Service I do have Steam installed on it. Tried to update client, it is up to date. Tried verify_all command line switch on hldsupdatetool. Still receiving the same messages.
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
