If you need to generate logs for Act! with troublshooting purpose you’d need to enable trace logging for Act!
The following trace values appear in log files:
0 – off: means no errors
1 – error: only error message will appear
2 – warning: error and warning message will be displayed
3 – info: informational messages, warning messages, and error messages
4 – verbose: verbose messages, informational messages, warning messages, and error messages
You can isolate what action is occurring when you are eperiencing issues by turning on verbose logging in the ActSage.exe.config file. For this purpose, please perform the following steps:
- Open the ActSage.exe.config file located in the Act! installation folder with Microsoft Notepad or another text editor.
- Locate the system.diagnostics section. Then Click the Edit menu, and then click Find. After this the Find dialog box appears, in it please, type system.diagnostics in the Find what field, and then click Find Next
- Change the following add name values to 4: ACTUISwitch, ACTSecuritySwitch, ACTSyncSwitch, ACTSyncSetupSwitch, ACTDesignTimeSwitch, ACTExtendedSwitch, ACTReportingSwitch.
- Save the ActSage.exe.config file. Please make sure you save it with the same name, without renaming
- Try to launch Act!. If Act! fails to launch, use the Windows Tasks Manager to close Act!. End the task for ActSage.exe
- Double click the LogViewer.exe file in the Act! installation folder. The Act! Log Viewer dialog box appears.
- Check Act! Log Viewer for what might be causing this issue.
Note: This log file is stored in the following location: C:\Documents and Settings\<user_name>\Application Data\ACT\<version of Act!>
where <user_name> is your Windows username and <version of Act!> is your installed version of ACT! (for example: Act for Windows 9, ACT for Web):
ACTLOG.XML is the most recent Act! session, ACTLOG2.XML is the second most recent Act! session, ACTLOG3.XML is the third most recent Act! session. If needed, you can copy these files to send off for review.
How to enable Event Log tracking:
- Locate Act Search Service Event logtracking within the configuration file
- Remove comment tags for system.diagnostics section (remove comment tags shown in image)
- Save change
- Restart the service