Albatross1953
asked on
Windows Server 2012
I have a PC on a network with a server running Windows Server 2012 essentials. When we log on to that particular computer, we get a message that says: Logging configuration cannot be loaded. Logging has been disabled. We cannot open Devices & Printers & cannot print from that machine. The network printer was just replaced & had to be installed on the other PC's which was not a problem. I've rebooted the PC & logged in as different administrative users with the same results. Suggestions are appreciated.
ASKER
That link applies to Vista on a local PC. This is Win 7 on a Domain with Win Server 2012.
I did create a new admin user in the server & logged into that account but had the same results. I just found that the login message has occurred since the PC was installed but hasn't caused any problem with normal use. The Devices & Printers window not loading just occurred after the network printer failed. I did a System Restore to a point a few days before that happened, but nothing changed,
I did create a new admin user in the server & logged into that account but had the same results. I just found that the login message has occurred since the PC was installed but hasn't caused any problem with normal use. The Devices & Printers window not loading just occurred after the network printer failed. I did a System Restore to a point a few days before that happened, but nothing changed,
ASKER
I ran sfc.exe & it was unable to restore everything. The log is attached. I changed Bluetooth Service from Manual to Automatic. I booted in Safe Mode & then in Normal Mode.
CBS.log
CBS.log
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There was only one comment. It was a link that didn't apply to this situation.
http://answers.microsoft.com/en-us/windows/forum/windows_vista-security/user-profile-service-service-failed-the-logon-user/4ed66b21-c23e-42f1-98b2-706dcf931fae
Also let me know you are facing this issue with Domain ID's or local ID's