Errors displayed in Event viewer related to Event Logs, Source not found.

4 Years Ago


When an administrative user opens Windows Event Viewer, one or both of the following errors can be found, under Bizagi as a source:

  • The description for Event ID [Event_ID] from source [Source_Name] cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.”
  • Error The source was not found, but some or all event logs could not be searched. To create the source, you need permission to read all event logs to make sure that the new source name is unique. Inaccessible logs: Security.

Applies to

Bizagi All versions


The Event viewer displays the errors mentioned in the summary. Nevertheless, Bizagi is not affected in its normal behavior.


This error is launched when a Bizagi application tries to write a log message and the windows registry HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\Bizagi/[ProjectName] is not found or not accessible. 
This happens when the user account used to install Bizagi does not have enough privileges.


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
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.


Recall using a user account with enough rights and permissions to install Bizagi in order to avoid this issue.

Rate this Article:


Last Modified:4 Years Ago
Last Modified By: JorgeR
Level: Intermediate
Rated 4 stars based on 2 votes.
Article has been viewed 12.0K times.