Troubleshoot Jobs and Services

If your job or service experience any of the following symptoms, refer to the following resolutions.

To debug jobs and services, you can enable the logging of the SOAP packets that are transmitted and received by the DataFlux Data Management Server. See Enable the SOAP Log,

Windows displays the following error message:

The application failed to initialize
properly (0xc0000142). Click OK to terminate the
application.

The Data Management Server log file might also display one of the following messages:

Data Service error:   failed to start
service process: 1 - Child failed to 
contact server process. Failed to start
base services, rc=1 (Error loading 
dependency library).

Process Service error:   Failed to 
getprocess, errorCode=2 (Process 
'HOST:ADDR' exited unexpectedly.)

Batch Job error:  failed to get process;
err: 0 - Process 'HOST:ADDR' exited unexpectedly.

It is possible for the Windows event log to not contain entries for DFWSVC and DFWFPROC, even when the DataFlux Data Management Server logs contain one or more entries. This symptom often indicates that the failure to start processes is caused by Windows running too many internal processes. The DataFlux Data Management Server cannot start new processes.

The log discrepancy occurs when Windows runs out of desktop heap. Specifically, the desktop heap in the WIN32 subsystem becomes depleted. To free system resources, stop as many non-essential applications and processes as permissible and try to run the jobs again on the DataFlux Data Management Server. If the errors persist, you might need to make a minor change in the Windows registry to increase the SharedSection parameter of the SubSystems key in HKEY_LOCAL_MACHINE. For additional information, see the following Microsoft Support articles:

This error message indicates that the libraries for OpenSSL were placed in a directory other than /bin. Make sure that the libraries match the host operating environment (32-bit or 64-bit.) Copy the libraries to the /bin directory and restart the server.

This error message indicates that someone at your site has upgraded the repository on the DataFlux Data Management Server. Install a new version of DataFlux Data Management Studio to use the new repository.

If you create a new WSDL for a service using DataFlux Web Studio, you can receive a not licensed error in the DataFlux Web Studio log file. To resolve this error, open DataFlux Data Management Studio, and then select ToolsData Management Studio OptionsData Management Server. Select the options Connect to Data Management Server for SAS and Connect to Data Management Server Web Edition.

The Driver for BASE does not allow data sets to be created that cannot be read by SAS. If you have Driver for SAS files that contains letters that cannot be accessed in the UNIX or Linux operating environments, then you will need to rename the file to all-lowercase. Other files that contain mixed case or uppercase letters might also need to be renamed using lowercase letters. Once the files are renamed, they can then be accessed in jobs using any case. For example, the file might be named lookupsource. In jobs, you can reference LOOKUPSOURCE, lookupsource, or LookUPSoUrCe, just to name a few.

This error occurs on some configurations of Microsoft Windows Server 2003, when the log file exceeds 32KB. A workaround for this problem is to set the following configuration value in the dmserver.cfg file:

DMSERVER/LOG_CHUNK_SIZE = 32KB

This error and this resolution apply only when the host of your Data Management Server is running Windows Server 2003.

The following error message content indicates that the job is attempting to use an unsupported version of Address Doctor:

2011-11-10T10:52:11,303 INFO [00001789] - 
Node DATAFLOW_0 started.2011-11-10T10:52:11,
390 ERROR [00001793] - Unknown locale name

To resolve this error, edit the job to use the latest Address Verification node, which uses the latest version of the Address Doctor software.

This error occurs when the currently loaded QKB uses definitions that are newer than those that are supported by the current version of the QKB. By default, the QKB attempts to load the definitions and issues warnings before loading them. If the definitions include instructions that the QKB cannot process, the instructions are ignored and an error is displayed.

The QKB/ALLOW_INCOMPAT option can be used to specify whether to allow incompatible QBK definitions to be processed by the QKB. The option is defined in the app.cfg file; it enables you to choose to either stop processing or allow the incompatibility and continue processing the definitions.

A job with a custom scheme that fails to run will produce an error similar to the following:

0817_11:17:40.691 ERROR   Node
DATAFLOW_0 error: 3: DQ Engine - 
DQ load scheme 'frfra001.sch.bfd' failed: 
DQ Engine - DQ error -400:
DQ Engine - Cannot open file "frfra001.sch"..

0817_11:17:40.694 INFO    Job terminated due to 
error in one or more nodes.

To resolve this error, ensure that the name of the scheme is entered correctly, as it is case sensitive. Also ensure that the QKB you are using is an exact copy of the QKB used when the job was created in DataFlux Data Management Studio.

To copy the QKB from Windows to UNIX or Linux, use FTP or Samba mappings. After you copy the QKB, restart the DataFlux Data Management Server and run the job again. In UNIX and Linux, change the scheme name (in the scheme directory of the QKB) as needed to use all lowercase letters.