The application failed to initialize properly (0xc0000022).

Help and support using the 3D and Bitmap Machining CAM packages:
QuickCAM 3D, QuickCAM 3D Pro, QuickCAM 4D (rotary axis CAM)

Moderators: Martin, Steve, Mr Magoo

Post Reply
User avatar
Denford Admin
Site Admin
Posts: 3632
Joined: Fri 10 Feb , 2006 12:40 pm
Hardware/Software: Go to User Control Panel > Profile
Enter as much information about your CNC hardware and software as you can - it makes it easier for everyone to know what you're talking about then.
Location: Sunny Brighouse
Contact:

The application failed to initialize properly (0xc0000022).

Post by Denford Admin » Wed 26 Apr , 2006 15:15 pm

We are having problems in running the QuickCam 4D software on our school machines

The machine is a PC running Windows 2000 on the school network. It is sited next to the Microrouter we purchased in December 05. The software is installed on the machine in accordance with the single user licence.


The software runs OK when a user with full administrator permissions logs on. However, when a student or member of staff logs on we get the following error message:-


The application failed to initialize properly (0xc0000022).

User avatar
Denford Admin
Site Admin
Posts: 3632
Joined: Fri 10 Feb , 2006 12:40 pm
Hardware/Software: Go to User Control Panel > Profile
Enter as much information about your CNC hardware and software as you can - it makes it easier for everyone to know what you're talking about then.
Location: Sunny Brighouse
Contact:

Post by Denford Admin » Wed 26 Apr , 2006 15:16 pm

There are a couple of INI files QuickCAM4D writes to:

C:\Documents and Settings\USERNAME\Application Data\Denford
(this is true for the latest version v1.6 which can be downloaded from our website)

However, these files DON'T have to be present to run the software.
The initialisation problem must be to do with a DLL or OCX that is being used by QuickCAM 4D, which cannot be loaded up because of user permisions
Searching the Internet, I found this advice to give all users at least read access to OCX and DLLs in the system32 directory
CACLS %systemroot%\System32\*.dll /E /G BUILTIN\Users:R
CACLS %systemroot%\System32\*.ocx /E /G BUILTIN\Users:R
also see http://support.microsoft.com/default.as ... US;Q276407&#

DLL's and OCX's to check for are:
deskey32.dll
wdrvr.dll
ntoskrnl.dll
instsec.dll
plus any OpenGL libraries eg, OpenGL32.dll - especially ones provided by graphics card manufacturer

Post Reply