Unable to connect to database STS_Config on myservername\Sharepoin  
Author Message
nixie21





PostPosted: Sat Jan 06 21:04:45 PST 2007 Top

SBS >> Unable to connect to database STS_Config on myservername\Sharepoin Brand new install of SBS2003. After application of service Pack one and all
the windows critical and optional updates I receive an error message:

Auto-Started service is not running. SQLAgent$SBSMONITORING is not running.

I reran the monitoring wizard and it solved the problem after a reboot. But
on the next reboot the problem returned.

If I look in System Tools, Event Viewer, Application, I find an erroro on :
Windows SharePoint Services:
#50070 Unable to connect to the database STS_Config on
myservername\Sharepoint.
Check the database connection information and make sure that the database
server is running.

I need to fix and repair this problem so that I can move on to the premium
technologies Disk. I understand that my SBS server is supposed to be running
cleanly before the preimium technologies portion of the install.

Thank you in advance for your assistance.

Information Technology66  
 
 
Kevin





PostPosted: Sat Jan 06 21:04:45 PST 2007 Top

SBS >> Unable to connect to database STS_Config on myservername\Sharepoin Rock, check out this link for several possible solutions to your 50070
error.
http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=207

And then, once you have it resolved, I would strongly suggest that after
installing the premium CD, that you also plan to completely REINSTALL SBS at
least two more times. Reasons for doing so are posted here:
http://msmvps.com/blogs/kwsupport/archive/2006/08/17/107981.aspx

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"Rock" <EMail@HideDomain.com> wrote in message
news:EMail@HideDomain.com...
> Brand new install of SBS2003. After application of service Pack one and
> all
> the windows critical and optional updates I receive an error message:
>
> Auto-Started service is not running. SQLAgent$SBSMONITORING is not
> running.
>
> I reran the monitoring wizard and it solved the problem after a reboot.
> But
> on the next reboot the problem returned.
>
> If I look in System Tools, Event Viewer, Application, I find an erroro on
> :
> Windows SharePoint Services:
> #50070 Unable to connect to the database STS_Config on
> myservername\Sharepoint.
> Check the database connection information and make sure that the database
> server is running.
>
> I need to fix and repair this problem so that I can move on to the premium
> technologies Disk. I understand that my SBS server is supposed to be
> running
> cleanly before the preimium technologies portion of the install.
>
> Thank you in advance for your assistance.


 
 
Rock





PostPosted: Sat Jan 06 22:09:00 PST 2007 Top

SBS >> Unable to connect to database STS_Config on myservername\Sharepoin I'm troubled by the concept that a SBS03 install can be broken by windows
critical updates.

I followed the links you provided. I do have the referenced DATA file where
indicated.

Restarting the 'SharePoint Timer Services' did not solve the problem, it
returned after a reboot.

Is it true then that I need to do a registry edit on a clean install of
SBS2003?


(I do like the Triple Crown article, great idea)




"Kevin Weilbacher [SBS-MVP]" wrote:

> Rock, check out this link for several possible solutions to your 50070
> error.
> http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=207
>
> And then, once you have it resolved, I would strongly suggest that after
> installing the premium CD, that you also plan to completely REINSTALL SBS at
> least two more times. Reasons for doing so are posted here:
> http://msmvps.com/blogs/kwsupport/archive/2006/08/17/107981.aspx
>
> --
> Kevin Weilbacher [SBS-MVP]
> "The days pass by so quickly now, the nights are seldom long"
 
 
Kevin





PostPosted: Sun Jan 07 16:07:39 PST 2007 Top

SBS >> Unable to connect to database STS_Config on myservername\Sharepoin we have too many people installing SBS2003 that have not encountered your
situation, so it's unlikely that it was simply broken due to installing
windows critical updates. Also, you could have two exact servers (from a
hardware perspective) and one works and one doesn't.

the other suggestion in that link was to adjust the pre-requisite
dependencies for that service ... that's not a registry change, just a
service mgmt change. if that works, then I would go ahead and flatten and
reinstall SBS from scratch and see if the problem reappears.

I'm glad you liked my post!

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"Rock" <EMail@HideDomain.com> wrote in message
news:EMail@HideDomain.com...
> I'm troubled by the concept that a SBS03 install can be broken by windows
> critical updates.
>
> I followed the links you provided. I do have the referenced DATA file
> where
> indicated.
>
> Restarting the 'SharePoint Timer Services' did not solve the problem, it
> returned after a reboot.
>
> Is it true then that I need to do a registry edit on a clean install of
> SBS2003?
>
>
> (I do like the Triple Crown article, great idea)
>
>
>
>
> "Kevin Weilbacher [SBS-MVP]" wrote:
>
>> Rock, check out this link for several possible solutions to your 50070
>> error.
>> http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=207
>>
>> And then, once you have it resolved, I would strongly suggest that after
>> installing the premium CD, that you also plan to completely REINSTALL SBS
>> at
>> least two more times. Reasons for doing so are posted here:
>> http://msmvps.com/blogs/kwsupport/archive/2006/08/17/107981.aspx
>>
>> --
>> Kevin Weilbacher [SBS-MVP]
>> "The days pass by so quickly now, the nights are seldom long"


 
 
Gregg





PostPosted: Sun Jan 07 16:30:59 PST 2007 Top

SBS >> Unable to connect to database STS_Config on myservername\Sharepoin Rock,

What version of SBS 2003? if you had to manually install SP1, then you
should have the RTM version (first release). If so, do you have the old Disk
3 or the new one (folders dated **I think** 9/2003 or 12/2003?).

Typically, you should install Windows Server 2003, then the SBS components,
and finish the complete setup BEFORE you do critical updates. Just make sure
you have a firewall between the SBS and the Internet.

The SharePoint error you see may be caused by using RTM disk 3 instead of
the replacement: http://support.microsoft.com/kb/832880/en-us

Gregg Hill



"Rock" <EMail@HideDomain.com> wrote in message
news:EMail@HideDomain.com...
> Brand new install of SBS2003. After application of service Pack one and
> all
> the windows critical and optional updates I receive an error message:
>
> Auto-Started service is not running. SQLAgent$SBSMONITORING is not
> running.
>
> I reran the monitoring wizard and it solved the problem after a reboot.
> But
> on the next reboot the problem returned.
>
> If I look in System Tools, Event Viewer, Application, I find an erroro on
> :
> Windows SharePoint Services:
> #50070 Unable to connect to the database STS_Config on
> myservername\Sharepoint.
> Check the database connection information and make sure that the database
> server is running.
>
> I need to fix and repair this problem so that I can move on to the premium
> technologies Disk. I understand that my SBS server is supposed to be
> running
> cleanly before the preimium technologies portion of the install.
>
> Thank you in advance for your assistance.