I posted this question in microsoft.public.sharepoint.portalserver. Any suggestions?
I just came on board in a company with SPS2003 installed on a single server with SQL. The portal is up and running and in production.
The first thing I did was run Sharepoint configuration analyzer. I received "Error detected: Windows Sharepoint Services is not installed on
In SP2003AdminTools: <Error>The virtual server that is referenced here
is not in the config database.</Error>
From the browser, I receive "HTTP Error 403 - Forbidden"
In SP Central Admin, Virtual Servers
URL Version
Not Installed Extend
Questions:
Should I "Extend and create a content database" using the same username admin acct that created the existing application pool?
If so, what are the risks, if any to production?
Is there something else I should do to correct this?
Thanks in advance.
I just came on board in a company with SPS2003 installed on a single server with SQL. The portal is up and running and in production.
The first thing I did was run Sharepoint configuration analyzer. I received "Error detected: Windows Sharepoint Services is not installed on
In SP2003AdminTools: <Error>The virtual server that is referenced here
is not in the config database.</Error>
From the browser, I receive "HTTP Error 403 - Forbidden"
In SP Central Admin, Virtual Servers
URL Version
Not Installed Extend
Questions:
Should I "Extend and create a content database" using the same username admin acct that created the existing application pool?
If so, what are the risks, if any to production?
Is there something else I should do to correct this?
Thanks in advance.