Quantcast
Channel: VMware Communities : All Content - VMware View
Viewing all articles
Browse latest Browse all 9103

View 6.2 Windows 7 Ent 64bit fails to log off some users

$
0
0

This has the effect of leaving them without a virtual desktop because view reports thtat they are currently logging off.

 

I was able to remotely look at the event log and I found this:

 

Log Name:      Application
Source:        Microsoft-Windows-EventSystem
Date:          12/18/2015 4:59:15 PM
Event ID:      4627
Task Category: Firing Agent
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      62-002.OBFUSCATED.local
Description:
The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978630-5B9F-11D1-8DD2-00AA004ABD5E} for publisher  and subscriber .  The subscriber failed to respond within 180 seconds. The display name of the subscription is "Explorer". The HRESULT was 80010002.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">  <System>    <Provider Name="Microsoft-Windows-EventSystem" Guid="{899daace-4868-4295-afcd-9eb8fb497561}" EventSourceName="EventSystem" />    <EventID Qualifiers="32768">4627</EventID>    <Version>0</Version>    <Level>3</Level>    <Task>18</Task>    <Opcode>0</Opcode>    <Keywords>0x80000000000000</Keywords>    <TimeCreated SystemTime="2015-12-19T00:59:15.000000000Z" />    <EventRecordID>39306349</EventRecordID>    <Correlation />    <Execution ProcessID="0" ThreadID="0" />    <Channel>Application</Channel>    <Computer>62-002.OBFUSCATED.local</Computer>    <Security />  </System>  <EventData>    <Data Name="param1">80010002</Data>    <Data Name="param2">Logoff</Data>    <Data Name="param3">{D5978630-5B9F-11D1-8DD2-00AA004ABD5E}</Data>    <Data Name="param4">    </Data>    <Data Name="param5">    </Data>    <Data Name="param6">Explorer</Data>    <Data Name="param7">180</Data>    <Data Name="param8">    </Data>  </EventData></Event>


Log Name:      Application
Source:        Microsoft-Windows-Winlogon
Date:          12/18/2015 4:57:14 PM
Event ID:      6005
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      62-002.OBFUSCATED.local
Description:
The winlogon notification subscriber <Sens> is taking long time to handle the notification event (Logoff).
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">  <System>    <Provider Name="Microsoft-Windows-Winlogon" Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />    <EventID Qualifiers="32768">6005</EventID>    <Version>0</Version>    <Level>3</Level>    <Task>0</Task>    <Opcode>0</Opcode>    <Keywords>0x80000000000000</Keywords>    <TimeCreated SystemTime="2015-12-19T00:57:14.000000000Z" />    <EventRecordID>39306348</EventRecordID>    <Correlation />    <Execution ProcessID="0" ThreadID="0" />    <Channel>Application</Channel>    <Computer>62-002.OBFUSCATED.local</Computer>    <Security />  </System>  <EventData>    <Data>Sens</Data>    <Data>Logoff</Data>    <Binary>00000000</Binary>  </EventData></Event>

 

Any ideas what is causing this?


Viewing all articles
Browse latest Browse all 9103

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>