Sharepoint 3.0 - Log file big precipitating loss of data

kaptainkruft · 12-03-2008, 10:05 PM

I'm a complete newb with sharepoint. It was installed by a previous admin and houses our knowledge base.

I realise that the following things which happened were probably really bad ideas and more than likely precipitated a condition where recovery will be difficult, but I have faith in the community.

Anyway, the server in question (a P.O.S. beige box, Windows 2003 standard SP2) running an installation of Sharepoint 3.0 ran out of disk space.

Upon investigation it was discovered that it was the result of a file ending with .LDF in C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data called SharePoint_Config_6d974c08-b697-45ea-aae2-d1cc0c8772d4_log.LDF.

As it was impeding more important functions on the box, we moved it to another disk (after shutting down the SQL Server Express Edition service).

Now, this is where the problems begin.

Fired SSEE back up, no apparent problems. Fired up the config wizard which asked if we wanted to remove it from a server farm. It then did something which I am not entirely sure of.

Anyway, it said to run it again, which we did, and it proceded to go and make a nice new instance of the Sharepoint with default info in it.

Great. So, basically, from my wonderful description of my problem does anyone have any brilliant ideas on how to get the data from the old DB into the newly created DB?

If they can be accessed using any of the client tools (got them) then all's the better. I am not familiar with its DB structure, though I am familiar with SQL Server (yes, moving the log file seemed like a bad idea, as did starting the server again without it) but not with SSEE.

So, like I said, I have finished digging up. Any ideas?

12-03-2008, 10:05 PM	#1 (permalink)
kaptainkruft Registered User Join Date: Dec 2008 Location: Queensland, AU Posts: 1 OS: Windows 2003 Standard SP2	Sharepoint 3.0 - Log file big precipitating loss of data I'm a complete newb with sharepoint. It was installed by a previous admin and houses our knowledge base. I realise that the following things which happened were probably really bad ideas and more than likely precipitated a condition where recovery will be difficult, but I have faith in the community. Anyway, the server in question (a P.O.S. beige box, Windows 2003 standard SP2) running an installation of Sharepoint 3.0 ran out of disk space. Upon investigation it was discovered that it was the result of a file ending with .LDF in C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data called SharePoint_Config_6d974c08-b697-45ea-aae2-d1cc0c8772d4_log.LDF. As it was impeding more important functions on the box, we moved it to another disk (after shutting down the SQL Server Express Edition service). Now, this is where the problems begin. Fired SSEE back up, no apparent problems. Fired up the config wizard which asked if we wanted to remove it from a server farm. It then did something which I am not entirely sure of. Anyway, it said to run it again, which we did, and it proceded to go and make a nice new instance of the Sharepoint with default info in it. Great. So, basically, from my wonderful description of my problem does anyone have any brilliant ideas on how to get the data from the old DB into the newly created DB? If they can be accessed using any of the client tools (got them) then all's the better. I am not familiar with its DB structure, though I am familiar with SQL Server (yes, moving the log file seemed like a bad idea, as did starting the server again without it) but not with SSEE. So, like I said, I have finished digging up. Any ideas? __________________ stupidQuestion++;