2007 upgrade can not find 2003 portal/site
hi,
i am testing an upgrade from SPS2003 (SP2) to MOSS 2007 (RTM Enterprise). the installation goes fine and i selected 'gradual upgrade'. the prescan tool does not report any issues and the configuration wizard runs fine as well. MOSS 2007 is up and running and i can create sites etc.
however, when i try to initiate the gradual upgrade process through "Site content upgrade status" in Operations, the page says: "There is nothing associated with this server farm that can be upgraded".
i have also tried to start the upgrade with stsadm and i have the same problem. stsadm returns: "No web application from a previous version of SharePoint matches the URL: [myserverurl]"
SPS2003 is running on port 80 on the server and is still functioning. the WSS 2.0 Virtual Server List still shows the 2003 virtual server (version 6.0.2.8117) and does not show any problems.
any idea why MOSS does not see the 2003 portal?
thanks,
jeroen
I am experiencing a similar problem.
When I go into the "Site Content Upgrade Status" screen. I have 2 sites, one is a test site (to test the gradual upgrade process) but when I click on the link to complete the upgrade, it doesn't find any site collections available.
There is also a WSS 2.0 site that was originally part of the previous SPS 2003 portal. This site was backed up using the STSADM utility on SPS 2003 and restored to its own virtual server on a new server (we wanted this site to have its own url). When I attempt to begin updating this site, it goes to the first page (where we set the DB's and such) then when I click to continue, it gives a generic error message. I have had trouble finding anything descriptive in the logs on this error.
In this farm, I also have 2 SPS 2003 portals running working fine but are not in the upgrade list.
I have 2 questions:
Where should I look to make sure the MOSS Config DB can see my portal sites that are not listed?
Where should I start to begin troubleshooting the WSS 2.0 top level site (the unknown error problem)?
I would like to get these sites updated as soon as possible so the environment is clean and I can get working on a Master Page.
Thanks,
Mark
looking at the SQL server activity when telling MOSS to upgrade, it looks like MOSS is querying the 2003 ConfigDB to find sites/portals that can be upgraded. it does find my active SPS2003 Portal in the first query but it seems to ignore this in subsequent queries. there must be something about those ConfigDB entries that MOSS doesn't like, but I don't have a clue what it could be.
still hoping someone else has an answer?
OK, I found the solution. MOSS did not recognize the 2003 portal because I had changed the IIS site name and the only way that SharePoint can identify the 2003 sites in IIS is through the name.
to be more precise, the 'virtualservers' table in the 2003 config database only has the IIS site NAME and no reference to the IIS Instance ID. so because MOSS could not find the name in IIS (because I changed it), it didn't list the 2003 portal as upgradable...
Awesome solution!
I was banging my head against the wall trying to figure out why my old site didn't show up in the upgrade page...
I went and looked in the database, and sure enough... the original site was setup with an IIS description of "Default Web Site", and somewhere down the road I'd changed the name of it to "Sharepoint" (probably when I added some more virtual websites here and there).
That's a really annoying bug... glad someone figured it out.
To make future google searches easier (I sort of stumbled on this thread):
Sharepoint SPS 2003 migration upgrade to MOSS 2007 fails - site content upgrade status shows empty list of URL's, gives an error of "nothing associated"
Resolution in this case was to look in the old config database SPS01_Config_db in the PortalURL's table, and the value in the "Name" column is what it expects the IIS site to be named. If you've renamed that website since you installed sps 2003, just name it back to what shows up in the db, maybe do an IISRESET for good measure, and voila, the "site content upgrade status" page now lists your URL! Hooray! 
