Re: Failed to get a SQL Server connection

Hi German,

I'd be curious to hear the results of the sp_who2 run against your
database...

In re-reading this email thread, I have a couple of other suggestions,
followed by another post I made today that concerned trouble accessing a
remote SQL Server device.

1) check that you have installed the SMS SQL database on the default
instance of SQL Server
2) check that you have installed all of the IIS prerequisite components for
the SMS site system roles
3) check that you have not installed or run the IIS lockdown template

finally:

Have you checked that you've defined a valid SPN for your database?
http://support.microsoft.com/kb/829868/en-us
http://support.microsoft.com/kb/886143/en-us

Also, on your site server, you may need to add an SQL Server client utility
(cliconf) TCP/IP alias pointing to the remote SQL Server.


ST

"German Suazo" <germans@xxxxxxxxxxxx> wrote in message
news:eH%231S6IBHHA.1196@xxxxxxxxxxxxxxxxxxxxxxx
Hello Steve!! Here are the answers to your questions.

1) Did you switch the SMS security mode from standard to advanced at the
time of the upgrade to SMS 2003 SP2?
R/ Actually, I installed SMS 2003 SP2, and when I was installing it, I set
it up with advanced security.


2) Is the management point & reporting point working OK?
R/ Well, they were working before, but I did a Site Reset, and after that,
I have problems with MP, trying to create Virtual Directories on IIS, and
I have error messages from SMS_MP_CONTROL_MANAGER component. The good news
is that there are no more error messages from SMS_DISCOVERY_DATA_MANAGER.
Only from Errors 3303 from SMS_HIERARCHY_MANAGER component and Error 600
from SMS_INVENTORY_DATA_LOADER component.
Here are the errors that I got from SMS_MP_CONTROL_MANAGER.

Error 4963

==========

MP Control Manager detected MPsetup has failed to create the CCM_Incoming
Virtual Directory.

Possible cause: The IIS IWAM account has expired, been disabled, or has
invalid or too restrictive logon hours. You may verify this information by
running the net user command line for the IWAM account. (i.e.: "net user
IWAMMachineName)

Solution: Use the output to verify that the account is enabled, and logon
is possible during the time of installation. Note: You can use "net user"
to modify the account properties.

Possible cause: The IIS IUSR account has expired, been disabled, or has
invalid or too restrictive logon hours. You may verify this information by
running the net user command line for the IUSR account. (i.e.: "net user
IWAMMachineName)

Solution: Use the output to verify that the account is enabled, and logon
is possible during the time of installation. Note: You can use "net user"
to modify the account properties.

Possible cause: The Default Web Site is disabled in IIS.

Solution: Verify that the Default Web Site is enabled, and functioning
properly.

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

Error 1020

==========

SMS Site Component Manager failed to reinstall this component on this site
system.

Solution: Review the previous status messages to determine the exact
reason for the failure. SMS Site Component Manager will automatically
retry the reinstallation in 60 minutes. To force SMS Site Component
Manager to immediately retry the reinstallation, stop and restart SMS Site
Component Manager using the SMS Service Manager.



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)
R/ I could not try to do it. I will try tomorrow.


Thanks.


"Steve Thompson" <stevethompson@xxxxxxxxxxxxx> wrote in message
news:%23KPl9bBBHHA.3368@xxxxxxxxxxxxxxxxxxxxxxx
"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





.

Relevant Pages

  • SMS 2003 MP Error to SQL Server
    ... I am getting the follwoing error in the SMS Console ... The SQL server site system is turned off, ... Verify that the SQL server site system is ... SMS Management Point does not have ...
    (microsoft.public.sms.setup)
  • Re: SMS_MP_Control_Manager Errors
    ... Manually restart the SMS Agent Host service on the MP. ... Verify that the SQL server is properly configured to ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Error Proxy Management Proxy
    ... Manually restart the SMS Agent Host service on the MP. ... MP encountered an error when connecting to SQL Server. ... Verify that the SQL server is properly configured to allow ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • MP is not responding to HTTP requests
    ... Manually restart the SMS Agent Host service on the MP. ... MP encountered an error when connecting to SQL Server. ... Verify that the SQL server is properly configured to allow ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Failed to get a SQL Server connection
    ... Use the output to verify that the account is enabled, ... SMS Site Component Manager failed to reinstall this component on this site ... Possible cause: SQL Server problem. ...
    (microsoft.public.sms.setup)