Neil Higham

I am trying to migrate our intranet from WSS3.0 and SQL 2000 to MOSS2007 and SQL 2005 on separate Sharepoint and SQL machines.

I've built the new servers and installed MOSS with an empty content DB. I'm now attempting to move the content from the old intranet, so have:

  • Backed up content DB on SQL 2000 server
  • Restored DB under new name on SQL 2005 server
  • Removed origianl content DB from MOSS server
  • Added original content DB using STSADM

I don't get any errors but I get a 404 error when attempting to access the site. My original site was http://intranet and the new one is http://newintranet.

Any ideas



Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Higham

Just for clarification I don't get any errors when I do the stsadm -o addcontentdb but I get a 404 error from Internet Explorer when I try to access the site.

Is it likely to becuase the URL has changed from intranet to newintranet or is that not included within the content DB

Thanks





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Hodgkinson

Relative urls are stored in the content database so that wont be the issue.

Did you prescan the database before attaching it. Did Prescan generate any errors

Have you tried adding /default.aspx to the end of the url

Try running an STSADM -o enumsites - url http://newintranet and see what results you get






Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Higham

I didn't prescan the daatabase before attaching it.

Adding default.aspx produced the same 404 result.

Running enumsites gave the error:

<Sites Count="1" Error="Object reference not set to an instance of an object."Object reference not set to an instance of an object.

Which doesn't mean a great deal to me

I can try unattaching the content DB and running a prescan if that is worth trying

Thanks,

Neil





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Higham

Looked at prescan and it doesn't work on WSS 3.0. It says that it needs WSS 2.0.





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Hodgkinson

Yeah sorry for some reason i was reading you migration as wss2 to wss3, my bad.

Did you have any custom managed paths on the old system. These must be recreated on the new environment also.






Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Higham

No, didn't have any managed paths. Tried redoing the wholes process again , but still get same problem. Any other thoughts




Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Hodgkinson

This now a bit tough to diagnose with trawling through the database to be sure the sites made it. A 404 would indicate the config database had been updated with the new sites but that the content databases doesnt have the content in there.

Any customer templates used on the old system These may not migrate properly.






Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Higham

Neil,

What do you mean by customer templates Customer site templates

Thanks,

Neil





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

kwm

If you go to http://newintranet/_layouts/sitemanager.aspx , are you then able to see your site structure





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Higham

No





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

kwm

Do you have any Site Collections in the Site collection list in CA

If not and If it is possible try to start over and then;

1. Create a new web application

2. Add the WSS content db with stsadm Co addcontentdb

3. Restore the SSP from WSS 3.0 on the MOSS farm by using stsadm Co restoressp

Code Snippet

stsadm -o restoressp -title SSPName-url http://portal:PortNumber C
ssplogin DOMAIN\ServiceAccount -mysiteurl http://portal:PortNumber/mysite
-indexserver MIGRATIONSERVERNAME -indexlocation "C:\Program
Files\Microsoft Office Servers\12.0\Data\Office Server\Applications" C
keepindex -sspdatabaseserver SQLSERVERNAME -sspdatabasename WSS_SSP
-ssppassword ServiceAccountPassword





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

kwm

NOTE:

Do not to create any SSP or site collections before attaching the DBs





Re: SharePoint - Setup, Upgrade, Administration and Operation Migrating from WSS3 to MOSS2007

Neil Higham

I've decided to do an export and import of each site, which seems to be going OK. Thanks for your help.