RE: EventID1000: #50070:Unable to Connect to Database - WSS 2.0

this issue cropped up again in the last week or so. Users notified me of the
problem today, and when I looked at the server app log I see that the errors
have been going on for a couple of weeks, just not bad enought for anyone to
advise me.

I wound up restarting the SharePoint timer service (owstimer.exe), and the
problem instantly disappeared. I've now scheduled a restart of this service
once a week and we'll see if that eliminates the problem for good.

Hope that helps someone.

"jj_in_atlanta" wrote:

Steven:

So far the problem hasn't recurred - after I set Central Admin and SPTimer
to use the same account.

I've still got my fingers crossed - in the past this problem has ceased for
some time, and then resurfaced.

Thanks for your assistance.

"Steven Cheng [MSFT]" wrote:

Hi Atlanta,

Have you got any progress on this? If you still haven't got it resolved and
require some quick assistance, I suggest you contact CSS for further
troubleshooting assistance.

Microsoft Support Engineer by contacting Microsoft Customer Support
Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
Organization: Microsoft
Date: Fri, 28 Mar 2008 03:29:36 GMT
Subject: RE: EventID1000: #50070:Unable to Connect to Database - WSS 2.0


Thanks for your reply Atlanta,

Yes, for the remove and reextend approach, I've noticed it maybe quite a
lot work for server that has lots of virtual servers/sites. To be careful
enough, I think you may first try it on one or two sites/virtual severs
that has suffereed the problem(after you've backup them correctly).

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: =?Utf-8?B?ampfaW5fYXRsYW50YQ==?= <jj_in_atlanta@xxxxxxxxxxxxxxxx>
References: <F53DF469-A81F-44AC-B57E-073F12CDFA07@xxxxxxxxxxxxx>
<yMJqfe9jIHA.360@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: EventID1000: #50070:Unable to Connect to Database - WSS 2.0
Date: Thu, 27 Mar 2008 06:39:07 -0700


I've seen that first post and I don't think there is anything in it that is
relevant - since my test application isn't getting errors reading from the
same database.

Also, most of the posts I see mention getting the error when reading the
SharePoint Configuration Database - my errors aren't reading the config
database, but rather individual content databases.

However, I'm not positive that it isn't related to the content database -
so
your last suggestion is interesting to me though I don't quite understand
it.
It sounds like it is saying to unextend/remove WSS from all the virtual
servers on the server, create a new configuration database, then re-extend
all the virtual servers?
I'm not sure this is practical for my environment as I have +200 virtual
servers, but it still might be worth investigating.

In the meantime I followed one of the suggestions in your second link, to
ensure that the Central Admin and SPTimer both use the same account and am
waiting to see if this has any longterm impact.

Thanks for your suggestions.

"Steven Cheng [MSFT]" wrote:

Hi Atlanta,

Regarding on this error, I've performe some research, and there are some
former issues with similar symptom. There are different kind of potential
causes. Here are some web threads mentioned some:

##50070: Unable to connect to the database <Database Name>
http://blogs.msdn.com/cgideon/archive/2006/05/24/605454.aspx

http://forums.msrportal.com/archive/index.php?t-625.html

Also, from one internal issue record, I found that it use the following
means to recover the problem:

====================
1. Use following address to access the virtual server settings and remove
WSS from
this virtual server:

<http://servername:Central Admin Port/vssettings.aspx?VirtualServer=WSS
site URL

2. Create a new configuration database for the whole WSS

3. Extend the virtual server mentioned in step 1 again.

4. Connect the virtual server with the original WSS database; remove the
new
created WSS database.
==================

seems it completely drop and create a new confguration database for the
sps
virtual server.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you.
Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent
issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each
follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.


--------------------
From: =?Utf-8?B?ampfaW5fYXRsYW50YQ==?= <jj_in_atlanta@xxxxxxxxxxxxxxxx>
Subject: EventID1000: #50070:Unable to Connect to Database - WSS 2.0
Date: Wed, 26 Mar 2008 06:56:00 -0700


I've got a WSS 2.0 server with lots of SharePoint Web applications on it.

Intermittently the event log shows the following errors:

#50070: Unable to connect to the database wss_DatabaseName on
dbServerName.

Check the database connection information and make sure that the database
server is running.

Where the DatabaseName varies - always a content database - never the
configuration database. (the config db is on a local SQL server, the
content
databases are on a separate SQL server)

The dba's aren't seeing any errors on the SQL side. Sometimes, when these
errors occur in the event log, a user accessing the affected site will
get
an
error on their screen saying the database is unavailable.

Yesterday I wrote a c# test app that constantly reads from one of the
tables
in one of the content databases. I ran the app on the SharePoint server -
it
has been running nearly 24 hours and has shown no errors reading from the
database, although the Event Log shows that SharePoint has thrown lots of
errors reading from that same database several times.

Any suggestions? this has been going on for about 1 week most recently,
and
I can't find any patterns.

Thanks




.

Relevant Pages

  • WSUS Errors after System state restored
    ... recover sufficiently and the server went off whilst running. ... no avail and in the end just restored system state from the backup. ... Connection to database failed. ... see Help and Support Center at ...
    (microsoft.public.windows.server.sbs)
  • Re: SharePoint Services 3.0 unable to display content
    ... When connecting to the original configuration database, ... The virtual server that is referenced here is not in the config database. ... I am 100% about the WSS. ... Microsoft Windows SharePoint Services 2.0 ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Inconsistent Schema Versions
    ... on the existing server, to try to force it to upgrade to the same version. ... Microsoft MSDN Online Support Lead ... Subject: Inconsistent Schema Versions ... The schema version of the database ...
    (microsoft.public.sharepoint.portalserver.development)
  • RE: Adding Full Text Search to SBS 2003 - Yes I have searched and Read Everything
    ... You receive a "The database this server is using does not support search" ... SQL Enterprise Manager. ...
    (microsoft.public.windows.server.sbs)
  • Restore WSS sites after disaster
    ... I lost the system disk of a server with a couple of WSS ... The database files files were located on a different disk. ... It seems that in order to restore a WSS site (with stsadm -o restore etc. ...
    (microsoft.public.sharepoint.windowsservices)