locked
WSS 3.0 Unable to access Site Collection after DB move RRS feed

  • Question

  • Hi all

    I have recently moved a WSS 3 server farm. The web server has remained, however the databases all shifted to a new server (admin content, config and site content databases).

    I did the move using the answer to this question: http://social.technet.microsoft.com/Forums/sharepoint/en-US/4f833383-6d77-4879-ac3e-051a06766a4e/migrating-wssadmincontent-and-wssconfig-databases-to-another-database-server?forum=sharepointadminlegacy

    I am able to access the admin site, and the backup has restored the admin content (I can see the site collection and application in the admin site) however I am unable to browse to the site collection - I receive a 404 error.

    IIS is on a 2k3 server (so it's IIS 6) and is running the admin site under .net 4 and the site collection under .net 2. The site collection app is set up and pointing to the correct folder, and permissions to said folder seem to be adequate. The AppPool is running as Network Service and the Site Collection app is using Integrated Auth only.

    The databases all have the same permissions between servers (so previous setup matches current) - the config wizard and restore have set everything up as expected. The DOMAIN\SERVERNAME$ account has access to the databases, which appears to be enough for the admin site.

    With a little further investigation with fiddler, I have found the 404 result occurs after a 401.2 followed by a 401.1 - but the user doesn't receive this error, they just get the end result, being the 404.

    I am logged into an account with site admin permissions, so I think that rules out SharePoint rejecting access, but rather on the IIS side.

    Any help would be greatly appreciated to resolve this issue.

    Cheers!

    Tuesday, November 12, 2013 7:32 PM

Answers

  • The content databases were restored from admin app backup.

    The next link didn't help either I am afraid.

    But I did get it resolved today by creating an entirely new application, using a new port and then using the same content database. It's odd that a site collection using the same app was working while the original one didn't, and that the same content db and site collection on a different app resolved the problem of the original.

    Thanks for the responses though :)

    Thursday, November 14, 2013 4:53 AM

All replies

  • One thing i would check, if new Content database point to the web appliction. you can check under the content DB,

    if its still point to the old detach that one and attach new db pointing to new DB server.

    if not, simply detach the content and reattach same after 1 min wait, trick will work.


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Tuesday, November 12, 2013 7:52 PM
  • Thanks for the response, but the content DB is pointing to the correct database on the correct server :)
    Tuesday, November 12, 2013 9:30 PM
  • try to detach and reattach the DB?

    2nd option will be clear config cache.


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Tuesday, November 12, 2013 9:32 PM
  • Neither has resolved the issue. I will attempt to create a new site collection, but feel free to post other suggestions!
    Wednesday, November 13, 2013 3:12 AM
  • you can see the all the site collection on the central admin under the view all site collection?

    yes, its good idea create a new site collection and see if content DB code goes up by 1.


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Wednesday, November 13, 2013 3:16 AM
  • Yes, I can see it in the admin site.

    Adding a new site collection works and is accessible, and uses the same content db successfully.

    Wednesday, November 13, 2013 5:16 AM
  • any error you are seeing in the application Log or uls Log at the time when you browse a site and get 404?

    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Wednesday, November 13, 2013 5:29 AM
  • Nope :)
    Wednesday, November 13, 2013 6:17 AM
  • Hi Jono Stewart,

    From your description, I don’t understand how you move the content database, would you please first follow the steps below to make sure the content database are moved successfully.
    http://technet.microsoft.com/en-us/library/cc262792(v=office.12).aspx

    Error 401.1 and 401.2 indicates an authentication issue, for basic authentication, if the user name is a domain account, IIS contacts a domain controller to verify the credentials, if this fails, IIS returns a 401.2 error, if this success, but user name or password is invalid, IIS returns a 401.1 error, follow documentation below to do the troubleshooting:
    http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/8feeaa51-c634-4de3-bfdc-e922d195a45e.mspx?mfr=true

    Thanks,

    Qiao

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Qiao Wei
    TechNet Community Support

    Wednesday, November 13, 2013 8:09 AM
    Moderator
  • The content databases were restored from admin app backup.

    The next link didn't help either I am afraid.

    But I did get it resolved today by creating an entirely new application, using a new port and then using the same content database. It's odd that a site collection using the same app was working while the original one didn't, and that the same content db and site collection on a different app resolved the problem of the original.

    Thanks for the responses though :)

    Thursday, November 14, 2013 4:53 AM