Not Starting While Running as a Windows Service - System Administration - Cloud - Foundation 24.1 - Foundation 24.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Premier - Essential

Cloud System Administration

Platform
OnBase
Product
System Administration - Cloud
Release
Foundation 24.1
License
Standard
Premier
Essential

Issue: When running OnBase as a Windows Service, the OnBase Client fails to start if it takes longer than 30 seconds to launch. This issue is due to a Windows default setting that will terminate a Windows Service if it does not respond within an allotted time frame. A Service Control Manager Error will be generated in the Windows System Event Log with an ID of 7009 in the event of such a timeout.

Resolution: To resolve this issue, increase the timeout used by Windows to terminate a Windows Service that has not yet started. This is done in the Windows Registry, and requires a user with Administrator Privileges on the affected server or workstation.

CAUTION:

Modify the registry at your own risk. Incorrectly editing the Windows registry can cause serious problems that may require you to reinstall your operating system. Be sure to back up the registry before making any changes to it.

  1. Select Start > Run and enter regedit.
  2. Click OK.
  3. Browse to the key HKEY_CURRENT_USER\SYSTEM\CurrentControlSet\Control.
  4. If ServicesPipeTimeout exists, select it. If ServicesPipeTimeout does not exist, right-click and select New > DWORD Value. Enter ServicesPipeTimeout and press Enter.
  5. Right-click and select Modify.
  6. Select Decimal.
  7. In the Value data field, enter a time (in milliseconds) for the new Windows Services Timeout.
  8. Click OK.