We've installed 24X7 on a new server and are having
problems with jobs that run other applications
(using RunAsUser).

The error message is as follows:
"The application failed to initialize properly
(0xc0000142). Click on OK to terminate the
application."

These jobs are currently being run on another server
with no problems. The user permissions are the
same on both servers. Any thoughts on what else
we should check? Thanks.

Please check you if you have the same system search PATH and also compare values of other environment variables.

Also, try running something simple like Notepad to see if is a common problem or a problem specific to your applications.

: We've installed 24X7 on a new server and are having
: problems with jobs that run other applications
: (using RunAsUser).

: The error message is as follows: "The application failed to initialize
: properly
: (0xc0000142). Click on OK to terminate the
: application."

: These jobs are currently being run on another server
: with no problems. The user permissions are the
: same on both servers. Any thoughts on what else
: we should check? Thanks.

: Please check you if you have the same system search PATH and also compare
: values of other environment variables.

: Also, try running something simple like Notepad to see if is a common problem
: or a problem specific to your applications.

We already tried the Notepad test and received the same
error. It appears to occur with any .exe file. I'll look
at the environment variables.

Are there any related errors in the Windows NT system and application event logs?

: We already tried the Notepad test and received the same
: error. It appears to occur with any .exe file. I'll look
: at the environment variables.

: Are there any related errors in the Windows NT system and application event
: logs?

Yes, the log reads "A required privilege is not held by the client."
We have the following set:
Log on as a batch job
Log on as a service
Log on locally

What's missing??

Are you giving these privileges to the right user? Are you using local user or domain user to run jobs? Are you using admin user account to run the scheduler?

: Yes, the log reads "A required privilege is not held by the
: client."
: We have the following set: Log on as a batch job
: Log on as a service
: Log on locally

: What's missing??

: Are you giving these privileges to the right user? Are you using local user
: or domain user to run jobs? Are you using admin user account to run the
: scheduler?

Hi, i am currently experiencing the same problem.
I am running 24x7 on a server. My 24x7 script executes runs 2 external programs throughout its execution. One a Cognos Macro script and the other an emailing client.
When i run the job a few times i get the following error:
"Application popup: 24x7.exe - Application Error : The application failed to initialize properly (0xc0000142). Click on OK to terminate the application."

Another error that appears in the event log is:
"The server {785CB4D1-4675-11D6-8F22-0} did not register with DCOM within the required timeout."
This error might be related to the macro exporting a report into Excel.

I usualyt get a few of these DCOM errors without much of an effect on 24x7. However, once i get those application errors, the service stops running, and even though it still says 'started' in the services panel, it only starts working again after i restart the service.

Thanks.
Tim.

Are you running JAL or VBScript?

Also
1. In the registry look under "HKEY_CLASSES_ROOT\CLSID\{785CB4D1-4675-11D6-8F22-0}\InprocServer32" key which program is registered as {785CB4D1-4675-11D6-8F22-0}
2. Try running this job manually and then after completion check in the Windows Task Manager (Processes tab) if it shows any traces of Cognos, Excel or other program that were not there before you ran the job.

: Hi, i am currently experiencing the same problem.
: I am running 24x7 on a server. My 24x7 script executes runs 2 external
: programs throughout its execution. One a Cognos Macro script and the other
: an emailing client.
: When i run the job a few times i get the following error: "Application
: popup: 24x7.exe - Application Error : The application failed to initialize
: properly (0xc0000142). Click on OK to terminate the application."

: Another error that appears in the event log is: "The server
: {785CB4D1-4675-11D6-8F22-0} did not register with DCOM within the required
: timeout."
: This error might be related to the macro exporting a report into Excel.

: I usualyt get a few of these DCOM errors without much of an effect on 24x7.
: However, once i get those application errors, the service stops running,
: and even though it still says 'started' in the services panel, it only
: starts working again after i restart the service.

: Thanks.
: Tim.

: Are you running JAL or VBScript?

: Also
: 1. In the registry look under
: "HKEY_CLASSES_ROOT\CLSID\{785CB4D1-4675-11D6-8F22-0}\InprocServer32"
: key which program is registered as {785CB4D1-4675-11D6-8F22-0}
: 2. Try running this job manually and then after completion check in the
: Windows Task Manager (Processes tab) if it shows any traces of Cognos,
: Excel or other program that were not there before you ran the job.

Im using JAL

I have just been testing this out. It seems that everything works fine when 24x7 is not running as a service.
The 24x7job executes the macro script which exports to excel perfectly, and emails the notification wihtout any problems.

It is when i turn the service back on. THat whenever the 24x7 job runs, i get that DCOM error, and the excel export runs, but fails to change update the file.
the 24x7 Application error then comes up after running the reports a few times.

any ideas?

It probaly fails because of some networking issues (no permission or access).
Don't run the service using LocalSystem account. Use domain admin or other administrative account for that purpose.

: I have just been testing this out. It seems that everything works fine when
: 24x7 is not running as a service.
: The 24x7job executes the macro script which exports to excel perfectly, and
: emails the notification wihtout any problems.

: It is when i turn the service back on. THat whenever the 24x7 job runs, i get
: that DCOM error, and the excel export runs, but fails to change update the
: file.
: the 24x7 Application error then comes up after running the reports a few
: times.

: any ideas?

: It probaly fails because of some networking issues (no permission or access).
: Don't run the service using LocalSystem account. Use domain admin or other
: administrative account for that purpose.
It's the desktop heap problem..
See for more details:
http://www.ss64.com/orasyntax/desktopheap.html
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q126962

In the registry
HKLM\System\CurrentControlSet\Control\Session Manager\SubSystems
"Windows" Key
Change the value from "...SharedSection=1024,3072,512..."
to
"...SharedSection=1024,3072,1024..." and reboot the machine
Read the above sites as it has a pretty descent explanation.

regards
Anand

Thanks for this info. It might be helpfull to other users.

: It's the desktop heap problem..
: See for more details: http://www.ss64.com/orasyntax/desktopheap.html
: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q126962

: In the registry
: HKLM\System\CurrentControlSet\Control\Session Manager\SubSystems
: "Windows" Key
: Change the value from "...SharedSection=1024,3072,512..."
: to
: "...SharedSection=1024,3072,1024..." and reboot the machine
: Read the above sites as it has a pretty descent explanation.

: regards
: Anand