?
Solved

On A recent SBS Install there seems to be no SQL instance created for either Updates or monitoring and reporting.

Posted on 2009-04-21
4
Medium Priority
?
701 Views
Last Modified: 2013-11-30
On SBS 2003 a recent install of which I have done many, clicking on Updates brings up a debug screen that says SQL server does not exist and when I go to Monitoring and reporting it shows the page cannot be displayed.....all this is quite strange as its a new install with only service packs applied..I am also getting an event log error of 421.  ... Also I have looked at my own server and I seem to have instances created under program file, sql server for MSQL$SBSMONITORING that is not on the new build.....  Ok Screens are posted below for both problems so hope you can help me with a solution to these as I have no explanation for these problems.

UPDATES SCREEN ERROR SHOWS -
Server Error in '/UpdateServices' Application.
--------------------------------------------------------------------------------

SQL Server does not exist or access denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  
SqlException: SQL Server does not exist or access denied.]
   System.Data.SqlClient.ConnectionPool.CreateConnection() +406
   System.Data.SqlClient.ConnectionPool.UserCreateRequest() +151
   System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +464
   System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
   System.Data.SqlClient.SqlConnection.Open() +384
   Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString) +311
   Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect() +567
   Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds) +226
   Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler) +17
   Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPMultipleResultSets(String spName, DBParameterCollection args, Type[] resultTypes) +198
   Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPGetConfiguration() +147
   Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load() +143
   Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration..ctor() +84
   Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args) +534
   Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args) +191
   Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetConfiguration() +45
   Microsoft.SBS.UpdateServices.DataProvider..ctor() +120
   Microsoft.SBS.UpdateServices.StatusPage.Utility.SyncInProgress(DataProvider dp) +155
   Microsoft.SBS.UpdateServices.StatusPage.formHome.Page_Load(Object sender, EventArgs e) +290
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Page.ProcessRequestMain() +750

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407

MONITORING AND REPORTING SCREEN SHOWS

The page cannot be displayed
An error occurred on the page you are trying to view.

--------------------------------------------------------------------------------

To work around this problem, perform the following steps. After each step, try again to access the page.

Ensure that the MSSQL$SBSMONITORING service is started.
Ensure that the server is not low on memory or disk space.
Restart the server.
Verify that the server is functional and that there are no system-wide problems.
Run the Set Up Monitoring Reports and Alerts task in the Server Management Monitoring and Reporting taskpad

EVENT LOG ERROR SHOWS - EVENT 421 - source = update sevices
Connection to database failed. Reason=SQL Server does not exist or access denied.. Connection string: Data Source=SVR-PTCOMMS\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100



 
0
Comment
Question by:stuart-CDSLTD
  • 3
4 Comments
 
LVL 12

Assisted Solution

by:Chris M
Chris M earned 80 total points
ID: 24202259
Hi, The above erros simply mean that you are either trying to connect to the wrong instance, SQL server not running or you simply do not have access to it
Let me know which version of SQL server are you running. SQL 2000 or SQL 2005.
It also looks like you're talking about two different named instances as follows:
One instance is named "MONITORING"  based on your first paragraph's description MSQL$SBSMONITORING and the other you seem to connect to is named "WSUS", based on the instance name SVR-PTCOMMS\WSUS in the connection string
Connection string: Data Source=SVR-PTCOMMS\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100
Based on that, you could be trying to connect to the wrong instance name, which probably does not exist.
Ensure that you're connecting to the right instance, and that it's running. And finally ensure that you connect to SQL with an account that has all required privileges for your operations.
Test connectivity first using a SQL client, also test permissions/privileges on SQL.
It's best that you use SA for DB access or any other account with admin rights on the instance while installing.
If the above does not work, go to the command propmt and run this command "NET START" (without quotes) and then send us the output.
Also open services management snap-in (under administrative tools) and list all services whose names start with SQL or MSSQL
From here, I will be able to solve this.
regards,
Chris Musasizi
 
0
 

Author Comment

by:stuart-CDSLTD
ID: 24205883
Hi Chris - Thanks for the help

The server is running SQL 2005 express sp3
I'm not 100% sure what you are asking me to do above with SQLi'm not proficient with SQL i'm afraid  but I do have the details you requested.

NET START - DETAILS BELOW

These Windows services are started:

   Application Experience Lookup Service
   Application Layer Gateway Service
   Automatic Updates
   COM+ Event System
   Computer Browser
   Cryptographic Services
   DCOM Server Process Launcher
   DHCP Client
   DHCP Server
   Distributed File System
   Distributed Transaction Coordinator
   DNS Client
   DNS Server
   Error Reporting Service
   Event Log
   Fax
   File Replication Service
   Help and Support
   HTTP SSL
   IIS Admin Service
   Intuit QuickBooks FCS
   IPSEC Services
   Kerberos Key Distribution Center
   License Logging
   Logical Disk Manager
   Messenger
   Microsoft Exchange Information Store
   Microsoft Exchange Management
   Microsoft Exchange Routing Engine
   Microsoft Exchange System Attendant
   Microsoft Search
   MSSQL$SBSMONITORING
   MSSQL$SHAREPOINT
   MSSQL$SOPHOS
   Net Logon
   Network Connections
   Network Location Awareness (NLA)
   NT LM Security Support Provider
   Plug and Play
   Print Spooler
   Protected Storage
   QuickBooks Database Manager Service
   QuickBooksDB17
   Remote Access Connection Manager
   Remote Procedure Call (RPC)
   Remote Registry
   Routing and Remote Access
   SBCore Service
   Secondary Logon
   Security Accounts Manager
   Server
   SharePoint Timer Service
   Shell Hardware Detection
   Simple Mail Transfer Protocol (SMTP)
   Sophos Agent
   Sophos Anti-Virus
   Sophos Anti-Virus status reporter
   Sophos AutoUpdate Service
   Sophos Certification Manager
   Sophos EMLibUpdate Agent
   Sophos Enterprise Manager Scheduler
   Sophos Management Service
   Sophos Message Router
   SQL Server (SQLEXPRESS)
   SQL Server Browser
   SQL Server VSS Writer
   SQLAgent$SBSMONITORING
   System Event Notification
   Task Scheduler
   TCP/IP NetBIOS Helper
   Telephony
   Terminal Services
   Web Usage Logging Service
   WebClient
   Windows Internet Name Service (WINS)
   Windows Management Instrumentation
   Windows Time
   Workstation
   World Wide Web Publishing Service

THE SERVICES THAT ARE LISTED ARE -

MSSQL$SBSMONITORINg - STARTED
MSSQL$SHAREPOINT - STARTED
MSSQL$SOPHOS - STARTED
MSSQL$WSUS - NOT STARTED AND WILL NOT START - I think this is where the error 421 above is generated from..

SQL SERVER (SQL EXPRESS) - STARTED
SQL SERVER ACTIVE DIRECTORY HELPER - NOT STARTED / MANUAL
SQL SERVER BROWSER -  STARTED
SQL SERVER VSS WRITER - STARTED
SQLAGENT$SBSMONITORING - STARTED
SQLAGENT$SHAREPOINT -  NOT STARTED / MANUAL
SQLAGENT$SOPHOS - NOT STARTED / MANUAL
SQLAGENT$WSUS - NOT STARTED / MANUAL

Hope this helps you to help me Chris.
Thanks again



0
 

Author Comment

by:stuart-CDSLTD
ID: 24232621
UPDATE -

I have removed and re-installed monitoring and this is now sorted.  The only issue I have now is the WSUS PROBLEM AND I STILL NEED HELP WITH THIS.
0
 

Accepted Solution

by:
stuart-CDSLTD earned 0 total points
ID: 24248356
Further Update

I have now resolved all of these issues.  I have uninstalled and re-installed Monitoring via SBSUNINSTALL METHOD and have uninstalled update services only and now re-installed WSUS 3.0  all seems to be working ok now....so i think the points are now mine...
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have a large data set and a SSIS package. How can I load this file in multi threading?
In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Suggested Courses

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question