SMS Log File Errors

This page details problems and issues relating to SMS Log File Errors.

'579' Errors in SMS_Executive and Site_Control_Manager Threads [28/1/01]
Discovery Data Manager Error 678 [3/1/01]
Error 0x80070005 in WNManual.log [1/12/00]
'Executing wbemsdk.exe' Last Entry in SMSSetup.log file when Installing a Secondary site [25/1/01]
'SMS_LOGON_SERVER_MANAGER failed to enumerate the NTLM shares' error in Logon Server Manager Log [13/1/03]

'579' Errors in SMS_Executive and Site_Control_Manager Threads

I'm getting a bucket full of 579 errors on a couple of different Primary servers :

(Could not write registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\xxxxx" on computer <servername>.
The operating system reported error 1332: No mapping between account names and security IDs was done.)

I'm getting this in both the 'SMS_Executive' and 'Site_Control_Manager' threads. Each is attempting to write into different Registry hives under the 'SOFTWARE\Microsoft\SMS\...' tree.

Anyone have a clue what's going on here?

Contributed By: Ed Aldrich, Cliff Hobbs
I've seen this error during site installations when there were domain controller connectivity delays. Synching the domain resolved the problem. In this case, synching the domain worked in one instance; in another, the WAN link back TO the domain was down at the time the thread attempted to update the Registry.

Discovery Data Manager Error 678

This is a nag-like error I'm getting on a number of site servers (Primary as well as Secondaries). It typically re-occurs on a monthly basis, and hits four or five times at essentially the same time. The only descriptive information is:

SMS_DISCOVERY_DATA_MANAGER Message ID:678 Description: Failed to update registry.

The time of occurrence is not coincidental with any automatic maintenance cycles that I can see.

This error occurs when the reporting (failing) site is unable to access the network (likely the PDC specifically, but I'm not sure of that added detail), when the update cycle occurs. I recently ran into this in my Brazil site(s) where I have a Primary and four Secondary child sites. All were reporting the same thing more or less at the same time and it turned out that at the time the errors were occurring, the Brazil servers were not seeing anything outside Brazil and their local Domain Controllers.

Error 0x80070005 in WNManual.log

When trying to manually install a client using SMSMAN the following lines are displayed in the WNMANUAL.LOG:

GetAccessiblePath failed for NAL path MSWNET:\\logon_point\SMSLOGON\SITES\site_code\. Error = 0x80070005
Warning: Unable to Check Assignment for site "site_code" - Access is denied.

Contributed By: Cliff Hobbs
This error can be seen in a NT Master Domain model where the Site Server is in the Resource Domain and the client to be installed is in the Accounts domain. Normally the default SMS NTFS permissions are sufficient.

However, there is one exception. Where the CAP is in one domain and the user account is in another, SMS sets the security rights through NTFS to the 'Users' and 'Guests' groups from the domain the CAP is a member of. If the CAP is in a Resource domain and the user accounts are in the Accounts domain, you need to grant NTFS permissions for the 'Domain Users' group from the Accounts domain to the CAP otherwise the installation may fail.

'Executing wbemsdk.exe' Last Entry in SMSSetup.log file when Installing a Secondary site

We had problems installing a Secondary site so we removed it. After the site was removed, we started to build a new Secondary Site on a different server, while we were at the location of the new Secondary Site. We connected to a share off of our Primary site server (across the WAN link), and started SMS setup, opting for a Secondary site.

Things progressed well for an hour or so, then we didn't see any progress in the Setup program. Checking the 'smssetup.log' on the new Secondary site server, shows the last entry as:

...executing wbemsdk.exe...

We decided to let it run overnight. It's been that way for 12 hours. I'm trying to troubleshoot what's gone wrong with the Secondary site installation. Any ideas? Both Primary and the new server otherwise appear to be functioning fine.

I have had this problem several times. Go into 'Task Manager' and end the 'wbemsdk' process. Watch the 'smssetup.log' to see the installation finish. Then after the install finishes go to the 'sms\bin\i386' directory and run 'wbemsdk /s /server'.

This will finish the installation. Then it will take a bit to get everything up to the Primary. I have been installing 100 Secondary sites in the last two weeks and have seen this a few times.

'SMS_LOGON_SERVER_MANAGER failed to enumerate the NTLM shares' error in Logon Server Manager Log

I have installed SMS 2.0 without any Service Packs (Evaluation CD) over a SQL 7.0 database in a Windows NT 4.0 Environment. The installation of both products was successful but when I start the process of configuring SMS to discover resources the Primary Domain Controller is not installed as a Logon Point.

I have spent a week trying to solve this problem but have found nothing that can help me or give some advice. The logs of the services NT_LOGON_MANAGER, NT_LOGON_INSTALLATION_MANAGER and NT_LOGON_DISCOVERY MANAGER says a Status message like

There's no suitable drive in \\(PDC SERVER) to copy the SMS logon files, please free some disk space

but actually the PDC has 5 drive letters and all have enough disk space, the one with less disk space is drive C: and actually contains 466 MB of free disk space.

Contributed By: Cesar Cabrera
I found the problem after reading the logs of the SMS services, specifically in the NT_LOGON_SERVER_MANAGER I found this message:

SMS_LOGON_SERVER_MANAGER failed to enumerate the NTLM shares in "PDC"

I then looked at Microsoft Knowledge Base article 215123 'SMS: SMS_LOGON_SERVER_MANAGER Fails to Enumerate Shares' which basically says to install the SMS Service Packs, which I did and now everything works.