Setting up NWNx as a windows service

Arcsylver · Post by **Arcsylver** » Wed Aug 04, 2004 5:54 pm

I need to know how to set up nwnx as a windows service so that the server client can be launched automatically on windows bootup every time even if the computer restarts due to a power outage etc.

When I try to use the sc command on the command line in windows server 2003 I get this error when I try to start the service

error:1053 the service did not respond to the start or control request in a timely fashion

Jeff · Post by **Jeff** » Wed Aug 04, 2004 8:15 pm

Just add a shortcut to NWNX to your start menu.

Arcsylver · Post by **Arcsylver** » Wed Aug 04, 2004 9:30 pm

I do that, unfortunately Windows Server 2003 is being a pain in the rear about letting me disable the login on startup so until the password is typed in the startup isnt processed. Thus the server doesnt load unless someone is physically here to type it in if the power goes out or something.

Was hoping to possibly set up something to auto launch somehow without the password being typed in since the services supposedly load prior to login.

Post by **Themicles** » Thu Aug 05, 2004 1:24 am

Suggest this feature for future versions of NWNX if someone picks up where Pap left off. I know someone wants to, but not sure if they are going to.

-Themicles

JollyOrc · Post by **JollyOrc** » Thu Aug 05, 2004 2:46 am

there are tools that let you run normal windows programs as system service.

Too lazy to do a google search right now, but they are out there.

TimeLord · Post by **TimeLord** » Thu Aug 05, 2004 8:50 am

Theres a program in the NT Resource kit called srvany.exe which is supposed to allow you to turn any .exe into a service.

Microsoft makes it difficult to download/support anything windows2000 so you may have a hard time finding the actual download. They would rather you buy Windows 2003 server. So do a search for svrany.exe on M$ site and you might get lucky.

The page here looks like its got an option or two, dont have time to evaluate this myself right now so let us know how it goes

http://www.nick.rozanski.com/software.htm

Maska · Post by **Maska** » Wed Aug 11, 2004 8:51 am

FireDaemon works quite well too...

Maska · Post by **Maska** » Wed Aug 11, 2004 8:51 am

FireDaemon works quite well too...

Post by **Silk** » Fri Aug 13, 2004 2:07 pm

FireDaemon

Post by **Themicles** » Sat Aug 28, 2004 10:31 am

I've now tried running NWNX as a service using FireDaemon. This does not work correctly, and I'm hoping someone can help me fix that.

If I start NWNX as a service with FireDaemon, I get the following errors:

* An error occured during OnCreate of odbc

in the NWNX.txt logfile.

AND

! Error while connecting to database: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

in the NWNX_ODBC.txt logfile.

This is not an issue with my setup of NWNX, MySQL or NWN directly, as it works JUST FINE if I launch it from my shortcut, instead of through FireDaemon.

Any help? Any suggestions? Would be really nice to have my server running without user login on the machine, AND be able to contact the database. Can't have the one without the other...

-Themicles

Rathaen · Post by **Rathaen** » Thu Jan 27, 2005 8:06 pm

What sort of DSN is your Neverwinter database? Make sure it's a machine-wide DSN. That could cause this problem, because if FireDaemon starts NWNX without you being logged in, any user-specific DSNs will be inaccessible. This is the same error message NWNX gives if no DSN exists.

Post by **Themicles** » Fri Jan 28, 2005 6:37 am

I have it working now.

A warning to multi-server worlds.
If you want to run NWNX as a service, you are going to have to give up the ability to access the server program to see who's online, and even properly shut it down.

Why?
Only way to run NWNX as a service and still have both NWNX and NWServer.exe show on the desktop is to use LocalSystem. But, if you do that, NWServer.exe cannot access a server vault on another computer on the network. LocalSystem is obviously not allowed network access.

Now to get around this, you must run the service as a user that does have network access. But, this means that it will be hidden and cannot interact with the desktop.

-Themicles

lafferty · Post by **lafferty** » Thu Feb 03, 2005 12:01 am

Just pointing to the obvious:

http://support.microsoft.com/kb/q137890/

and then in the service dialogue (Management console) activate "May interact with desktop"

Maybe that works better....