terça-feira, 28 de dezembro de 2010 18:15
I have installed Forefront Protection Server Management Console in our test environment in Standalone Express configuration. Since the installation I have been seeing errors in the Application Event Log from the User Profile Service. Most of the errors are 1512: Windows cannot unload your registry file. The memory used by the registry has not been freed. This problem is often caused by services running as a user account. Try configuring services to run in either the LocalService or NetworkService account. DETAIL - The media is write protected.
I believe these are being generated from the Scheduled Tasks that were created when FPSMC was installed. The tasks are configured to run as a local user account (SMGR_SERVERNAME) that was also created during the install. Should I modify the Scheduled Tasks to run as Local System or is there a better way to fix these errors?
Todas as Respostas
sexta-feira, 7 de janeiro de 2011 18:55
I am seeing the same Error - Event ID: 1512 - and also, Information - Event ID: 1517
segunda-feira, 24 de janeiro de 2011 15:27Add me into the mix. I'm seeing the same thing.
Orange County District Attorney
terça-feira, 25 de janeiro de 2011 18:38I am also seeing the same errors/information in the Event log
sexta-feira, 25 de março de 2011 13:59
I get the same errors, I installed two different systems with the Console and they both show the same errors in the EventLog.
Any additional info would be welcome...
By the way, did any one ever try the User Profile Hive Cleanup Service (UPHClean) tool (as suggested on http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=1512&EvtSrc=Userenv&LCID=1033) ?
terça-feira, 19 de abril de 2011 20:40
Good question. I haven't seen these errors but it seems a fair amount of you have. Has anyone run that user profile hive cleanup service tool that Yves posted above. It sounds like that would do the trick.
FPMC does create default scheduled tasks on install and if you create any jobs it will create additional scheduled tasks to correspond to those jobs.
All of my scheduled tasks run as a user (domain\adminaccount) and I do not receive those application log entries.
quarta-feira, 20 de abril de 2011 17:01
I actually did some asking around about these events. Apparently, this is a byproduct of a Windows problem with Task Scheduler not logging off the username after running the scheduled task(s).
The tasks should run under the account you listed but that has nothing to do with the error so changing it will not resolve the issue. I was told that changing it to LocalSystem would break everything!
sexta-feira, 22 de abril de 2011 15:47I should also state that this error is benign...