Ken, I edited the metabase and was certutil was then able to run OK. Many
"Ken Schaefer" wrote:
> From memory, you should just be able to add a virtual directory that points
> to the certsrv folder. Additionally, if required, add .cer as processed by
> ASP.
>
> The other option would be to simply create a new website called "Default Web
> Site". You can edit the metabase to set the identifier to "1". That will,
> hopefully, enable you to create the virtual directory using certutil.exe.
> Afterwards, just create a virtual directory with the same settings on any
> other arbitrary website (you can export/import a metabase node), and then
> delete/deactive the Default Web Site you created.
>
> Cheers
> Ken
>
> --
> My IIS Blog:
www.adOpenStatic.com/cs/blogs/ken >
> "Karl" <Karl@discussions.microsoft.com> wrote in message
> news:B1356D44-519B-4990-812A-280EBA8D9480@microsoft.com...
> >I have two servers that I'm having a problem installing Certificate
> >Services.
> > Both are running Server 2003, one of them SP1 and the other other SP2.
> > Both
> > have IIS installed; the SP2 one is supporting 12+ domain web sites.
> >
> > When trying to install Certificate Services, I get the following message
> > at
> > the end of the installation: "Internet Information Services (IIS) is not
> > installed on this computer. Certificate Services Web Enrollment Support
> > will
> > be unavailable until IIS is installed".
> >
> > I've checked IIS and then ran "certutil -vroot" to try and resolve the
> > issue
> > and get the following message; I can find no reference to the 80070003
> > code
> > returned.
> >
> > Web Virtual Root Create Error
> > File Share Already Exists
> > CertUtil: -vroot command FAILED: 0x80070003 (WIN32: 3)
> > CertUtil: The system cannot find the path specified.
> >
> > My best guess is that because neither of these machines has the original
> > default web site at Identifier 1 (W3SVC1), the Certificate Services
> > Installer
> > is failing when trying to configure the Web Enrollment Site.
> >
> > Can anyone shed any light on this issue and how I can resolve it?
> > Uninstalling and then reinstalling IIS is not an option.
> >
> > Thanks.
> > Karl.
> >
>