OpenProcessToken failed.
I got this message after applying my gp to an XP workstation. It happens when I try to use the override shutdown command. I'm guessing it has to do with "Allow only specified programs to run" setting. I did add PWB.exe to the list. What to I need to add for the shutdown command to work? Or what else could cause this error? Thanks.
Anthony
"OpenProcessToken failed." Error on Shutdown
Moderators: Tyler, Scott, PWB v2 Moderator
"OpenProcessToken failed" now with v.2.06
I just upgraded all of our web catalogs to v.2.06 (from 2.04) to solve the Trend/inactivity problem, and now I've picked this new problem up, I'm getting the "Open Process Token Failed" error when I try the shutdown override.
Nothing else has changed, these are all Windows 2000 sp4 in a restricted user account for the public users. This also happens in an administrative account. Every account and the System have the permission to shut down the computer.
It's not a severe problem, as "shutdown" still closes the browser, and people can then shut the pc down normally from the start button. But it does add steps, and take away what I thought was a really cool feature.
Dan
Nothing else has changed, these are all Windows 2000 sp4 in a restricted user account for the public users. This also happens in an administrative account. Every account and the System have the permission to shut down the computer.
It's not a severe problem, as "shutdown" still closes the browser, and people can then shut the pc down normally from the start button. But it does add steps, and take away what I thought was a really cool feature.
Dan
Try this revision which fixes a bug that can cause Windows XP computers to display this error.
http://www.teamsoftwaresolutions.com/beta/PWBv206r3.zip
We are waiting on releasing PWB v2.06 revision 3 because PWB v2.07 will be coming out soon.
--Scott
http://www.teamsoftwaresolutions.com/beta/PWBv206r3.zip
We are waiting on releasing PWB v2.06 revision 3 because PWB v2.07 will be coming out soon.
--Scott
That fix it!
Thanks, the v.2.06r3 fixed the problem!
This was on Windows 2000 SP4 machines.
Dan
This was on Windows 2000 SP4 machines.
Dan