Announcement

Collapse
No announcement yet.

Sharepoint Data Files Move Crashed

Collapse
This topic is closed.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sharepoint Data Files Move Crashed

    I received notifications from my 2008 SBS that drive space on C: was getting pretty low. Accordingly, I ran the Sharepoint Data Move Wizard from the SBS Advanced Concole. Unfortunately, half way through the move the wizard crashed. It did not say that the databases were unable to be moved, but rather it just straight up crashed. When I tried to run the wizard again, I received an error "403 forbidden" and it would not let me proceed. After looking around, it seems that half of the files from the C: drive store made it to the D: drive. My event viewer is freaking out and user's receive "cannot access database" errors when attempting to browse to the "companyweb" page. Any ideas?

    Will restoring the databases from my SBS backup resolve the issue? If not, do I need to repair or reinstall WSS 3.0? Does anyone have any information that might help me conduct the needed procedure? Thanks in advance!

    D

  • #2
    Re: Sharepoint Data Files Move Crashed

    move the files back manually, the restore the database.
    it can't hurt... it's already borken
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Sharepoint Data Files Move Crashed

      Originally posted by tehcamel View Post
      move the files back manually, the restore the database.
      it can't hurt... it's already borken
      Tehcamel,

      The files appear in both places, at least a subset of the files from the C: drive do. On the C: drive under "C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data" all original DB files and logs exist. Now, under "D:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data" , I have a subset of the files from the system drive, but not everything. Not all of the log and DB files made it over because the wizard crashed, so it's not a matter of simply copying them back to the original location - all of the original files, from what I can tell, are still on the system partition.

      I tried restoring the database and ran the repair from the SBS Disk 2 Component Repair, but that didn't help. Upon reboot, I tried to run the Sharepoint Config Wizard and it failed with an "unhandled exception". I didn't try to restore after the repair because I don;t want to break things more if I haven't already.

      I have the following events in the application log:

      Log Name: Application
      Source: Windows SharePoint Services 3 Search
      Date: 10/2/2009 10:05:12 AM
      Event ID: 2436
      Task Category: Gatherer
      Level: Warning
      Keywords: Classic
      User: N/A
      Computer: SERVER.DOMAIN.local
      Description:
      The start address <sts3s://HOSTNAME:987/contentdbid={6e76eccb-47da-41b4-9613-4c28e7806b63}> cannot be crawled.

      Context: Application 'Search index file on the search server', Catalog 'Search'


      Log Name: Application
      Source: Windows SharePoint Services 3 Search
      Date: 10/2/2009 10:05:12 AM
      Event ID: 2424
      Task Category: Gatherer
      Level: Error
      Keywords: Classic
      User: N/A
      Computer: SERVER.DOMAIN.local
      Description:
      The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

      Context: Application 'Search', Catalog 'index file on the search server Search'


      Log Name: Application
      Source: Windows SharePoint Services 3
      Date: 10/2/2009 10:00:06 AM
      Event ID: 3760
      Task Category: Database
      Level: Error
      Keywords: Classic
      User: N/A
      Computer: SERVER.DOMAIN.local
      Description:
      SQL Database 'ShareWebDb' on SQL Server instance 'SERVER\Microsoft##SSEE' not found. Additional error information from SQL Server is included below.

      Cannot open database "ShareWebDb" requested by the login. The login failed.


      Log Name: Application
      Source: Windows SharePoint Services 3
      Date: 10/2/2009 9:50:17 AM
      Event ID: 3355
      Task Category: Database
      Level: Error
      Keywords: Classic
      User: N/A
      Computer: SERVER.DOMAIN.local
      Description:
      Cannot connect to SQL Server. np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query not found. Additional error information from SQL Server is included below.

      Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.


      Log Name: Application
      Source: Windows SharePoint Services 3
      Date: 10/2/2009 9:31:03 AM
      Event ID: 5215
      Task Category: Timer
      Level: Error
      Keywords: Classic
      User: N/A
      Computer: SERVER.DOMAIN.local
      Description:
      Unable to connect to database. Check database connection information and make sure the database server is running.


      Log Name: Application
      Source: Windows SharePoint Services 3
      Date: 10/2/2009 9:31:03 AM
      Event ID: 6398
      Task Category: Timer
      Level: Error
      Keywords: Classic
      User: N/A
      Computer: SERVER.DOMAIN.local
      Description:
      The Execute method of job definition Microsoft.SharePoint.Administration.SPImmediateAle rtsJobDefinition (ID cde363b9-22ac-45f2-abcf-5b1aa9d622a7) threw an exception. More information is included below.

      Unable to connect to database. Check database connection information and make sure the database server is running.


      Here's the contents of both directories:

      System drive (C):

      08/13/2008 12:16 AM 517 A0A06B71-0438-4DD6-AAA1-1DA94EE09E5C.cer
      04/01/2009 12:26 PM 517 EFFF282F-DC61-4647-AF7B-A76DA487F3CF.cer
      03/20/2009 10:04 AM 517 FAEF5F50-A7B0-4798-BAF0-0B718E747063.cer
      11/10/2008 11:36 AM 517 FD5FE6EC-4225-44B0-B116-25352E82559C.cer
      10/01/2009 03:28 PM 4,194,304 master.mdf
      10/01/2009 03:28 PM 1,048,576 mastlog.ldf
      10/01/2009 03:28 PM 1,245,184 model.mdf
      10/01/2009 03:28 PM 24,969,216 modellog.ldf
      10/01/2009 03:28 PM 19,922,944 msdbdata.mdf
      10/01/2009 03:28 PM 7,077,888 msdblog.ldf
      11/24/2008 02:27 PM 524,288 mssqlsystemresource.ldf
      11/24/2008 02:27 PM 40,304,640 mssqlsystemresource.mdf
      09/21/2009 11:54 AM 30,605,312 SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab.mdf
      09/21/2009 11:55 AM 115,081,216 SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab_log.LDF
      09/21/2009 11:55 AM 6,488,064 SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6.mdf
      09/21/2009 11:55 AM 6,314,065,920 SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6_log.LDF
      09/21/2009 11:54 AM 33,751,040 ShareWebDb.mdf
      09/28/2009 01:01 AM 529,596,416 ShareWebDb_log.LDF
      10/01/2009 03:38 PM 24,182,784 tempdb.mdf
      10/01/2009 03:38 PM 40,239,104 templog.ldf
      10/01/2009 10:48 AM 11,730,944 WSS_Content.mdf
      10/01/2009 10:48 AM 8,585,216 WSS_Content_log.LDF
      09/29/2009 03:35 AM 26,411,008 WSS_Search_SERVER.mdf
      09/21/2009 11:55 AM 16,973,824 WSS_Search_SERVER_log.LDF

      Storage drive (D):

      10/02/2009 10:19 AM 30,605,312 SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab.mdf
      10/02/2009 10:19 AM 115,081,216 SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab_log.ldf
      10/01/2009 03:28 PM 6,488,064 SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6.mdf
      10/01/2009 03:28 PM 6,314,065,920 SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6_log.ldf
      10/02/2009 10:23 AM 33,751,040 ShareWebDb.mdf
      10/02/2009 10:23 AM 529,596,416 ShareWebDb_log.ldf
      10/01/2009 03:28 PM 26,411,008 WSS_Search_SERVER.mdf
      10/01/2009 03:28 PM 16,973,824 WSS_Search_SERVER_log.ldf


      From the modified dates, it appears the files on D: are being actively used! Any assistance is welcomed and appreciated. I have a backup of the Sharepoint data and need to get the application working again. Thanks, guys and sorry for the huge post!

      D
      Last edited by RaeKWoNCHeF; 2nd October 2009, 15:30. Reason: Additional File/Directory Contents Info

      Comment


      • #4
        Re: Sharepoint Data Files Move Crashed

        Every wizard creates a log file. find it and find out why it crashed and at what stage it crashed. Post it here if you need more help...
        TIA

        Steven Teiger [SBS-MVP(2003-2009)]
        http://www.wintra.co.il/
        sigpic
        Iím honoured to have been selected for the SMB 150 list for 2013. This is the third time in succession (no logo available for 2011) that I have been honoured with this award.

        We donít stop playing because we grow old, we grow old because we stop playing.

        Comment


        • #5
          Your exchange databases are already on D: as indicated by your output. The wizard fails because the other local drive C: does not have enough space to accommodate the exchange data.
          Apart from this you can take help of [MOD EDIT] It is the best tool that helps to rectify all the SharePoint related errors.

          [MOD EDIT - LINK REMOVED. Next time will be a ban]
          If the OP still has this problem 6 years on,. they probably have a lot more things to worry about.
          [/MOD EDIT]
          Last edited by Ossian; 8th September 2015, 11:39.

          Comment


          • #6
            Original post was 6 years ago. Thread closed.
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment

            Working...
            X