Select this diagnostic, save your changes, exit SYSPRO and rerun the Contact Management to Outlook Sync program. This creates logs in the %temp% folder on the client, with the following structure: CMSSync_OperatorCode_DateTime.txt.

The events window traces all application events that occur in the normal running of SYSPRO.

The output of the events window is saved in \settings\operator_dev02_debug.txt on the client machine.

This debug file can be sent to SYSPRO for analysis to help troubleshoot problems.

Each time a business object is executed, this diagnostic code causes the e.net Encorre.dll application extension to write to these files.

Typical information written to these files includes:

	These log files can grow rapidly in size.

The server side logging in a live environment is in a sub folder called SYSPROAnalytics in the system temporary folder of the machine on which the SYSPRO Analytics Server components are installed (for example C:\Windows\Temp).

The client side logging is written to a SYSPROAnalytics sub folder in the client side temp folder.

The file is generated in the user's temp folder and has the naming convention: SOI_OperatorCode DateTime.txt (e.g. SOI_ADMIN 20xx-xx-xx 08-17-24.txt).

A new file is created each time a new instance of the SOI addin is created.

Only a trace of the last SQL statement issued is output.

The generated file {oper}.sql is created in the \Base\Settings folder (where {oper} indicates the operator code). For example the ADMIN operator would create a file called: \Base\Settings\ADMIN.SQL.

This causes various programs that have been optimized for SQL to output a trace of the SQL statement being issued. This includes the SQL statements issued by the Report Writer.

This accumulates all SQL statements to the log file.

	This log file can grow rapidly in size.

The file is generated in the user's temp folder and has the naming convention: SRS_OperatorCode DateTime.txt (e.g. SRS_ADMIN 20xx-xx-xx 08-17-24.txt).

A new file is created each time a new instance of SRS is launched.

The log file ...\base\settings\{oper}.txt is generated on the application server - where {oper} is the operator code. For example the ADMIN operator would have a file called: ...\base\settings\ADMIN.TXT.

The client side logging is created in the client side temp folder and is called Comp_?_Oper_{oper}_SRSLog.txt where ? is the company code and {oper} is the operator code.

This activates the diagnostic tool for SYSPRO Reporting Services.

This incorporates all logging from printing and archiving and can drastically affect performance. It is equivalent of having all options SRSD01 through to SRSD06 enabled.

The generated file (OperatorName.txt) is output to the \Base\Settings folder of your SYSPRO installation.

The file contains an entry referencing a _T*.DAT temp file in your temporary folder as well as the generated XML. The following files are generated in the temporary folder:

Open the *.xml file to see if any errors were generated.

Files transferred include:

We recommend that you use this option when operators are not using the system as a large volume of message boxes may be invoked.

If this code is enabled and you receive an Error 153 message when you log into SYSPRO, it indicates that the message box program itself may not be available on the client workstation. You will need to edit the IMPACT.INI file and remove the sys02 value for the IMPCOM= entry.

If this code is enabled and you receive an Error 153 message when you log into SYSPRO, it indicates that the message box program itself may not be available on the client workstation. You will need to edit the IMPACT.INI file and remove the sys03 value for the IMPCOM= entry.

If you are designing a template and this diagnostics code is enabled, then another client-side log file (Comp_?_Oper_??????_WordDlog.txt) is created in the \Temp folder to trace the client-side program execution in design-mode. This can be useful when trying to locate an error during either the print or design phase.