Logging StudioCOM 3.8

Version 3

    Verified Product Versions

    Wavelink Studio Com 3.7

    Logging for StudioCOM is turned on through command prompt.

     

    You will need to point to where the WLserver.exe is located.  This is usually located in the StudioCOM bin folder.

    Next you will use the below command to run wlserver.exe in debug mode:

     

    wlserver.exe -n -dx

     

    -n creates a new log and the x is a place holder for which level of debug you want to run.  (Debugging levels are described below)

    Hit enter.  You will now have a new log located in the LogFiles folder under StudioCOM running level 3 of debugging.

    Debug Level Descriptions

     

    The four debug modes of the Wavelink and their descriptions are as follows:

     

      • Level Zero: No logging. The Wavelink Server will not save events to either the system event log or the Server log file.

       

       

      • Level One: Application Status. Only “application starting” and “application stopping” messages will be saved to both the system event log and the Server log file.

       

       

      • Level Two: Hard Errors. All “hard” errors encountered, which prevent the Wavelink Server from executing, are saved to the Server log file. An example of a “hard” error is an invalid authorization code. The same information that is logged within the Level Two debug mode will also appear within the system application event log when using the Wavelink Server as a service in Windows NT/2000. Please see the Windows NT Online Help for more information on viewing the system event log.

       

       

      • Level Three: Warnings, Hard Errors. In addition to logging “hard” errors, Level Three will log any system warnings encountered by the Wavelink Server. A system warning is classified as any resource error that does not prevent the Wavelink Server from initially starting. Possible errors that can be logged in this mode range from failed connections between a mobile device and a Port Monitor to system memory limitations. The same information that is logged within the Level Three debug mode will also appear within the system application event log when using the Wavelink Server as a service in Windows NT/2000. Please see the Windows NT/2000 online help for more information on viewing the system event log.

       

       

      • Level Four: Messages, Warnings, Hard Errors. The most comprehensive of the four available debug modes, Level Four logs all of the information included within the previous three levels plus any general server status messages. For example, in this mode a successful mobile device connection or similar message will be logged to the Server log file. In addition to server messages, this debug mode will also log user application messages within individual wireless connection log files. Any startup application or spawned application messages, such as function executions for a single mobile device user, will appear within a connection log file.

       

      Your logs can be viewed with a standard text editor or with the Wavelink Studio Log Reader which can be found in the programs menu under All Programs>Wavelink Studio.

       

      To configure logging on a device please see this link:

       

      Studio Client Config