oxc0000022 error application error

[NewsArchive]

So, I installed an update and for some reason on this one clients computer,
it will not run under a certain user. (I am installing into the root folder
still (please don't judge)). Normally we have no problem, but on this client
the one user has different permissions... and I get this error.

When I had them install the update, the install program asked to reboot,
which she did. Our install normally doesn't ask to reboot, at least I didn't
program it in there. So, is it possible that the installation program see's
something in the system registry from another program that wants the
computer rebooted? My feeling is another program (probably an antivirus) is
causing this problem... of course, I'm grasping at straws. To the client, we
installed the program then it didn't run under the lesser user.

Thanks,

--
Ray Rippey
VMT Software - http://www.vmtsoft.com

[NewsArchive]

Ray,

You can try running this as admin in the install folder to reset the
permissions:

icacls *.* /reset /t /c

http://technet.microsoft.com/en-us/library/cc753525.aspx

Larry Sand

[NewsArchive]

Ray

The reboot request will happen if they run your updater while they have the program
running. You should check that it is not in-use before allowing the update.

JohnG

>When I had them install the update, the install program asked to reboot,
>which she did. Our install normally doesn't ask to reboot, at least I didn't
>program it in there. So, is it possible that the installation program see's
>something in the system registry from another program that wants the
>computer rebooted? My feeling is another program (probably an antivirus) is
>causing this problem... of course, I'm grasping at straws. To the client, we
>installed the program then it didn't run under the lesser user.

[NewsArchive]

Ray,

What John said. The installer had to replace one or more in-use (locked)
file(s). As a result, Windows needs a reboot to complete the installation
process. You should test (before the file copy process begins) if there are
locked files in case you do not want a replace on reboot.

After the reboot, it's very well possible that a permission problem causes
it. The Windows CopyFile process does not copy permissions over from one
location to another (you have to reset it; see what Larry suggested or use
the "Set Access Control" function).

Friedrich

[NewsArchive]

Yes, I do check to see if the program is running... on the current machine.
Perhaps she had it running for 2 different users.. not sure how that
works... but I'll try the Set access control or what Larry said.

Thanks,

Ray