?
Solved

Help with broken Companyweb!

Posted on 2012-09-04
16
Medium Priority
?
1,592 Views
Last Modified: 2012-09-15
Okay friends -- hopefully somebody out there can help.  In SBS 2008, can anybody tell me where the directories containing the data for the internal website are located in Windows?  (i.e. -- http://companyweb?  And I mean the actual directories -- not the sites in IIS.)  The search feature was not working so nobody could query a search for any results on the companyweb page.  Worse case to worst, WSUS 3.0 was uninstalled to remove the internal database as well uninstalling SharePoint services.  Reboot.  Reinstall WSUS to reinstall clean internal SQL databse and then a reinstall of SHarepoint services.  I have the companyweb back up and online but I need to reconnect the old site content back to the new site.  I have no idea where these directories are located so I can restore from volume shadow copy and hopefully figure out how to create a new site in IIS and reconnect.  Any takers out there?  HELP!

- Chris in San Antonio
0
Comment
Question by:chrisdodds
  • 9
  • 4
  • 2
  • +1
16 Comments
 
LVL 11

Expert Comment

by:kyodai
ID: 38363986
Standard is c:\inetpub - unless you configured something else.

Sharepoint or WSS is a totally different thing though - Sharepoint websites are not having any directory, the content is stored in an SQL database. As you cant find the dir my first guess is that your company page was a WSS based page, so if you really cleaned all SQL databases you effectively destroyed all content. I'd check the SQL if any databses are still existing.
0
 
LVL 12

Expert Comment

by:Seaton007
ID: 38364001
Web site files are usually located in DRIVE_LETTER:\inetpub\wwwroot
0
 

Author Comment

by:chrisdodds
ID: 38364073
Okay, so even worst case scenario -- assuming that the SQL database was removed, where is the directory that the MICROSOFT ##SSEE SQL database resides in?  If I know that, I assume I should be able to look at my shadow copies of that SQL db and copy the contents of last week's directory to another repository and from there re-establish a connection to that SQL db effectibely restoring the old website data content.  Yes?  Not that I know how to do that either, but first things first here; I need to find that database!
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 11

Assisted Solution

by:kyodai
kyodai earned 1000 total points
ID: 38364131
Standard dir should be like C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\
0
 

Author Comment

by:chrisdodds
ID: 38364235
I think I'm screwed.  Due to the ENORMOUS amount of data I was tasked with backing up daily (to the tune of 1.5 Tb), we purchased a copy of BackupAssist and I have it set to mirror to a USB drive.  That said, it does this once every day (but I have only enough room to backup the server and save only a single instance -- I do not have multiple days' worth of backups.  I can potentially restore back to last Friday with either the Backup Assist or using the previos versions of these directories, I can recover back to last Thursday.)  

Unfortunately, for some reason these directories do not allow me to recover anything prior to that date.  I assume that is because I uninstalled, rebooted and reinstalled these components and the earliest known instance of these data directories is now set forth from the date of the install?  This suuuuuucks.  I feel terrible about this, but it's not as if I didn't warn against this type of disaster recovery scenario when I recommended a backup solution.  However, the cheapest means by which to backup the server data won out over the ability to have multiple backups.  Now to go do some damage control.... :(
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38367892
Sharepoint and WSUS do share the same database file and it would be found here:
C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA (unless you've moved it to another directory via the SBS Management Console)

It is possible to recover the database if you have a copy of it, essentially by following the steps found here:  http://technet.microsoft.com/en-us/library/dd548329(v=ws.10).aspx

Jeff
TechSoEasy
0
 

Author Comment

by:chrisdodds
ID: 38368821
TechSoEasy -

Thanks so much for this post.  I have not yet informed the client that all is lost and was hopefuly somebody might have some other input before I do so.  In looking in the default repository, I see multiple files from dates prior to when I removed SharePoint and reinstalled.  However, whenever I type in the command "np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query" (as per the MS technet link you posted), I see multiple databases but I'm pretty sure that of them all, the one I need is not there.  With that being said, I also see the .mdf file and .ldf file that pertain to the website prior to the hiccup.  Is there a means by which to get that data back into a database?  With your previous post I'm closer, but I'm not sure I'm out of the woods just yet.  Any further assistance is greatly appreciated.

- Dodds
0
 

Author Comment

by:chrisdodds
ID: 38370832
Okay, I'm making progress.  I have been successful in bringing up my company database in SQL Server Management Studio Express and I am now attempting to follow the instructions contained on the webpage from the link above.  I have been successful in doing everything up until it asks me to:

a.Run the following SQL command to set the database offline: alter database [db1] set OFFLINE with ROLLBACK IMMEDIATE, where db1 is the name of the database that you are moving. You must include the brackets.

Question -- What exactly does this mean?  From where do I run this command? (and subsequent others?)  Go ahead and laugh because it probably seems really naive of me to ask that but I've tried running it from the same place I ran the "np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query" command as well as from a CMD prompt (running as Administrator) and no luck.  Is there a SQL command line I should be using?  I feel like I'm so close, but so lost!  Help! (Again!)
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38370873
The command is run in SQL Server Management Studio Express.  Click New Query and enter the command as instructed.

Jeff
TechSoEasy
0
 

Author Comment

by:chrisdodds
ID: 38370904
I figured that out just before you posted this.  I am so confused.  You've pointed me on the right path, but this didn't work quite as it's laid out and thus, http://companyweb is still broken and I've worked another 2.5 hours with no more luck than I had before.  SharePoint is not my thing and this feels like learning to swim by being thrown into the ocean.  I'm going to have to reinstall Sharepoint (again) and start from scratch.  At least I know my .mdf file is here along with its logfile and certainly there must be some way to connect it to my internal website and restore it to its former state.  I may have to pony up and call Microsoft to get somebody to do this for me and I will watch.  I don't know what else to do.
0
 
LVL 74

Assisted Solution

by:Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy earned 1000 total points
ID: 38370912
Just be sure to follow the steps outlined here:
http://technet.microsoft.com/en-us/library/dd548327(v=ws.10).aspx

Jeff
TechSoEasy
0
 

Accepted Solution

by:
chrisdodds earned 0 total points
ID: 38383273
After Uninstalling WSUS (and the internal SQL database) and SharePoint Services 3.0 on SBS 2008, and reinstalling, and breaking, and uninstalling, and reinstalling, and breaking, and uninstalling, and reinstalling....  I was finally able to configure the http://CompanyWeb to use the old ***.mdf SQL database file.  Because I knew so little about SQL and SharePoint services prior to having this issue, it took me a lot longer to resolve due to the fact that I didn't realize I had the solution early on and didn't know fully how to implement it. Kyodai was invaluable with assisting me in finding the location of the actual data files that SharePoint uses on the SQL backend of the internal website.  Fortunately I chose NOT to remove the data files whenever I uninstalled SharePoint 3.0 and thus, the data file was in the default location of C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA -- it just took me a little while to figure out which one of these files it was that I needed.  Once I located the file and was sure I had a good copy of the data needing to be used as the default database for http://CompanyWeb, I followed a mix of steps from  Jeff's (TechSoEasy) post here:

http://technet.microsoft.com/en-us/library/dd548327(v=ws.10).aspx

but I found that what I really needed to do was to detach from the default database creeated when SharePoint 3.0 was reinstalled and connect to my company ***.mdf file and create a new site in SharePoint Central Administration by clicking on the "Applications Management" link (on the left) and then under "SharePoint Web Application Management", choosing "Create or Extend Web Application".  From there I followed Step 5 found here:

http://www.thehelpdesk.co.nz/2011/03/reinstallrepair-sbs-2008-companyweb.html

However, instead of using a known "good" backup of a working internal website form another server, I just plugged in the location of my desired SQL db when I got to step "n." --

n. Database Name: WSS_Content (leave as default).

I pointed the site to my SQL data file instead.  From there, I restarted all associated services and stopped the default "SharePoint - 80" website that was created upon reinstallation and started my new instance of the internal website.  Voila!  My old company website was back online and everything appeared to be working properly.  I'm not exactly sure if everything is as it should be, but it's back online and my client is happy.  Thanks to everybody who assisted and I'm awarding the points to Jeff even though I found the final solution on my own - I certainly could not have done this without his time and help in this resolution.
0
 

Author Comment

by:chrisdodds
ID: 38383289
x
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38385419
Awesome!  I can tell you that I learned about SQL in just about the same manner -- thought everything was lost never to return, and then VOILA! there it is!  

I am continually amazed by the resilience of the database files.  

Glad it worked out for you.

Jeff
TechSoEasy
0
 

Author Comment

by:chrisdodds
ID: 38385430
Jeff - you are a KING! Thanks again for all your responses and continued support. Wish you the best and maybe I'll see you around again...

- Doddsy
0
 

Author Closing Comment

by:chrisdodds
ID: 38401317
The final solution was a combination of tips shared by other admins and information mined online on my own and a lot of trial and error on my part.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Note:  There are two main ways to deploy InfoPath forms:  Server-side and directly through the SharePoint site.  Deploying a server-side InfoPath form means the form is approved by the Administrator, thus allowing greater functionality in the form. …
A while back, I ran into a situation where I was trying to use the calculated columns feature in SharePoint 2013 to do some simple math using values in two lists. Between certain data types not being accessible, and also with trying to make a one to…
Screencast - Getting to Know the Pipeline
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?
Suggested Courses

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question