Note: you should run RunUO.exe at least once from the
command line to create the owner account before running it as a service.
Otherwise, when you start it as a service, there will be no way to answer
the prompt regarding creating the owner account and the program will be
stuck at that stage. If you reinstall the Ultima Online client software
on the system again, you will need to create the owner account again by running
RunUO from a command
prompt.
After installing FireDaemon Pro use the FireDaemon Pro Service Manager to create a Windows service for RunUO.
Click on Service then select New.
You can put RunUO in the Short Name and Display Name fields. You can put whatever you like in the Description field.
For the Application to Run as a Service section, browse to the location of the RunUO.exe file and select it for the Executable . The Working Directory field will automatically be filled with the directory in which the RunUO.exe file is located.
Leave the Start-Up Mode set to "Automatic" to have the service start automatically when the system boots, which means that RunUO.exe will be run when the system boots.
If you wish the system to automatically try restarting RunUO if the service fails, then click on the Recovery tab then change the value for First failure from "Take No Action" to "Restart the Service" or "Restart the Computer". You can also change the values for "Second failure" and "Subsequent failures", if you wish. I set it to only try restarting the service after the first failure.
When you are finished configuring the service, click on OK.
You can then close the FireDaemon window.
If you check the Windows services, which you can do under Windows 8
by typing services.msc and hitting enter, you
will see the service running.
If you need to make changes to the service later, you can use the FireDaemon Pro Service Manager to edit the RunUO service parameters.
If you need to troubleshoot the RunUO service, RunUO stores a log for
each day in the \Logs\Commands directory beneath the RunUO
directory. For troubleshooting, you can also turn on logging of error
messages
through FireDaemon Pro by clicking on its Advanced tab
and, under Output Capture
, specifying a file for Capture
in File.
Or you can capture
all of the output that would normally go to the console by specifying a file
for Capture Stdout in File. I have any files specified for
troubleshooting created in RunUO's Logs directory.
I don't normally capture all output, i.e., Stdout, unless I'm troubleshooting a problem, since I don't want to log all of the periodic "World: Saving" messages that would normally appear. However, it can be useful at times, e.g., by turning on capturing of all output, I would see "Listener Failed: 0.0.0.0:2593 (In Use)"when an attempt was made to run the RunUO service, but it had already been started from the console rather than as a service.
Note: if the service is running when you change the logging, you will be informed "The service is not stopped. Do you wish to stop the service and proceed with the install?" The service will be stopped and restarted to make the logging change.
The company that provides FireDaemon Pro, FireDaemon Technologies Limited, also provides a free program FireDaemon Fusion, which provides a mechanism to control services run with FireDaemon Pro, or other Windows services, via a browser, which can give you the capability to restart the RunUO service from a remote system, if needed.
Created: