Sharepoint Services 2.0 not finding content

Hi All

We have a really old Server 2003 box, with WSS 2.0, which is being upgraded / migrated to Server 2008R2.

In prep for the move to Sharepoint 2010, WSS 2.0 was service packed to SP2 and then an in-place upgrade was done to Sharepoint Portal Server 2003, as a step towards Sharepoint 2010.

Somewhere in the mix, the system lost track of the content. SPS2003 has been uninstalled and the files from backup have been restored to what they were before SPS2003.

You would think that fixes the problem, but we now have a page which says

"Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
"

Can anyone guide us as to reconnecting the WSS 2.0 back to the DB content ?

Also, is there a better way to migrate to Sharepoint 2010 ?

Thank you
LVL 1
DoveSupportAsked:
Who is Participating?
 
bas2754Connect With a Mentor Commented:
Can you post what the application log entry says is the problem?  I am by no means a sharepoint Guru, but wanted to try to help if possible.  I have dealt with my share of issues with SQL, Sharepoint, and Windows.  Unfortunately a LOT of detail is missing to even try to guess at the problem, but my thoughts would be:

1.  The web application folder in IIS has been deleted, changed, or moved
2.  ASP.NET version incorrect?
3.  Cannot find SQL Content causing the application to bomb?

You may want to enable logging in IIS and check what the IIS logs say as well.  Post back what it all says and maybe we can figure it out.
0
 
DoveSupportAuthor Commented:
Hi bas2754 - thanks for the reply. It looks like the old sharepoint has been modified to work on 2003, but it has got stuck in the middle. The old version ran on "http://hostname/department/default.aspx", whereas 2003 runs off "http://hostname/sites/department.aspx" etc
It's quite possible that the IIS config has been modified, but I can't find config for the old version, in order to change it - almost like the old version's  config tools weren't installed.
Nothing blatantly obvious is popping up in the application log - both under normal operation and when the site is accessed.
WSS 2 has been repaired, service packed and reinstalled, but there's still something missing !
0
 
DoveSupportAuthor Commented:
Ok, so I built a new VM and installed WSS2.0, then attempted to link the central administration site to restored copies of the content and config databases. The wizard on the config database gives me "The IIS application pool user name is invalid."
I've set many user accounts to run the app pool identity etc, but only the "Network Service" works to allow the central admin site to work, but then the wizard gives me the error.

Anyone have any ideas ?
Thanks
0
 
bas2754Commented:
I am taking a complete and total shot in the dark here...

1.  Whatever user ID you use to run the IIS Applicaton Pool must have permissions (NTFS) to the folder containing the IIS content.

2.  The same user used to run the App Pool also will need permissions to access the SQL Database.

Does the Network Service have permission to SQL database (both NTFS and in SQL itself?).  Again this is just shooting from the hip, but I have run across issues with a .NET app not working for these same reasons myself.
0
 
DoveSupportAuthor Commented:
Right, so in the end, an installation of WSS2 SP3 was all it needed to relink everything and bring the POS back up !
Thanks bas2754 - the only one to respond and thus get points !
0
All Courses

From novice to tech pro — start learning today.