WNetAddConnection2 failed, SMS_EXECUTIVE dies unexpectedly
- From: W N <W N@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 21 Apr 2006 11:22:01 -0700
Giving you as much info as possible:
Pre:
Domain = WORK
User = sms
SMS installed on = SMS1
Domain Controller = DOMCONTR
1) Collections have hourglasses (alongside the computers icons) that never
seem to go away. Do not know when this started, but it's not my big concern,
my big concern is SMS_EXECUTIVE dying every time I try to run it or it
automatically runs (Every 1 hour, 2 minutes, and 42 seconds). I think the
hour glass issue is simply a symptom of the greater problem.
2) I made a change to Client Push Installation account username and password
while using SMS2003 without the latest service pack, realized the changes
weren't reflected, and updated to latest version.
3) I deleted the account in the Client Push Installation and then readded it
with proper username and password.
4) The account, "sms", can log into all the stations and shares that it
needs to.
5) System Event Viewer:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 4/21/2006
Time: 11:56:19 AM
User: N/A
Computer: SMS1
Description:
The SMS_EXECUTIVE service terminated unexpectedly. It has done this 206
time(s).
6) Security Event Viewer:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: 4/21/2006
Time: 11:56:52 AM
User: NT AUTHORITY\SYSTEM
Computer: SMS1
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name: sms
Domain: WORK
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: WORKSTATION
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 192.168.102.85
Source Port: 0
7) crash.log output:
EXCEPTION INFORMATION
Time = 04/21/2006 11:55:08.959
Service name = SMS_EXECUTIVE
Thread name = SMS_CLIENT_CONFIG_MANAGER
Executable = E:\SMS\bin\i386\smsexec.exe
Process ID = 6048 (0x17a0)
Thread ID = 5544 (0x15a8)
Instruction address = 7100be2c
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 00000002
for which it does not have the appropriate access."
Raised inside CService mutex = No
CService mutex description = ""
ON THIS: I noticed that there exists a KB article here:
http://support.microsoft.com/?kbid=872779
This article deals with the virtual address issue on the
SMS_DISTRIBUTION_MANAGER thread, however, so I figured it does not apply.
Another forum post here:
http://www.mcse.ms/message1717792.html
This one deals with SMS_INVENTORY_DATA_LOADER crashing. The "fix" indicates
clearing out items in the inbox, specifically in inboxes\datalodr.box and
inboxes\auth\datalodr.box
Since mine is with SMS_CLIENT_CONFIG_MANAGER I removed all the files in:
inboxes\clicfg.src and still have the same problems.
8) Here's the failure in the CCM.log:
~~ Doing Account Cleanup Operation .... $$<SMS_CLIENT_CONFIG_MANAGER><Fri
Apr 21 12:05:36.881 2006 Central Daylight Time><thread=3056 (0xBF0)>
~~ Processing domain WORK $$<SMS_CLIENT_CONFIG_MANAGER><Fri Apr 21
12:05:37.021 2006 Central Daylight Time><thread=3056 (0xBF0)>
~~ Trying each entry in the SMS Client Remote Installation account list~
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Apr 21 12:05:37.240 2006 Central Daylight
Time><thread=3056 (0xBF0)>
~~ Attempting to connect to administrative share '\\DOMCONTR\admin$' using
account 'WORK\sms'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Apr 21 12:05:37.256
2006 Central Daylight Time><thread=3056 (0xBF0)>
~~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
WORK\sms (0000052e) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Apr 21 12:05:37.459
2006 Central Daylight Time><thread=3056 (0xBF0)>
SMS_EXECUTIVE signalled SMS_CLIENT_CONFIG_MANAGER to stop.
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Apr 21 12:05:41.662 2006 Central Daylight
Time><thread=5500 (0x157C)>
I've never seen this "Account Cleanup Operation" in any Google searches. I
don't know what it is or what it does. I also don't know why it is trying to
run on DOMCONTR, the domain controller. Additionally, when doing a search for
files containing DOMCONTR in "inbox" I find no files.
9) I've went through and removed all mention of "sms" user in "Client Push
Installation" and "Software Distribution" and still have this exact error.
I'm thinking at this point it might be a database issue.
What I'd like to get answered is the following:
1) Where is this "sms" user and password being stored? The database? In a
file? If I could find it, I could ensure that it gets deleted if it was made
when I errantly added it on a previous SP level
2) Where is the entry for connecting to the domain controller being stored?
What is "Account Cleanup Operation"?
Thanks. If you need more info, please do not hesitate to ask and I'll find it.
.
- Follow-Ups:
- Prev by Date: Re: SMS is not seeing all computers
- Next by Date: Re: Can I copy the CCR?
- Previous by thread: why do program icons disappear?
- Next by thread: RE: WNetAddConnection2 failed, SMS_EXECUTIVE dies unexpectedly
- Index(es):
Relevant Pages
|
Loading
