Re: Failed to get a SQL Server connection
- From: "Steve Thompson" <stevethompson@xxxxxxxxxxxxx>
- Date: Thu, 9 Nov 2006 10:51:57 -0500
"German Suazo" <German Suazo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0BE29291-31D6-4BE9-ADB0-CDE70CD2C1DF@xxxxxxxxxxxxxxxx
Hello! After we installed SMS 2003 SP2, we have some errors events on SMS
Components:
- SMS_DISCOVERY_DATA_MANAGER
- SMS_HIERARCHY_MANAGER
- SMS_INVENTORY_DATA_LOADER
- SMS_SOFTWARE_METERING_PROCESSOR
This is what we have:
- SMS Site Server based on SMS 2003 SP2, configured with Advanced
Security.
SMS is installed on a Windows Server 2003 SP1, and I already configured
DCOM
permissions, as says on this URL on Windows Server 2003 SP1 section
(http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/tfaq02.mspx#EMHAC).
This server has MP, RP, CAP, SLP and DP site system. We already did SMS
Server account, member of Domain Admins, and also gave Full Control over
AD
System Container.
- SMS Site Database is located on another server. Database is on a SQL
Server 2000 SP4, and the OS is Windows Server 2003 SP1. We already put SMS
Site server account as a local administrator on SMS Database Server.
We have checked SQL Server logs, but we did not find any errors related to
SMS Site Server.
Is there any configuration that we have to do on SMS Database Server? Or
is
there any other configuration to do on SMS Site Server?
These are the errors we got, and we don't want to continue to deploy SMS
Clients until we have solved this issues. We appreciate your help.
Error 2601 (SMS_DISCOVERY_DATA_MANAGER)
=======================================
SMS Discovery Data Manager failed to connect to the discovery database.
Possible cause: SQL Server problem.
Solution:
1. Review the immediately preceding status messages from this component
about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that SMS can access the SMS site database.
5. Verify that the SMS site database, transaction log, and tempdb are not
full.
6. Verify that there are at least 50 SQL Server user connections, plus 5
for
each SMS Administrator console.
If the problem persists, check the SQL Server error logs.
----------
Error 2600 (SMS_DISCOVERY_DATA_MANAGER)
========================================
SMS Discovery Data Manager failed to synchronize this site's deletions
with
all secondary site databases. When discovery data is deleted, the deletion
must be propagated to all secondary sites. In addition, any licenses
associated with the deleted resources must be revoked. Because secondary
site
data is not synchronized, more licenses will be used than is necessary.
Possible cause: SQL Server problem on this site or one or more secondary
sites.
Solution:
1. Review the immediately preceding status messages from this component
about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that SMS can access the SMS site database.
5. Verify that the SMS site database, transaction log, and tempdb are not
full.
6. Verify that there are at least 50 SQL Server user connections, plus 5
for
each SMS Administrator console.
If the problem persists, check the SQL Server error logs.
------------
Error 600 (SMS_DISCOVERY_DATA_MANAGER, SMS_INVENTORY_DATA_LOADER)
==================================================================
Failed to get a SQL Server connection. Either the SQL Server is not
running, or all connections have been used.
------------
Error 3303 (SMS_HIERARCHY_MANAGER)
=======================================
SMS Hierarchy Manager cannot connect to the SMS site database.
Possible cause: SQL Server problem.
Solution:
1. Review the immediately preceding status messages from this component
about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that SMS can access the SMS site database.
5. Verify that the SMS site database, transaction log, and tempdb are not
full.
6. Verify that there are at least 50 SQL Server user connections, plus 5
for
each SMS Administrator console.
If the problem persists, check the SQL Server error logs.
Thank you for the detailed explanation... couple of questions:
1) Did you switch the SMS security mode from standard to advanced at the
time of the upgrade to SMS 2003 SP2?
2) Is the management point & reporting point working OK?
3) If you check for current activity against your SQL Server, can you tell
that SMS is accessing the sms database? (from Query Analyzer - execute
sp_who2)
Steve
.
- Follow-Ups:
- Re: Failed to get a SQL Server connection
- From: German Suazo
- Re: Failed to get a SQL Server connection
- References:
- Failed to get a SQL Server connection
- From: German Suazo
- Failed to get a SQL Server connection
- Prev by Date: Re: SP 2 and Lagacy clients
- Next by Date: Re: Move SMS 2003 to another server
- Previous by thread: Failed to get a SQL Server connection
- Next by thread: Re: Failed to get a SQL Server connection
- Index(es):
Relevant Pages
|
