Skip to main content
Waters Employee Login
 
Waters

Where are the log files for NuGenesis 9 LMS and SDMS located? - WKB74663

  1. Last updated
  2. Save as PDF
Article number: 74663

ENVIRONMENT

  • NuGenesis 9

ANSWER

  • NuGenesis LMS
    • LMS Server log files:
      • IIS log file: WELNIIS.log, in C:\Temp\WatersLMS\WLMSServer.  Log file name, location, and logging level are controlled by Web.config in the <Default Web Site root folder>\WATERSLMS\. Can also edit the file by a shortcut on the desktop, or through  <Default Web Site root folder>\WATERSLMS\Bin\WatersELNConf200.exe
      • LMS Application server logs: server.log, scheduler.log, and manager.log, written to Drive:\WatersLMSServer\log. Log file location and logging level can be edited through the configurator shortcut on the desktop. The server.log file rolls over to a new log every day, while the manager and scheduler logs roll over when they hit 10 MB in size.
      • SDMS Interface: %ALLUSERSPROFILE%\Application Data\Waters\Sdms Result Extractor\Logging\RR2ELN.log
      • SampleShare: C:\inetpub\wwwroot\SampleShare\Logs. If SampleShare is installed to a non-default location (for example, if the Default Web Site's paths is changed), then the logs will be in \SampleShare\Logs below that non-default location. The logging level can be changed through the configurator program on the Start menu or by editing web.config in the \SampleShare folder.
      • Stability: the log for the NuGenesis Stability module interfaces (transfer of data from Stability to LMS and back) is managed by the LMS Job Manager and Scheduler services. Log messages written by the Stability interfaces are written to the manager.log file.
      • Document Creator Service: DocumentCreatorService.log and Substitution.log, written to C:\Users\ServiceAccountName\AppData\Roaming\Waters\NuGenesis LMS Document Creator\<version>. The log file location can be changed through the config tool, on the start menu: NuGenesis LMS Document Creator > LMS Document Service configuration. This program edits the files CreateDocumentService.exe.config and Substitution.config in the DCS installation folder. Note that the path for the log file as displayed in the DCS config tool may not be correct. It expands "%APPDATA%" to the AppData path for the logged-in user, whereas the service expands it to the AppData path for the Service account. Only if the logged-in user matches the service user will the path displayed in the DCS config tool be correct.
      • NuGenesis Connectors: The log file for the NuGenesis 8 Connectors service is in Drive:\Program Files (x86)\Waters Informatics\Connectors\Workflow\log.  Look for manager.log and manager.log.1 through manager.log.10
      • LMS-SAP Interface: the transfer of data between LMS and SAP is handled by background jobs in the LMS server.  The primary means of notification in the event of transfer errors is via the Inbox in LMS.  All users who are members of the "InterfaceAdmin" department in LMS will receive messages in their Inbox for SAP transfer errors.  The LMS Job Manager service will also write error messages to it's log file for any SAP job which results in an error
      • Request Report Mailer: Drive:\Program Files (x86)\Waters\NuGenesis LMS Request Report Mailer\Logs\RequestReportMailer.log.  Configuration file: log4net.config, location in the Report Mailer installation path.
    • LMS 9 Client log files:
      • LMS client: product.log, written to the %APPDATA%\Waters\NuGenesis LMS\version. The logging level and log file path is set by editing eln.exe.config in the NuGenesis LMS client installation directory.
      • Smart Builder: LMSSmartBuilder-<date>.log, written to %APPDATA%\Waters\NuGenesis LMS Smart Builder. A new log file is created every day. The log level is set via the Smart Builder configuration app, accessed via the Start menu (NuGenesis Smart Builder > Configure NuGenesis Smart Builder, which edits FormDesigner.dll.config in the Smart Builder install directory.
      • Smart Builder Plugins: <name_of_plugin>.txt, written to the LEME install folder\Plugins\Logs. Logging level and log file location are determined by <name_of_plugin>.dll.config in the Smart Builder Install Directory\Plugins. Example: Plugins\Waters.ELN.AC.SampleRepository.dll, Waters.ELN.AC.SampleRepository.dll.config, logs written to \Plugins\Logs\Waters.ELN.AC.SampleRepository.txt.
      • LMS-Empower interface:  ResultSender.log and SampleBrowser.log, written to C:\ProgramData\AppData\Waters\LMS Empower Interface\Log. The logging level and file paths are set in the configuration files EmpowerResultsSender.exe.config and EmpowerSampleBrowser.exe.config, both of which can be found in the installation folder, Drive:\Program Files (x86)\Waters\NuGenesis LMS Empower Interface.
      • Serial Device Support: Configurator-<date>.log, DiagTerminal-<Date>.log, Waters.SDS-<Date>.log, writtern to %APPDATA%\Waters\Waters Serial Device Support. Configured by three config files in the SDS installation directory: Configurator.exe.config, DiagTerminal.exe.config, SDS.exe.config
      • LMS SDK: ClientExtern.log, written to %APPDATA%\Waters\NuGenesis LMS SDK\<version>\ClientExtern.log. Configured by ELNTK_ClientExtern.config in the LMS SDK installation directory (example: C:\Program Files (x86)\Waters\NuGenesis LMS SDK). Written when applications make use of the LMS SDK, such as the Smart Builder Plugins.
      • Word Autoprint: AutomaticPrint-<Date>.log, written to %APPDATA%\Waters\NuGenesis LMS Word Automatic Print. Configured by AutomaticPrint.dll.config in the Word Automatic Print install dir
      • PowerPoint Autoprint: AutomaticPrint-<Date>.log, written to %APPDATA%\Waters\NuGenesis LMS PowerPoint Automatic Print. Configured by AutomaticPrint.dll.config in the Word Automatic Print install dir
  • NuGenesis SDMS
    • Most SDMS components do not create log files by default. They can write debug logs, which are controlled by a set of registry keys and activated when the software is restarted, but "normal" (non-debug) logs are not written by most SDMS components.
    • SDMS 9 File Capture log files
      • NOTE: The File capture log files will not be present on disk if the module is stopped. For historical log files, look in the SDMS_System_Activities project, Default View (or the relevant module-specific view). Click on the record links to download the log files. The files should open in Notepad.
      • Archive Agent: NGSDMSAAActivity.log found on disk in Drive:\Program Files (x86)\Waters\NGSDMS\AA. Old log files are stored in the SDMS_System_Activities project and deleted from disk.
      • Data Management: NGDM_*.LOG found on disk in Drive:\Program Files (x86)\Waters\NGSDMS\RPC. Old log files are stored in the SDMS_System_Activities project and deleted from disk.
      • Transport Engine: NGTEActivity.log Prior to FR1, the only log entries made by TE were in the *.NGD files (or *.mark_bad files) in the TE_TEMP folder. TE log files were not retained by the system. You would have to open the files in the TE_TEMP folder in order to see the log entries. Starting in FR1, a new log file, NG80TEActivity.log, is written to disk, in Drive:\Program Files (x86)\Waters\NGSDMS \RPC.
      • Offline Storage Manager: found on disk in Drive:\Program Files (x86)\NuGenesis 8.0\RPC. Old log files are stored in the SDMS_System_Activities project and deleted from disk.
      • Record Router: log files are stored in the application settings directory. By default this is found at Drive:\ProgramData\Waters\NuGenesis LMS SDMS Record Router\Logs. The location is configurable within the app post-install.
    • SDMS 9 Web Server log files:
      • The SDMS Web server stack uses several components: Microsoft IIS, Application Request Routing (ARR, an IIS plugin from Microsoft, installed along with the SDMS Web server software), Apache Tomcat, Java Runtime, and the NuGenesis VISION Server service. Of those components, only IIS and Tomcat create log files on a normal basis; the Java Runtime, ARR, and VISION Server do not create log files. The VISION Server is SDMS software, so it can create debug logs per the SDMS debug logging procedure (see the separate FAQ entry, link below, for details).
      • Microsoft IIS: by default, it's in C:\inetpub\logs\LogFiles. There are separate subdirectories for each WWW and FTP site. If the log files cannot be found on C: in the default location, open the Administrative Tools > IIS Manager window, click on the website, and double-click the "Logging" entry, to get the log file path.
      • Apache Tomcat: in Drive:\Program Files (x86)\Waters\apache-tomcat-9.0.8\logs. Tomcat retains old log files on disk. The most relevant log files are "catalina.DATE.log" and "localhost.DATE.log", where DATE is a date in the format YYYY-MM-DD
      • New Audit Trail (v9.1 and later): Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\AuditTrail\WebServer\logs\DATE.log, where DATE is in the format YYYY-MM-DD
      • New WebVision (v9.3 and later):
        • Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\Vision\SdmsIdentity\logs\DATE.log
        • Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\Vision\SdmsProjects\logs\DATE.log
        • Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\Vision\SdmsProjectServers\logs\DATE.log
        • (v9.3.1 and later) Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\Vision\SdmsSdkGateway\logs\DATE.log
        • Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\Vision\SdmsUserPreferences\logs\DATE.log
    • SDMS 9 Database Server log files:
      • NuGenesis 9 uses Oracle 12c or 19c as its database platform. Oracle organizes its log files by database instance. Each instance is identified by a SID or a service name. For the purposes of this FAQ, the examples assume a database SID of "SDMS".
      • A second DB instance also exists named "SLIM" (by default), for the Stability module.
      • TNS Listener: in Drive:\oracle\product\12.2.0\diag\tnslsnr\<hostname>\listener\trace\listener.log. Additional information may be available in *.trc files.
      • Alert log: in Drive:\oracle\product\12.2.0\diag\rdbms\SDMS\sdms\trace\alert_sdms.log. Additional information may be available in *.trc files.
    • SDMS 9 client log files:
      • Archive Template builder in SDMS Administrator: Error messages are written to Drive:\Program Files (x86)\Waters\NGSDMS\PM\DATE.log and DATE.derr, where DATE is in the format YYYY-MM-DD
      • NuGenesis Restore: Log files are written to Drive:\ Program Files (x86)\Waters\NGSDMS\UV. Old log files are stored in the SDMS_System_Activities project and deleted from disk

 

ADDITIONAL INFORMATION

 

id74663, MSDS, NGLMS, NGLMSLIC, NGLMSOPT, SDMS, SDMS8, SDMS8NU, SUPISDMS, SUPNG

Not able to find a solution? Click here to request help.