|
Posted by Ken Schaefer on October 4, 2006, 10:51 pm
Please log in for more thread options You are running a 32bit worker process - you want to be using a 64bit worker
process.
See:
http://www.adopenstatic.com/cs/blogs/ken/archive/2006/09/30/Certificate-Services-Website-generates-404-on-Windows-Server-2003-x64-_2800_64-bit-edition_2900_.aspx and change the IIS metabase setting back
Cheers
Ken
>I recently reinstalled a machine with x64 edition in order to better
> use the 6GB of RAM on the server. It was previously running 32-bit and
> was an enterprise root CA and domain controller. I performed steps
> outlined in KB 298138 to backup the CA in preparation to re-add it back
> to the machine once it had x64 installed. I then removed the CA from
> 32-bit and dcpromo'd the machine out of active directory, and then
> removed it from the domain.
>
> I staged the box with W2k3 Standard x64. I installed IIS, and then I
> installed Certificate services (along with the optional IIS/web
> component) and configured it as an enterprise root. I imported
> previously saved settings (from a 32-bit system) on the server. The
> old system and the new install are using the same computer name so as
> to keep the root CA functioning properly.
>
> The import went fine, but then I was unable to access the /certsrv
> directory on the webserver. It would show 404 and 403.1 and 403.2
> (access denied/bad credentials type errors).
>
> I eventually broke out filemon and watched the system as I hit "go" on
> the URL bar... and that's when I noticed "w3wp.exe" (IIS web server
> process) was trying to hit C:\Windows\SysWOW64\CertSrv and throwing NOT
> FOUND errors in filemon.
>
> The CertSrv folder is in C:\Windows\System32.
>
> Obviously, this is a problem. I didn't want to just move the folder
> around, so I found a utility to allow me to create an NTFS junction
> point. I created a junction with the source of %windir%\system32 and
> the target of %windir%\syswow64\certsrv. Now the full tree is where it
> is expected to be by IIS and the web site sort of works. However, now
> it throws errors when I try to submit a request - "an unexpected error
> (0x000001A8) occurred while getting the certificate template list."
>
> I'm stuck now... did anybody test the operation of the CA services in
> an x64 system before it went gold?
>
|