hi there
in my eventlog i found a warning about userenv and id 1512. After some warnings it switched to error.
searching for the eventid 1512 gets me this:
"Windows cannot unload your registry file. The memory used by the registry has not been freed. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. If this problem persists, contact your administrator."
At the Microsoft homepage is a tool for that problem :
http://www.microsoft.com/downloads/details.aspx?familyid=1b286e6d-8912-4e18-b570-42470e2f3582&displaylang=en
this tool installes a service that makes a cleanup. and it writes in the eventlog what programm or process did the lock. in my case it was kaspersky av and outpost.
Outpost causes eventid 1512 - mercebank.com - Powered by chcms::
hi there..in my eventlog i found a warning about userenv and id 1512. After some warnings it switched to errorsearching for the eventid 1512 gets me
http://mercebank.com/867/outpost-causes-eventid-1512-328867.htmHOME |
thought to let you know that if sombody has the same problem.
btw. is it a bug? is it known?
That's something you as a customer need to do directly since they may ask for further details. You may do so here: 1.
Good luck and please let us know what they say.
sorry to answer that late, but i had to clear some more important things than computers.
i use the updatefunction and outpost told me everything is up to date. some day i was on the homepage and found a new version and asked myself why this new version was not offered by the updatefunction.
but back to the problem. since the new version 375 the error is nearly gone. it only appears every 8 or 9 shutdowns.
from agnitum i heard nothing.
... In this case the slow logoff due to improper releasing of handles may be due to poor code from either MS or Agnitum. ... If this were to happen on a consistent and regular basis then I'd file a bug report.
i watched it now for about one month and yes, it occurs every shutdown. so it would be nice if you could contact agnitum for that one.
i also asked microsoft about that problem. they say it is due to agnitum and i should contact them. as for now i should use uphclean as i already do.
I've had it happen always but with 2.6 the problem seems to be gone for good now. Just wanted to report this.
Event logs are not always easily explained and most of the time the best approach is to ignore them. In this case the slow logoff due to improper releasing of handles may be due to poor code from either MS or Agnitum. I see it occassionally but, other then a bit of slowdown when releasing profiles on shutdown, I don't believe it causes any real harm. I ignore it when I see it. If this were to happen on a consistent and regular basis then I'd file a bug report. Installing UPHClean as you suggested will probably get rid of the error message but why overlay more code to solve something that's not really a significant problem. Anyway, that's my take on it.
 Microsoft Unleashes Visual Studio .NET
 IBM's iPhrase Buy Adds to WebSphere |
Outpost causes eventid 1512