Bizagi Standard Operation Service does not start by default

Last Year
JorgeR
SCHEDULER AND UNDERLYING SERVICES

Summary

Bizagi Standard Operation Service does not start by default and it must be started up manually.

Applies to

Bizagi All versions

Symptoms

When you start the server/machine where Bizagi is installed, the Bizagi Standard Operation Service does not start automatically and must be started manually.

Cause

By default, the Service Control Manager waits 30 seconds for an installed service to start up. However, some configurations, technical restrictions, or performance problems may cause a delay in the startup of the Bizagi Standard Operation Service, and it doesn’t start.

Solution

Edit the ServicesPipeTimeout key in the registry to increase the wait time.

1. Open the Registry editor (running the command regedit) and go down to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control and verify whether the ServicesPipeTimeout key exits.

If the key does not exist, right-click the Control node and click New > DWORD Value. Enter ServicesPipeTimeout as its name.


If the key exists or after its creation, right-click it and select Modify…
Select Decimal base and enter 180000 as value. This is equivalent to three minutes.


2. Restart Bizagi Standard Operation Service.

Rate this Article:

Details

Last Modified:Last Year
Last Modified By: JorgeR
Type: ERROR
Level: Beginner
Article not rated yet.
Article has been viewed 172 times.

Options