Bizagi's traces are not created

5 Years Ago
Administrator
SCHEDULER AND UNDERLYING SERVICES

Summary

Bizagi traces are enabled but they are not created in the folder. This usually happens when there are not enough permissions in the project folder.

Applies to

Bizagi 10.x

Symptoms

The most common scenario for this problem is when a custom trace is included in an expression (or rule), using the tracing function: CHelper.trace(“Filename”, “text”). At run time the expression is executed and a trace was included at the beginning of the expression, so the trace should have been recorded. However a trace file is not created in the Trace folder (C:\BizAgi\Enterprise\Projects\PROJECT_NAME\Trace).

Cause

According to the security level in the application server, it is possible that the Application needs writing permissions on the Trace folder.

Solution

In order to configure the required permissions, follow these steps

1.     In the application server open the settings for the Bizagi application taking note of the Application Pool.

2.     In the Application Pools view, find out which is the Identity of the pool running the application.


3.     If the Identity is ApplicationPoolIdentity, change it to Network Service.


4.     Then go to the project folder (C:\BizAgi\Enterprise\Projects\PROJECT_NAME) and change its Security Properties to include the user Network Service with all the permissions (read, write, execute, etc.).

Rate this Article:

Details

Last Modified:5 Years Ago
Last Modified By: JorgeR
Type: ERROR
Level: Intermediate
Article not rated yet.
Article has been viewed 4.4K times.

Options