Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 764
  • Last Modified:

Sharepoint Configuration Database Inaccessible

I am sure this has been asked a million times. Using SBS 2008 with WSS 3.0. Everything was working fine until some VSS wrtiers stopped working. Rather than running a script to try to fix them, I decided to update the server. I did this, and for whatever reason it fixed the problem. But, now I cannot access Sharepoint.

I receive the error message: Cannot connect to the configuration database.

The following error message is attached. I do have two accounts, both of which failed when trying to log into the Sharepoint Central Management (or whatever it is called).

 Error.txt
0
Bert2005
Asked:
Bert2005
  • 9
  • 7
1 Solution
 
Cliff GaliherCommented:
If you ran updates, you may have gotten bit by an issue where a sharepoint update fails to update the database, and the mismatch causes logins to fail. The official SBS team has posted a blog on resolving these issues.

http://blogs.technet.com/b/sbs/archive/2009/05/06/companyweb-inaccessible-after-sharepoint-3-0-service-pack-2.aspx

-Cliff
0
 
Bert2005Author Commented:
I don't think any of the updates were pertaining to sharepoint. There were quite a few though. When I ran the technology wizard it wanted me to disconnect it from the farm which kind of made me nervous. Thanks. I will cheek out your suggestions in the morning.
0
 
Bert2005Author Commented:
Updates on 5/4 just prior to Sharepoint's not working.

 Windows Updates
Do any of these seem like they should be rolled back?
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
Cliff GaliherCommented:
Have you read the blog post and tried its advice yet?!?
0
 
Bert2005Author Commented:
Read it. Haven't tried it yet. Was waiting until the business day was over. I just thought I would send these to you in case you thought any of them jumped out of you.
0
 
Cliff GaliherCommented:
Ahh. Okay, when you asked if something should be "rolled back" that is what triggered my concern. The ones that I notice are the SQL updates, since Sharepoint does rely on SQL on the back-end. But again, the blog post I provided should actually fix incompatibility issues without requiring any patch removal.

-Cliff
0
 
Bert2005Author Commented:
I tried everything with no success. I went to uninstall the SP4 for SQL Express which shows up in the attachment above but not in the window which allows you to uninstall. It is missing about four updates.
0
 
Cliff GaliherCommented:
SQL server service packs are usually one-way (cannot be uninstalled) because they make underlying changes to the database structure that cannot be reverted. that means that both the express SP4 and the Windows Internal Database SP4 cannot be individually rolled back. You'd be looking at restoring from backup to properly revert.

Before you go there though, did the psconfig command succeed or did it report back errors?

-Cliff
0
 
Bert2005Author Commented:
Thanks. Is it OK to run the psconfig command even though it seems to be for a different issue? Maybe that's a stupid question or I am just nervous.
0
 
Cliff GaliherCommented:
Actually, if you look at the KB article referenced in the blog post, KB 944267 (link: http://support.microsoft.com/kb/944267), you'll see that your issue is one of several issues covered by that KB article (count down about seven symptoms...they don't number them.)

But yes, it is always okay to run that command. In a healthy system all that happens is that psconfig comes back and says that the SharePoint databases are already up-to-date. In a system where the databases are not up-to-date, it updates them.

Now, as with *any* command or update that writes data to the hard drive, things *can* go wrong so HAVE A BACKUP!  ...but that doesn't mean the command is destructive or that it is unsafe to run. It is simply the standard precaution.

Should square you right up.

-Cliff
0
 
Bert2005Author Commented:
Here is the result. I kept hoping the zero would be a one.
psconfig.txt
0
 
Cliff GaliherCommented:
And, again, referring to the blog post, you've ensured the database is not read-only? The authentication issues listed in the error log are pretty straightforward and usually means either the database got marked read-only (happens as part of the upgrade, but is supposed to be undone at the end) or somehow the database is actually no longer allowing connections, which is *not* something a service pack ever changes.

....uh....speaking of which, as an aside, you are logged on as a domain administrator (preferrably the administrator accoutn created when SBS was installed) and you are using the "run as administrator" option when launching the command prompt?

-Cliff
0
 
Bert2005Author Commented:
I tried that awhile back, but I receive the attached error. Yes, I am using "run as administrator" when launching the command prompt? Yes, I am logged on as a domain admin.

I am not using the the default administrator account. I never have. Not sure if I know how other than use Administrator as the username. Wouldn't know the password.

Thanks, again, for all your help.
SQL-error.jpg
0
 
Cliff GaliherCommented:
Well, as you can see from that error, there are three possible culprits. Which, yes, if you have errors trying to follow a fix in a blog-post, those errors tend to be important. :) Probably could've saved a few posts back and forth.

Best to do as the error indicates and check the SQL server log to get the details of the error. If you are low on memory or disk space, steps will have to be taken to resolve that before the psconfig command will work. If it is a permissions issue, that matters as well.

And also, just to be sure, you are running the SQL management studio using "run as administrator" as well? That is also important...

-Cliff
0
 
Bert2005Author Commented:
Yep, running SQL management studio as admin. I have 30GB of free space. And, 20GB of memory. I will look for the error message.
0
 
Bert2005Author Commented:
Thanks Cliff.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 9
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now