Resolve SPS Issue: No Activity Logs, Logging in Synergize Process Server Stops
Use this article when the Synergize process designer has stopped logging (the Activity Log is blank and shows no log instances) and the database doesn't have any logs to browse. The ApplicationLog table in the deployment database may have hit the terminal logging value.
-
Confirm that the Process Designer has stopped showing logs in the window and this was not configured.
-
Typically, there is one location that can cause this to happen. The ApplicationLog table in the deployment database may have hit the terminal logging value.
To check this value:
-
Open the CONFIG table, and look at the ApplicationLog|ApplicationLogID row.
-
If the ConfigValue is 2,147,483,647 then that is why logging has stopped.
-
This value reflects the ID of the logging in the ApplicationLog table. This is the highest value that an INTEGER can reach.
-
-
At this point, setting the value back to zero (0) is the only way to get the SPS designer to display the logs again. Perform the remaining steps.
-
Truncate the ApplicationLog table to clear out the old logs, so that there isn't any duplicate ApplicationLogID values. Use "Truncate table ApplicationLog" sql statement to do so.
-
Set the value in the CONFIG table back to zero using this sql statement:
Update Config set ConfigValue = 0
where ConfigName = 'ApplicationLog|ApplicationLog_ID' -
If the Synergize Process Service is still running, logging will start immediately.
-
Clean up the Synergize Exception logs where all these errors have been written to in the time that logging hasn't been happening.
-
Browse to the directory
<Application Data Folder>\Microdea\Logs\ -
Delete the log file called Synergize_Management_Exception.log.
The size is most likely too large to open in text format anyway, so deleting the file is the only option.
-
There are many ways to turn off SPS logging with different advantages and disadvantages described in other KB articles.
