First-use issues

IVP

Performing DWAgent IVP is a very effective technique for identifying first-use problems as early as possible, especially after the configuration has been altered. A failure in IVP is usually qualified by a verbose error in one or more logs in <DWAHOME>\logs, which can help in identifying the root cause of the problem. You perform IVP by running this command: dwagent.sh -ivp

Investigating missing prerequisites, NOCLASSDEFFOUND exceptions

DWAgent is not a self-contained product. Depending on the emitters and proxies that are actually used in a specific installation, one or more prerequisite products must be available at runtime. All these products must be correctly referenced in the initial configuration of each component, as previously explained in this manual. A common symptom of an incorrectly referenced product prerequisite is a NoClassDefFound exception in DWAgent product logs that usually translates into a problem (e.g., a spelling error or a missing variable definition) in the environment read by DWAgent at runtime. In a complex production scenario, determining the actual environment variables available to the DWAgent at runtime might not be easy. A very effective technique to cope with this kind of problem is to take a user dump of a running DWAgent and inspect the section where an integral textual dump of the actual environment observed by DWAgent is reported. For example, you can take a user dump of a live instance of DWAgent by running this command: dwagent.sh -usrdump

Failure to run DWAGENT as a Windows service

In rare circumstances (depending on the combination of the Windows version being used and/or JRE versions and brands being used) a correctly registered Windows Service DWAgent may fail upon start-up reporting the following error messages in <DWAHOME>\logs\dwagentservice.log:

[2020-02-16 10:16:56] [174 javajni.c] [error] The specified module could not be found. [2020-02-16 10:16:56] [994 prunsrv.c] [error] Failed creating java c:\program files\java\jre6\bin\server

The root cause of this problem is a failure to load the correct instance of the Microsoft C Runtime Library dll, i.e. the one redistributed in your JRE bin directory. To work around this problem, copy any msvcr*.dll (e.g. msvcr71.dll) from your JRE bin directory to <DWAHOME>\bin\runtimeW64 directory.