autoupdate broke SBS2003R2

Hi

An autoupdate>> Product: Microsoft Windows Server Update Services 3.0 SP1 -
Update '{288B5E1C-79F5-4EEE-8C9E-998BE68F472F}' installed successfully.

Ran on an SBS2003R2, the system rebooted, and reported>>

Self-update is not working.

#50070: Unable to connect to the database STS_Config on dserevr\SharePoint.
Check the database connection information and make sure that the database
server is running.

The configuration of the AdminConnection\TCP protocol in the SQL instance
MICROSOFT##SSEE is not valid.

Verify that the Microsoft Exchange MTA service has started. Consecutive
ma-open calls are failing with error 3051.

An error occurred in attempting to send a Server Status Report in e-mail.
The e-mail message was not sent. There may be a problem with connectivity or
system configuration. Ensure that the ASP.NET State Service and IIS Admin
service are running. You can also try resetting your monitoring and reporting
preferences. To do this, open the Monitoring and Reporting taskpad in Server
Management, and then click Set Up Monitoring Reports and Alerts.

and stayed broken since then.

Any ideas as to what happened and how to repair this?

Thanks, David L. www.rabboar.com www.rbqaeng.com
.

Relevant Pages

  • Re: 3vl 2vl and NULL
    ... reporting, MV end-users were either churning out reports and ad hoc ... MV-database-independent applications as often as they do in the SQL ... where I cannot leave MV behind unless I can find a better data model. ... screen to be identical to the logical data model of the database. ...
    (comp.databases.theory)
  • Re: New Computwer with "Office with Access"
    ... Alpha 4 I found interesting at the time, ... Filemaker was a pretty good database from a user standpoint. ... Reporting was easy too, and one of it's ... Perhaps more familiarity with it would help. ...
    (misc.news.internet.discuss)
  • Re: Reporing service failure
    ... I understand that when you tried to configure your database for your SQL ... Server Reporting Services, you encountered the logon failure error. ... And then configure your SSRS databases via Reporting Services Configuration ...
    (microsoft.public.sqlserver.security)
  • RE: Reporing service failure
    ... I understand that when you tried to configure your database for your SQL ... Server Reporting Services, you encountered the logon failure error. ... it was strange that the audit failure was for another user account NT ... And then configure your SSRS databases via Reporting Services Configuration ...
    (microsoft.public.sqlserver.security)
  • Re: Need an expert advice
    ... This is the only database used for both OLTP and custom reporting. ... Even with the reporting load moved to a different server, ...
    (microsoft.public.sqlserver.datawarehouse)