If you ever try to run ut3 as a service, depending on what muts and stuf you start up with it can take longer than 29 seconds to load and windows will kill it before it starts. I found a way to increase the service startup timeout and figured I would share:


When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds. If you do not adjust this time-out period, the Service Control Manager ends the process and the attached debugger while you are trying to debug. To adjust this time-out period, follow these steps:

   1. In Registry Editor, locate, and then right-click the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
   2. Point to New, and then click DWORD Value. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.
   3. Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.
   4. Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify. The Edit DWORD Value dialog box appears.
   5. In the Value data text box, type TimeoutPeriod, and then click OK

      Note TimeoutPeriod is a placeholder for the value of the time-out period (in milliseconds) that you want to set for the service. For example, if you want to set the time-out period to 24 hours (86400000 milliseconds), type 86400000.
   6. Restart the computer. You must restart the computer for Service Control Manager to apply this change.

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


unfortunately it didn't fix my problem :/

well what's your problem? and why run UT3 as a service? i thought UT3 ran as a process..

so that if it crashes or hangs for whatever reason, windows sees it, event logs it, and then restarts it and/or emails me

currently it looks like ut3 is crashing for some reason while loading as a service, but runs fine when executed via bat.

I could use firedaemon pro, but i dont want to license it

noob query, yes i said query, but you're sure all your drivers are up to date and everything?

can you load the editor?  because that uses UT3.exe also

and im sure you've reinstalled the game and such..so yeah..

..do you go Retail or through Steam?  if Retail, try downloading the steam version, if the steam version, try installing just retail..etc..

haha..licenses... you could always ask your internet peers to seed it to you