Ccmexec / Execmgr logs full of WTSQueryUserToken errors (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003



Message

swood -> Ccmexec / Execmgr logs full of WTSQueryUserToken errors (5/9/2007 11:12:05 AM)

I've noticed a few of my clients are getting

WTSQueryUserToken[2](SessionID=0) failed with GLE=1245

errors in their ccmexec and execmgr logs. All the other client logs are clean, no errors. This is since SP3 install. Is there a site reset in my future?



mcarriere893 -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (5/9/2007 11:35:03 AM)

Probably no user is logged on, when an operation is trying to be performed.. Not a concern I don't believe, unless "SMS" is trying to do something and it isn't getting done (ex an advert to run when no user logged is failing).

Check and see what is attempting to get processed, and see if there's a failure.



swood -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (5/9/2007 11:38:29 AM)

You know, that made me think that I forgot to set the Environment tab correct in the package! It was set to "only when a user is logged on". I'll change it and see if it still gives out the error. Thanks for the help!



swood -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (5/9/2007 12:17:07 PM)

Well, I'm still getting the error. Now I see it on all clients. If I restart CCMEXEC on a system the ccmexec.log
show

Registering endpoint notifications.
WTSQueryUserToken[2](SessionID=-1) failed with GLE=1008
WTSQueryUserToken[2](SessionID=-1) failed with GLE=1008
WTSQueryUserToken[2](SessionID=-1) failed with GLE=1008
Registering for Logon/Logoff notifications.
WTSQueryUserToken[2](SessionID=-1) failed with GLE=1008
WTSQueryUserToken[2](SessionID=-1) failed with GLE=1008
WTSQueryUserToken[2](SessionID=-1) failed with GLE=1008
No user logged on to console during RegisterForLogon.






bswenson325 -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (7/13/2007 12:59:15 PM)

I noticed the same problem on two servers so far.  What I had to do to fix was:
1.  run ccmclean
2.  run ccmdelcert
3.  del system32\VPCache Folder
4.  del the SMS Registry Key
5.  del the SMS Record for the server.
6.  run Discovery for Active Directory System Discovery
7.  refresh All Systems Collection
8.  push SMS Client out.
9.  (still had the error), but I ran the vb script that defines the mp server with an IP address. This fixed the problem

P.S.  I tried runing the vb script first, prior to totally deinstalling the SMS Client, but that did not fix the problem.

Observation, so far.  both servers were w2k3 sp1 with IIS 6.0 installed. 



SMSNewBee123 -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (1/8/2008 1:29:14 PM)

Hi there,

What exactly do you mean by " define the MP server with an IP address"..what does this do..and where can i find the vbscript that does this for me?

Any help is greatly appreciated as i am facing the same issue

thanks,
Adam



bwilms -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (1/8/2008 2:39:17 PM)

Me too.

I've been doing some heavy investigatory work on our client health.  I'm seeing this error on about a dozen clients right now.  These are Windows XP SP2 workstations, not servers.  I'm unable to figure out where it is coming from.



bmason505 -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (1/8/2008 5:03:42 PM)

I assume we see these on workstations and not servers.  I think it's what's trying to get the last console user data (System Console User).  No?

Anyway, I've seen no detrimental effects from the error message.  Software distribution & patching have been fine.



bwilms -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (1/9/2008 6:59:22 AM)

If it is associated with the System Console User, would it not show up in the InventoryAgent.log?

It might be due to the fact that I'm only looking at "unhealthy" clients, but I am seeing it on workstations that I can't get the SMS client functional.  I'll have to look and see if I'm getting it on clients that aren't giving me noticable issues.

Also, it appears in several logs: execmrg.log, SrcUpdateMgr.log, CcmExec.log, PatchUIMonitor.log, Scheduler.log, CAS.log



sheffron -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (1/9/2008 9:41:31 AM)

We are also seeing it on a number of healthy clients (servers and workstations) ever since the SP3 install. Agreed that there are no obvious detrimental effects or other symptoms at this point, but it is a little troublesome.  I am also curious about the vbscript that bswenson325 mentioned that sets the IP for the MP.

Uninstalling and re-installing client does not seem to have any effect for us either. If I had time to waste, I would contact PSS to see what they had to say...



ktu -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (6/5/2008 12:40:15 PM)

Run into this artical, may help for your problems.
http://support.microsoft.com/kb/917676

Thanks,
Kevin



criticalerror -> RE: Ccmexec / Execmgr logs full of WTSQueryUserToken errors (10/31/2008 4:48:30 PM)

That works. As soon as I made the reigistry change the error stopped.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.1835938