Troubleshoot Orchestration Jobs

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

The Runtime Server log file dmserver.log displays the following error message:

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

The Runtime 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 that the Windows event log does not contain entries for DFWFPROC, and one of the preceding errors appears in the Runtime Server log. In that case, then the error is likely caused by a large number of Windows processes running on the host. The number of processes can prevent Windows from opening new DFWFPROC processes for the Runtime Server. This behavior occurs when Windows runs out of desktop heap. Specifically, the desktop heap in the WIN32 subsystem can be depleted. To free system resources, stop as many non-essential applications and processes as permissible and try to run the jobs again on the Runtime Server. If the errors persist, you might need to make a minor change in the Windows registry. Increase the SharedSection parameter of the SubSystems key in HKEY_LOCAL_MACHINE, as recommended in the following Microsoft Support articles:

This error message indicates that security is enabled on the Runtime Server and that OpenSSL was not found. The OpenSSL directories either need to be located in the /bin directory or listed in the PATH environment variable. To resolve this error, add the directories to /bin or update the PATH variable and restart the server.

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 contain mixed case or uppercase letters that cannot be accessed in UNIX or Linux, then rename the file to all lowercase letters. 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 to Windows Server 2003.