Re: IIS Error - 500 when running a CGI/EXE after upgrading XP to
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 01/19/05
- Previous message: David Wang [Msft]: "Re: IIS 6 is a steaming pile of ***"
- In reply to: ATS: "Re: IIS Error - 500 when running a CGI/EXE after upgrading XP to"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 19 Jan 2005 13:25:30 -0800
Thanks for the info.
That is weird. I know we run a lot of tests against CGI to cover the cases
when upgrading from XP RTM as well as XP SP1 to XPSP2 (across various CPU,
language, etc), and there weren't any problems with privileges on any of
those runs.
Is your machine stand alone or in a domain? Perhaps a Group Policy script
or something custom was run on your server to change this setting (but never
restarted the server) -- and due to XPSP2 requiring a server restart, you
now see the issue?
-- //David IIS http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights. // "ATS" <ATS@discussions.microsoft.com> wrote in message news:ED4389A3-C49E-4504-8760-B1B10BD1B0BB@microsoft.com... Thanks for the reply, SP2 does indeed impact the security. It is either taking away the privelege for IUSR and IWAM to "Create Token Objects" and/or adding a new privilege called "Create Token Objects" (which I doubt, and could easily determine, but don't have the time to), of which it is not adding IUSR and IWAM to. I confirmed this by simply adding IUSR and IWAM to have that privilege and then IIS and CGI worked.
- Previous message: David Wang [Msft]: "Re: IIS 6 is a steaming pile of ***"
- In reply to: ATS: "Re: IIS Error - 500 when running a CGI/EXE after upgrading XP to"
- Messages sorted by: [ date ] [ thread ]