locked
WSS 3.0 Content Database not recognised on Foundation 2010 RRS feed

  • Question

  • Hi,

    I built a Windows 2008 Server(64-bit) and installed SharePoint Foundation 2010. I then did a backup of the content database from my old SharePoint server containing WSS 3.0 and restored it to a database on my new server. I then upgraded the database so SharePoint 2010 would recognise and I connected it to my server farm through Central Administration. It seems to have connected successfully but the content does not appear. Can anybody think what I may have done wrong?

    Cheers

    Paul

    Wednesday, September 25, 2013 3:53 PM

Answers

  • My command was incorrct. It should have been Mount-SPContentDatabase
    • Marked as answer by runnerpaul Thursday, October 10, 2013 11:58 AM
    Thursday, October 10, 2013 11:58 AM

All replies

  • You say the content does not appear, what do you get? a white screen? a 404? go into central administration and then application management -> content databases, and make sure your content database has at least one site collection inside it. Also note the domain relative URL of this site collection, so you can make sure your URL is correct when trying to browse it.

    Please mark my response as an answer if appropriate.
    Learn.SharePoint.com

    Wednesday, September 25, 2013 3:59 PM
  • I can see that there is one site collection but I don't know where to check the domain relative URL.

    The screenshot below is what I get when I access the SharePoint:

    However, in my WSS 3.0 I get the following when usig the same content db:

    Thursday, September 26, 2013 7:54 AM
  • I came across the 'mount' command. Is this something I should be running?

    I tried to run it but got an error. Below is what I ran and the error I got:

    Am I correct in trying ths and if so can anybody please tell me what I'm doing wrong?

    Cheers

    Paul

    Thursday, September 26, 2013 9:49 AM
  • Oh, also I just noticed that there was a log file from when I attached the content database. It contained the below errors and warnings:

    [STSADM] [SPContentDatabaseSequence] [ERROR] [9/25/2013 3:32:48 PM]: Found a missing feature Id = [75a0fea7-9507-49c7-a473-0ce55c18ef89]
    [STSADM] [SPContentDatabaseSequence] [ERROR] [9/25/2013 3:32:48 PM]: The feature with Id 75a0fea7-9507-49c7-a473-0ce55c18ef89 is referenced in the database [WSS_Content_Base], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
    [STSADM] [SPContentDatabaseSequence] [ERROR] [9/25/2013 3:32:48 PM]: Found a missing feature Id = [75a0fea7-040e-4abb-b94b-32f1e7572840]
    [STSADM] [SPContentDatabaseSequence] [ERROR] [9/25/2013 3:32:48 PM]: The feature with Id 75a0fea7-040e-4abb-b94b-32f1e7572840 is referenced in the database [WSS_Content_Base], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
    [STSADM] [SPContentDatabaseSequence] [ERROR] [9/25/2013 3:32:49 PM]: Database [WSS_Content_Base] contains a site (Id = [f6ed1f51-c6d9-4f0a-b034-b778fb6cd3b8], Url = [/]) that is not found in the site map. Consider detach and reattach the database.
    [STSADM] [SPContentDatabaseSequence] [WARNING] [9/25/2013 3:32:49 PM]: The orphaned sites could cause upgrade failures. Try detach and reattach the database which contains the orphaned sites. Restart upgrade if necessary.
    [STSADM] [SPContentDatabaseSequence] [ERROR] [9/25/2013 3:32:49 PM]: Database [WSS_Content_Base] contains a site (Id = [f6ed1f51-c6d9-4f0a-b034-b778fb6cd3b8], Url = [/]) whose url is already used by a different site, in database (Id = [8e03758f-38a8-4e42-9884-6a696412140f], name = [WSS_Content_9010d726-0997-4fb4-b45c-5e4d27864a1f]), in the same web application. Consider deleting one of the sites which have conflicting urls.
    [STSADM] [SPContentDatabaseSequence] [WARNING] [9/25/2013 3:32:49 PM]: The orphaned sites could cause upgrade failures. Try detach and reattach the database which contains the orphaned sites. Restart upgrade if necessary.
    [STSADM] [SPContentDatabaseSequence] [WARNING] [9/25/2013 3:32:52 PM]: File [Features\SharePointBoost.Admin.SiteUserPlus\SiteUserPlus.dwp] is referenced [1] times in the database [WSS_Content_Base], but is not installed on the current farm. Please install any feature/solution which contains this file.
    [STSADM] [SPContentDatabaseSequence] [WARNING] [9/25/2013 3:32:52 PM]: One or more setup files are referenced in the database [WSS_Content_Base], but are not installed on the current farm. Please install any feature or solution which contains these files.
    [STSADM] [SPContentDatabaseSequence] [WARNING] [9/25/2013 3:32:57 PM]: WebPart class [7e287d59-ae87-2432-e52a-6420e81ddc91] is referenced [1] times in the database [WSS_Content_Base], but is not installed on the current farm. Please install any feature/solution which contains this web part.
    [STSADM] [SPContentDatabaseSequence] [WARNING] [9/25/2013 3:32:57 PM]: One or more web parts are referenced in the database [WSS_Content_Base], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
    [STSADM] [SPContentDatabaseSequence] [DEBUG] [9/25/2013 3:32:57 PM]: Web Part Type Id [c17f9896-5c01-bf29-48af-096fd218184e], referenced [1] times in the data, is mapped to [Microsoft.SharePoint.WebPartPages.UserDocsWebPart]
    [STSADM] [SPContentDatabaseSequence] [DEBUG] [9/25/2013 3:32:57 PM]: Web Part Type Id [404822d6-cc74-7e5c-6767-b8206c1490fc], referenced [1] times in the data, is mapped to [Microsoft.SharePoint.WebPartPages.SimpleFormWebPart]
    [STSADM] [SPContentDatabaseSequence] [DEBUG] [9/25/2013 3:32:57 PM]: Web Part Type Id [e60f6c95-e86c-4717-2c0d-6d8563c9caf7], referenced [1] times in the data, is mapped to [Microsoft.SharePoint.WebPartPages.ContentEditorWebPart]
    [STSADM] [SPContentDatabaseSequence] [DEBUG] [9/25/2013 3:32:57 PM]: Validating event receiver assemblies referenced in content database WSS_Content_Base that are installed.
    
    Thursday, September 26, 2013 10:31 AM
  • My command was incorrct. It should have been Mount-SPContentDatabase
    • Marked as answer by runnerpaul Thursday, October 10, 2013 11:58 AM
    Thursday, October 10, 2013 11:58 AM