TimTate
Tue Feb 13 13:38:00 CST 2007
This issue has been resolved. The error message pointed me to the
knowledgebase article that resolved the issue.
Please refer to the following KB article:
http://support.microsoft.com/kb/829113
"Tim Tate" wrote:
> OK, Time is running short, so I have gone back to using WSS 2.0; and have
> been successful in getting it to create the appropriate connections to the
> database; when using it's own, newly created files.
>
> When connecting to the original configuration database, the following error
> is presented:
>
> The virtual server that is referenced here is not in the config database.
>
> How do I get it to work? Associating it through the Central Administration
> and Virtual Server Settings do not work.
>
> "Tim Tate" wrote:
>
> > I have been succesful in creating a new instance at the same URL as the old
> > one, however I still can not access the data.
> >
> > In looking at the database, I see that the tables are the same; but when
> > looking at the database table information, I see there are possible
> > differeneces (databaseId; VitualServerID; DatabaseServiceId; etc).
> >
> > If I capture this information from the new databases and replace it in the
> > old database tables, will the data be accessable?
> >
> > Is there another/better way to get the data from the old database files?
> >
> > "Tim Tate" wrote:
> >
> > > I donâ??t know if this will help or not, but there are 2 different errors that
> > > are being received:
> > >
> > > Error one:
> > >
> > > Server Error in '/' Application.
> > >
> > > The resource cannot be found.
> > > Description: HTTP 404. The resource you are looking for (or one of its
> > > dependencies) could have been removed, had its name changed, or is
> > > temporarily unavailable. Please review the following URL and make sure that
> > > it is spelled correctly.
> > >
> > > Error two:
> > >
> > > You are not authorized to view this page
> > > You might not have permission to view this directory or page using the
> > > credentials you supplied.
> > >
> > > If you believe you should be able to view this directory or page, please try
> > > to contact the Web site by using any e-mail address or phone number that may
> > > be listed on the usplsdlnt602b.espace.eds.com home page.
> > > You can click javascript:doSearch() Search to look for information on the
> > > Internet.
> > >
> > >
> > > "Tim Tate" wrote:
> > >
> > > > Mike,
> > > >
> > > > I just verified that the IIS version on the server is 6.0.
> > > >
> > > > Please let me know if there is any further information you require.
> > > >
> > > > "Tim Tate" wrote:
> > > >
> > > > > Mike,
> > > > >
> > > > > Thanks for the reply. I was a bit tired when I put this question in, so
> > > > > excuse the confusion.
> > > > >
> > > > > 1. You are correct about the SQL Server. It was 2000, upgraded to 2005 and
> > > > > is now back at 2000.
> > > > >
> > > > > 2. I am 100% about the WSS. I have just verified in the Control Panel that
> > > > > there is now 2 entries for WSS:
> > > > > - Microsoft Windows SharePoint Services 2.0
> > > > > - Microsoft Windows SharePoint Services 3.0
> > > > >
> > > > > This is expected based on the overview I read indicating that both would be
> > > > > running simultaneously and you can remove 2.0.
> > > > >
> > > > > "Mike Walsh" wrote:
> > > > >
> > > > > > WSS 2.0 does not run on Windows Server 2000 as it requires IIS 6.0. Are you
> > > > > > 100% sure that what you were running previously was WSS 2.0?
> > > > > >
> > > > > > There is no SQL Server 2003. Can we asume you mean SQL Server 2005 ?
> > > > > >
> > > > > > Mike Walsh
> > > > > > WSS FAQ www.wssv3faq.com / wss.collutions.com
> > > > > > No private questions please (additions to FAQ welcome)
> > > > > >
> > > > > > "Tim Tate" <TimTate@discussions.microsoft.com> wrote in message
> > > > > > news:5A9AE099-A20C-4BF4-9204-2B9FFB0871B4@microsoft.com...
> > > > > > > We were running SharePoint Services 2.0 on Windows Server 2000 and SQL
> > > > > > > Server
> > > > > > > 2000. Windows Server was upgraded to 2003 and SQL Server was upgraded to
> > > > > > > 2003.
> > > > > > >
> > > > > > > At this point, SharePoint Services stopped working. I found that
> > > > > > > SharePoint
> > > > > > > Services 2.0 does not run on Windows 2003 because of a file conflict.
> > > > > > > Also
> > > > > > > that SharePoint Services requires SQL Server 2000.
> > > > > > >
> > > > > > > Therefore, SQL Server was downgraded to 2000.
> > > > > > >
> > > > > > > As for SharePoint Services, this was upgraded to 3.0 after applying the
> > > > > > > .NET
> > > > > > > 3.0 upgrade. The upgrade identified that there was a previous
> > > > > > > installation
> > > > > > > and upgraded the databases accordingly.
> > > > > > >
> > > > > > > The configuration and content tables can be viewed using the
> > > > > > > login/password
> > > > > > > identified in the SharePoint Central Administration WEB Site.
> > > > > > >
> > > > > > > When connecting to the SharePoint Services site the error message provided
> > > > > > > indicates that I do not have permissions to view the page. I can not
> > > > > > > alter
> > > > > > > the permissions in the Central Administration.
> > > > > > >
> > > > > > > I also can not create a new Virtual Server to display the content from.
> > > > > > >
> > > > > > > How do I get the content back?
> > > > > >
> > > > > >
> > > > > >