Discussion Locked

The application failed to initialize pro

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

What's wrong on the W2k Advanced Server (SP2) if we start getting this error message:
Application Error : The application failed to initialize properly (0xc0000142)
This is the result of almost all attempts to start a task (e.g. McAfee console, orSAP dispatcher cannot connect to the message manager running on the same box, or mmc.exe).

9 replies

by maxwell edison

Greetings,

A possible solution:

This error occurs when a Windows 2000 program (often running as a service) restricts access to OpenGL. To start OpenGL programs in this case, you must stop the program that has exclusive control over OpenGL. Ifthis program is running as a service, change the Startup Type of the service to Manual and then reboot.

Something to try.

Good luck,

Maxwell

by maxwell edison

.
.
Another possible solution - Run the following utilities:

Application Compatibility Tool:

The Windows 2000 Application Compatibilty Tool (apcompat.exe) allows you to set certain pre-Windows 2000 settings in a virtual machine and then run non-Windows 2000 aware programs within that context. In some cases, it can make applications work that refuse to function properly within Windows 2000.

Microsoft Windows 2000 Readiness Analyzer:

The Windows 2000 Readiness Analyzer tool analyzes your system and reports potentially incompatible hardware devices and software applications.

Good luck (again),

Maxwell

by maxwell edison

.
.SYMPTOMS
========

Non-administrators who log on to a Microsoft Windows 2000-based server running
Terminal Services, may receive the following error message:

Userinit.exe application error. The application failed to initialize properly
0xc0000142 click ok to terminate the app.

The user is then automatically logged off. The same user, however, can log on to
the Terminal Services console without receiving the preceding error message.

CAUSE
=====

This behavior can occur because the administrator has not assigned the user the
right to bypass traverse checking.

RESOLUTION
==========

To resolve this behavior, the administrator must give the user the right to
bypass traverse checking.

STATUS
======

Microsoft has confirmed this to be a problem in the Microsoft products that are
listed at the beginning of this article.

MORE INFORMATION
================

To find out which users have the right to bypass traverse checking, look in
Group Policy for the Windows 2000-based server and follow these steps:

1. Click Computer Configuration.

2. Click Windows Settings.

3. Click Security Settings.

4. Click Local Policies.

5. Click User Rights Assignment.

6. Double-click Bypass traverse checking.

The Effective Policy setting must give the Terminal Services users this right. By
default, the Everyone group should already have this right. The current
Effective Policy settings could have been inherited from policies within the
domain. If this is the case, those domain policies have to be changed.

Also a link to a similar problem:

http://www.jsiinc.com/SUBG/TIP3000/rh3087.htm

Regards,

Maxwell

by maxwell edison

.
.
(Cut and paste messed up) The preceding comment was a solution found in:

MS KB [Q272142] "Users Logged Off Automatically When Logging on Terminal Services."

by palkerekfy

Hello Maxwell,
All of the suggestions are being analysed and verified in our system. I will come back to you with the results, hopefully, soon.
Many thanks!

This discussion is closed to new replies.