DesertDawg
asked on
Sharepoint
Without any warning I received a report on Monday from our SBS 2008 concerning a SharePoint error.
Event Details:
SQL Database ''SharePoint_AdminContent_ d4e397f2-a 27a-48a0-a 628-d25db6 672bab'' on SQL Server instance ''np:\\.\pipe\MSSQL$Micros oft##SSEE\ sql\query' ' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_AdminContent_d 4e397f2-a2 7a-48a0-a6 28-d25db66 72bab" requested by the login. The login failed. Login failed for user ''NT AUTHORITY\NETWORK SERVICE''.
Any recommendations on how to resolve this error? SharePoint stopped working at the same time.
Event Details:
SQL Database ''SharePoint_AdminContent_
Any recommendations on how to resolve this error? SharePoint stopped working at the same time.
ASKER
SBS2008 does have SQL and SharePoint on the same box. In fact, there is no choice. Yes, the previous administrator has traced this problem to a failed service pack install. I didn't know that yesterday.
I'm normally just the SQL guy. I asked over the cube wall, and my Sharepoint guy suggests running the Sharepoint Config Wizard. From what I've seen it looks like its the normal procedure after installing a service pack, and he indicates that -- worst case -- it shouldn't hurt anything.
ASKER
I'll give that a try then see where we go from there.
ASKER
Well, that didn't work. The wizard threw an exception two screens in. :(
Okay, I think some specific errors will need to be collected at this point. When the Service Pack failed to install, what specific errors were reported? When the wizard threw an exception, did it report anything?
I'll also say, we're getting beyond my area of expertise. I feel comfortable saying the problem is the Sharepoint Service Pack install... not SQL. Therefore I'd tend to want to redirect the question to the Sharepoint subtopic area, if possible.
I'll also say, we're getting beyond my area of expertise. I feel comfortable saying the problem is the Sharepoint Service Pack install... not SQL. Therefore I'd tend to want to redirect the question to the Sharepoint subtopic area, if possible.
ASKER
Thanks Razmus. I did get SharePoint up and running at the weekend by applying the service pack and other updates. However, I don't seem to be attached to the database.
What I need now is the instructions to re-set SharePoint to its' default settings within SBS 2008 as the SharePoint facilities have been little used in the past.
What I need now is the instructions to re-set SharePoint to its' default settings within SBS 2008 as the SharePoint facilities have been little used in the past.
ASKER
I've tried multiple methods to get the database connected but I'm still getting a signature error. Otherwise, all other settings seem fine.
The configuration tool is now running correctly but fails at step two.
The configuration tool is now running correctly but fails at step two.
When the configuration wizard fails, does it report a specific error?
ASKER
There's the usual server farm notification then it just hangs.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What is happening is IIS and thus Sharepoint are attempting to log into SQL using the Network Service account on the local box. This usually can work, and if they are on the same server, you can likely grant permissions to that built in account to get past that error. But, I believe there is some value in determining the underlying cause/source of the issue. Is there any chance that a Sharepoint Service pack was recently installed?