SMS Site Server Errors

• CCR Error Code 1003 [01/06/04]
• DDM Hanging on a Specific DDR and Getting 2636 Errors [13/11/00]
• Dr. Watson REMODBC.EXE Error on Site Server [4/2/02]
• Error 1069 - Logon failure error [2/4/01]
• Error Message ID 10104: CCIM encountered an error while trying to copy config files [28/11/00]
• Error Message "Could Not Write Registry Key to HKLM...\Sites\<Site_id> on computer" [19/8/03]
• Event ID 2022 'Server was unable to find a free connection' [2/11/00]
• 'FATAL ERROR:' in SMS_BOOTSTRAP.LOG [2/11/01]
• Last Error Code=53 in CCRs for lots of Clients [21/03/05]
• 'Setup cannot compile MOF file' error when Installing SMS 2.0 [8/12/00]
• "Site xyz added to list of busy sites because there is no available address." [31/10/03]
• "SMSPROV DllCanUnloadNow - returning S_FALSE" in SMSProv.log [12/05/04]
• SMS Debugging Information [1/7/01]
• SMS_Collection_Evaluator reporting error message 3023, severity 16 [updated 22/2/01]

CCR Error Code 1003

Contributed By: Steven D'Aprix [MSFT]
If you're seeing this error message help is at hand...  [Go to article]
 

DDM Hanging on a Specific DDR and Getting 2636 Errors

Has anyone else seen an error with Discovery Data Manager hanging on a specific DDR and getting '2636' errors? I see that there's a Microsoft article on it but is says that it has been fixed in SP2, which is what we are running. When I delete the DDR, DDM resumes processing. Here's the error below. Any ideas?

SMS Discovery Data Manager failed to process the discovery data record (DDR)  "E:\SMS\inboxes\ddm.box\X8ZKS5XX.DDR", because it cannot update the data source.
Possible cause: On a Primary site, it is probably a 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.

Possible cause: On a secondary site, SMS Discovery Data Manager
AND
Microsoft SQL Server reported SQL message 8152, severity 16: String or binary data would be truncated.

The cause of this particular problem was the subnet description was too long (it was 'ICT0MS10 ALTERNATE SUBNET'). The column (I think that it was called 'Subnet_Name0') in the table in SMS 'Cust_Arch_6_Disc' was set to a maximum data length of '20'. And, our description was 25 characters long. We just increased the column size in SQL and the problem is GONE!!

The other fix to this problem is to remove 'public' from the SNMP community string in Network Discovery. Keep in mind that you won't discover SNMP devices though.
 

Dr. Watson REMODBC.EXE Error on Site Server

Contributed By: Cliff Hobbs [MVP SMS]
Here's how to troubleshoot Dr. Watson REMODBC.EXE errors on your Site Server ...  [Go to article]
 

Error 1069 - Logon failure error

When trying to start the SMS services, I'm seeing:

Error 1069 - Logon failure error

Check that the 'SMSService' account isn't locked out (as it was in this case).
 

Error Message ID 10104: CCIM encountered an error while trying to copy config files

Message ID 10104:

SMS Client Component Installation Manager (CCIM) encountered an error while trying to copy the site's client component configuration files from "\\SERVER1\CAP_ZUR\clidata.box\". The operating system reported error 2: The system cannot find the file specified.

Solution: Check the client account permissions to verify that the client has read permission to the Clifiles.box directory.

What should I check?

It looks like the lookup file ('CLIENT.LKP') in your 'clidata.box' is still referring to a '*.cfg' file which is not there anymore. The '*.cfg' files are used to force a hardware or software resync on the client. The '*.cfg' file is created when a corrupted inventory file was detected on the SMS server.

If you are seeing this problem on a lot of clients, you may want to perform a manual cleanup. Therefore, you should stop the 'Inbox Manager' thread and the 'Site Component Manager' service on the Site server. Also stop the 'SMS_EXECUTIVE' on all your CAPs.

On the SMS server , you then delete all files in the 'clidata.src' folder EXCEPT for 'cli_inst.cfg', 'clibase.cfg', 'caplist.ini'. Repeat this process on all your CAP's, but there you need to remove them in the 'clidata.box' (also DON'T delete the 'Notify' folder).

Once this is done restart your 'Site Component Manager' service on the SMS server, which will restart 'Inbox Manager' and the 'SMS_EXECUTIVE' on all your CAPs.

When new '*.cfg' files are created , a new lookup file will be created which will be in sync.
 

Error Message "Could Not Write Registry Key to HKLM...\Sites\<Site_id> on computer"

Contributed By: Cliff Hobbs [MVP SMS]
Seeing this error? This information from Peter Howard could help you resolve it… [Go to article]
 

Event ID 2022 'Server was unable to find a free connection'

Since installing my SMS server as a client/ DP I am getting the following error:

Event 2022: Server was unable to find a free connection 1 times in the last 60 seconds

The following Microsoft Knowledge Base Articles detail potential causes of this problem:

• 245080 'Receiving Multiple Instances of Event ID 2022'

• 245723 'Simple Schedule Inventory Always Runs at Midnight'

• 245077 'Computer Stops Responding with Event ID 2022'

This problem is basically caused  because the NT Server service is unable to keep up with the demand for connections. The problem can be caused by several things such as a lack of free hard disk space/ fragmented hard disks, all of your clients running inventory at the same time and flooding the network, amongst others.
 

'FATAL ERROR:' in SMS_BOOTSTRAP.LOG

When installing an SMS Secondary site remotely, the 'SMS_BOOTSTRAP.LOG' contains the following error:

FATAL ERROR: Cannot read the SMS Identification key from the local registry, bootstrap procedure aborted!

Contributed By: Cliff Hobbs [MVP SMS]
The 'SMS_BOOTSTRAP.LOG' file is only generated if the installation runs into a problem. In this case the installation was being performed on a NT Member Server. The Master Account 'Domain\Domain Administrators' group wasn't a member of the Local 'Administrators' group on the Member server. Adding this group in and re-installing the site cured the problem.
 

Last Error Code=53 in CCRs for lots of Clients

'Setup cannot compile MOF file' error when Installing SMS 2.0

Setup cannot compile MOF file D:\SMS\bin\i386\sms_schm.mof. Do you want to continue Y/N

When I click 'Yes', I get a further 3 MOF-file related errors and the installation continues. But when I open the SMS Administrator console I get the error message:

An error occurred........Invalid Services Pointer...

Has anyone good ideas?

A hotfix that resolves this problem is available from Microsoft.  See 221481 'FIX: WMI Fails to Install on Windows NT 4.0 SP 5 or Later' for details of this problem.
 

"Site xyz added to list of busy sites because there is no available address."

Contributed By: Stan White [MSFT]
If you’re seeing this in your Sender.log file then here’s a potential fix... [Go to article]
 

"SMSPROV DllCanUnloadNow - returning S_FALSE" in SMSProv.log

Contributed By: Eric Holtz [MSFT]
If you’re seeing this error in your SMSProv.log then you can safely ignore it... [Go to article]
 

SMS Debugging Information

Contributed By: sms admin
When an SMS 2.0 Server service or thread raises an exception (such as an access violation or stack overflow) no visible message should appear. Instead, the following items occur:

The service reports a status message (ID 669) for the component that raised the exception. You can view this message in Status Message Viewer.

The service creates an 'SMS\Logs\CrashDump\YYYYMMDD_HHMMSS_Service' folder, where 'YYYYMMDD_HHMMSS' is the date and time of the exception and 'Service' is the name of the service that raised the exception (for example, Smsexec, Sitecomp,or Smsdbmon).

If logging is turned on, the service copies all of the log files into the 'SMS\Logs\CrashDump\YYYYMMDD_HHMMSS_Service' folder.

Whether or not logging is turned on, the service also dumps an internal cache of log messages to files in this folder. Even if logging is not enabled, you still get the last 10 log messages from every thread of the service.

The SMS service that raised the exception checks to see if the 'C:\Die_evil_bug_die.sms' file existed when the service started. If it did not exist when the service started, the service stops. Site Component Manager restarts the service within an hour and server operation continues.

If the 'C:\Die_evil_bug_die.sms' file did exist when the service started, the service passes the exception back to the operating system. The operating system handles the exception like any other exception it receives from a program.

If the 'C:\Die_evil_bug_die.sms' files exists, the operating system checks to see if the 'HKLM\Software\Microsoft\Windows NT\CurrentVersion\AeDebug\Auto' Registry value is set to '1'. If it is set to '1', the operating system immediately carries out the next item in this list.

If it is set to '0', you see a dialog box that details the program error and prompts you to:

Click 'OK' to terminate the application.

-or-

Click 'Cancel' to debug the application.

If you do not want to debug the problem, click 'OK' and the service stops.

If you want to debug the problem, copy the debug symbols to the computer and make sure that the correct debugger will be started by the next item in this list, and then click 'Cancel'.

The operating system starts the debugger specified by the 'HKLM\Software\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger' Registry value. By default, this is Dr. Watson. If you install a debugger on your computer, the value is set to your debugger.

For optimal debugging of SMS:

• Make sure that the 'C:\Die_evil_bug_die.sms' file exists on your SMS site systems (your Site Server, remote SQL server, remote CAPs, etc.) before installing SMS.
   
• Make sure that the 'HKLM\Software\Microsoft\Windows NT\CurrentVersion\AeDebug\Auto' Registry value is set to '0'.

SMS_Collection_Evaluator reporting error message 3023, severity 16

Microsoft SQL Server reported SQL message 3023, severity 16: Backup, CHECKALLOC, bulk copy, SELECT INTO, and file manipulation (such as CREATE FILE) operations on a database must be serialized. Reissue the statement after the current backup, CHECKALLOC, or file manipulation operation is completed.

I have about 20 Collections configured (SMS 2.0 SP2) and each is scheduled to update every 2 hours, all at varying times. Could it be that the scheduled update is interfering with the backup?

A couple of possible resolutions:

• As all of your Collections are scheduled to update every two hours, the update task may be trying to run during the SQL backups late at night. 
  
  Use SQL Enterprise Manager and go to SMS databases and look at the tables therein. The culprit may be the relationship between the tables '_TEMP_RESCOLL_<sitecode_CollectionID>' and the corresponding '_RES_COLL_<sitecode_CollectionID>'
  
  This will be documented in the Collection Evaluator log ('COLLEVAL.LOG') where it will refer to the problem table. Occasionally when the temp tables are created they get scrambled. I found that deleting the '*TEMP*' table cleared up the problem.
   
• This problem can also be caused if there is a Database Maintenance plan defined in SQL Enterprise Manager that is backing the SMS database up. Changing this from being scheduled in Enterprise Manager to being scheduled in SMS eliminates the error message.