Monday 12 August 2013

What LOG files does Syspro create?

Diagnosing errors can be tricky; a log file can be invaluable. Here are some log files that Syspro updates.

Log file
Description
BASE/mfdebug.log
This file gets written to when you crash Syspro; you can crash Syspro by creating a custom with a .Net User Control that throws an unhandled exception.
BASE/SRSQRT.TXT
If you create an empty file, BASE/SRSQRT.DEBUG, file, then as soon as SRS or VBScriptiong with CALLBO is used, this log file will be written to.
BASE/log.txt
If you call SYSPRO.EXE, IMPACT.EXE, IMPCSC.EXE or IMPAUT.EXE with the /log parameter, then this file will be created. It will record each time the client/server communications dialog tries to connect to the server.
BASE/settings/<operator>_RTS_ERROR.TXT
Created when there is a runtime error.
%Temp%/SYSPROCOMMLOG_*.txt
Syspro Communications Service will log files in your Temp directory (e.g. C:\Users\You\Local Settings\Temp) if you have the DetailedLog setting set to true in your Syspro Communications Service's config file, e.g. <add key="DetailedLog" value="true" /> in C:\Syspro\Syspro WCF Services\SYSPROWCFHostService.exe.config.
%Temp%/SYSPROActivityCallsLog.txt
If you create this file, the Syspro Workflow engine will log actions in it.
BASE/Settings/enetlog.dat
This log file identifies the Business Objects invoked. This file gets written to by e.Net. There are two ways to cause this file to be written to:

  1. Set the LogLevel parameter to ldDebug when you use e.Net to log into Syspro.
  2. In the Syspro GUI, go to Setup / Setup Options / General Setup / System Setup; go to the General tab and set Diagnostics to enet01.
BASE/Settings/enetlog.txt does not seem to be written to anymore, since about Syspro 6.1 SP1.

To view enetlog.dat, go to Home / Administration / Diagnostics / Diagnostics Manager (aka. IMPMON). Then go to the e.net Transaction Log tab and hit the Refresh button.

See this post for more details.
BASE/Settings/diag_xml
Xml inputs and outputs to Business Objects are logged here if the Diagnostics setting in System Setup / General is set to enetxx.
e.net Transaction Log
Go to Home / Administration / Diagnostics / Diagnostics Manager / e.net Transaction Log and hit the Refresh button.
AdmEventLog (database table)
Go to Home / Customzation / Event Management / Functions / View Log File.
AdmSignatureLog (database table)
Query this table directly in the database using SQL Server Management Studio or similar.
Job Logging
Go to Setup / Security / Job Logging. This listing includes program Logon and Logoff dates and times - quite useful.
Windows Event Log
Go to the Windows Event Log / Applications and Services Logs / SYSPROCOMMS and SYSPROSWS.
BASE\Settings\IMPUPD_Copy_Errors_*.txt
Errors encountered installing Syspro ports.
Electronic Signatures Audit Log
To view this, from the Syspro main menu, go to Program List / Administration / Electronic Signatures / eSignature Query.

Don't forget these invaluable tools as well:



Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)