![]() ![]() There is always a COM+ event notification a few hours before the total system locks. We have it on Windows 2008 Standard & R2. #4SHADOW STUCK NOTIFICATIONS EVENT WINDOWS# Could it be network-related? Today, I tried to reach a computer on my network (within a terminal session). The server hung on this action (the computer nor network had problems, I could ping etc.). When I tried to logoff (in my terminal session), we got the "Please wait for the system event notification service". I tried the workaround from "rmoat", but I did not succeed to restart my server regularly. I could not stop the SENS-service (even not with the taskkill-command). It happens every two or three days and I can't find a situation in which it always happens. The only thing that helps me a bit, is NOT logging off in a terminal session, but just close it. The Com+ - event doesn't appear, but I don't wait for hours to reboot my server. Today we had the problem again, and this time, we had also a Com+ - event in our logs. We are using MS Communicator 2007 R2, but we have applied the last hotfixes and patches in the server and client side: We don't have any NIC Teaming actived and we have installed McAfee Virusscan 8.7 in one server, and no antivirus in the other to test it, and we are having the same issue in both of them. The remote desktop and citrix management console show the user as Active, but it can close the session.The users that have active sessions CAN work.When it occurs other users CAN log in, but any user that try log off get this message.One user get his session hang, so when we try to force close it we get the message "Waiting for system event notification service" and the user sessions never close.It is happenig every morning wince we put the second XenApp6 server on our new farm. #4SHADOW STUCK NOTIFICATIONS EVENT WINDOWS#.#4SHADOW STUCK NOTIFICATIONS EVENT CODE#. ![]()
0 Comments
Leave a Reply. |