Home
 

Enabling Cadacus WCF logs for analysis and troubleshooting

A Cadacus Windows Communication Foundation (Cadacus WCF) SQL troubleshooting log can be optionally activated at the Cadacus WCF service level.  Please note that the Cadacus WCF log is is a critical tool used for analysis and troubleshooting; however, it should only be activated in a production environment using extreme caution due to:

  1. the potential impact on production scanning speed, and
  2. the potential live server impact of a continuiously growing Cadacus WCF Service troubleshooting log size.

There are two types of SQL troubleshooting logs available:

  1. A global Cadacus WCF log - when activated, this log contains detailed technical entries (for troubleshooting purposes) for each handheld communicating to it on the server;  the steps to enable this global log are detailed below
  2. A local handheld device log - when activated, the data folder of the specific local handheld device will contain a table of logged calls specific to the local handheld device;  for details, go here for instructions on how to activate this local log

NOTE:  For deleting/removing old Cadacus WCF Log files, a SQL script is available on the SYSPRO server under Base\Scripts called EDIDropWCFLogTables.sql.

 

Enabling the global WCF SQL log

To activate the SQL log globally for all WCF activity, start the Windows Registry editor from the Start menu (Start-> Run-> regedit).

Navigate to the following registry key for a 32-bit server:

HKEY_LOCAL_MACHINE -> SOFTWARE-> Cadacus-> WCFService

As in this example:

Cadacus WCF Logging

Or, navigate to the following registry key for a 64-bit server:

HKEY_LOCAL_MACHINE -> SOFTWARE-> Wow6432Node->Cadacus-> WCFService

As in this example:

 

To activate the SQL log (recommended), right-click each registry name and select "Modify...", as follows:

    • SQLDatabase:  to avoid impacting a live production environment, it is important to enter a non-SYSPRO database here;  either create a new database for this log table or use some other non-SYSPRO database
    • SQLLog: set this value to "True" (not case senstive; any other value will be interpreted as "false"
    • SQLPassword: enter the database password
    • SQLServer: enter the SQL Server computer name
    • SQLUser:  enter the user name associated with the above password
      • NOTE:  the "SQLConnection" string can be entered, if known, as an alternative to the above settings
    • SQLTable:
      • For Cadacus WCF Service versions prior to February, 2014--create a SQL logging "Activity" table by downloading and running the Cadacus "WCFActivity" table script here (note: this table can be created in a separate database from SYSPRO or within the SYSPRO database)
      • For Cadacus WCF Service versions after February, 2014 (and newer), set the value of the desired table name for the "SQLTable" entry and the table will be created automatically, if it does not already exist.  If "CYMD" is added to the name of the table entry, the CYMD portion will be automatically replaced with today's date and a new table will be created every day. For example, entering "WCFActivityCYMD would create table "WCFActivity20140306" today and "WCFActivity20140307" tomorrow, and so on.  This keeps the size of the table smaller and more manageable.
    • Restart the Cadacus WCF Service
    • Enter any SYSPRO activity on a Cadacus Handheld device
    • Check the newly created SQL table to inspect the logging results, as in this example

 

Alternatively, to activate the Text log in the Registry:

    • TextLog: set this value to "True" (not case senstive; any other value will be interpreted as "false"
    • TextLogFile: optionally, a path and file name can be set for this file; note: the default path for this file is the same path in which the Cadacus WCF service resides; also, if a user-defined file name is created, it is recommended to include the "CYMD" text in the file name-- the logs will then be more manageable in size and will be separated by calendar year, month, and day
    • Restart the Cadacus WCF Service
    • Enter any SYSPRO activity
    • Check the newly created text file to inspect the logging results

 

To validate logging:

The Windows Application Event Log can be viewed from the Windows Administrative Tools to ensure logging is occurring as expected, as in this example:

 

To export a log for Technical Support:

In Microsoft SQL Server Management Studio, right-click the database containing the WCFActivity log --> Tasks --> Generate Scripts:

Select only the WCFActivity log for the day at issue, as in this example, and click "Next":

Click "Advanced" and scroll down to ensure "Types of data to script" is both "Schema and data", as in this example:

Click "OK", make note of the location the destination output SQL, click "Next" and "Finish".  The WCFActivity log should be available at the destination location for advanced troubleshooting with technical support. Please note it is recommended to compress (e.g., zip) the log prior to sharing with technical support

 

Why CADACUS SOLUTIONS FOR SYSPRO?

Since 1991, as developer of the standard EDI, Shipping, and Freight Calculator Solutions for SYSPRO, our products are fully integrated with SYSPRO and drive efficiencies for hundreds of users worldwide.

Why SYSPRO?

For 35 years, SYSPRO has had a single product focus resulting in an award-winning ERP system with a track record of success for over 14,000 customers worldwide.