Solution
1.
Check if the registry has the respective subkey related to your
project and verify its correct configuration:
1.1. Open the Registry Editor. You may open it by using Windows + R and
typing regedit.
1.2. Go to the Application eventlog key located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
1.3. Locate the project’s subkey called Bizagi/[ProjectName]
1.4. Check if this subkey has the following configuration:
Name: EventMessageFile
Type:
REG_EXPAND_SZ
DATA:
For 64-bit versions: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\EventLogMessages.dll
For 32-bit versions: C:\Windows\Microsoft.NET\Framework\v4.0.30319\EventLogMessages.dll
If the subkey does not exist, create it using the configuration
mentioned above. Right click the Application
node and select New >
key. Then, type the corresponding name.
Once created, right click the newly created key and select the option New >
Expandable String Value to add the path for the DATA Value.
2. Check if the following keys are created as well using the same path
for DATA
and Type
mentioned in step 1.4:
DefaultSourceName key: BizAgi
Scheduler key: SchedulerServiceName/[ProjectName]
ServerOperationService Key: Bizagi
Standard Server Operations Service
If any of the keys mentioned before are not created, create them by
right clicking on the Application
node and selecting New >
key. Once created, right click the newly created key
and select the option New >
Expandable String Value to add the path for the DATA Value.

|