Hello,
I'm running Windows Server 2008 R2. Recently, apparently after installing some automatic updates when the server shutdown unexpectedly several odd errors occurred on the machine. First to be noticed was that faxes were no longer being received. Upon further checking, the fax service had stopped working, and could not be restarted, as had the Windows Event Log. After searching for a long time, a solution was found here: http://social.msdn.microsoft.com/fo.../thread/c75ae899-d05b-411d-a7f2-00fdd33b8589/
The subinacl.exe fix described in the post did not work, but the deleting of a corrupted windows log folder did, and the event log and fax services would start again.
I thought that my problem was solved, however the fax service is still broken.
In trying to configure the server to once again receive faxes with Windows Fax and Scan, as it had done just fine before, I came across another error. When setting up the first fax account by following the wizard initiated by selecting "new fax" for the first time, or by going through tools->fax accounts->add options, the wizard errors with this message: "There was an error in configuring the account. Please contact your administrator". Having looked at several other forums (this problem was much harder to find information on then the first error described), this solution seemed to be what several posts pointed to:
http://www.vistaheads.com/forums/mi...ax-scan/50649-fax-account-wizard-error-2.html
This solution involved deleting the registry keys for the accounts through regedit. I tried this, and it did not work.
There doesn't seem to be much more I can do. I was ready to try a system restore on the server, but apparently there haven't been any restore images saved, so even that isn't an option.
After being directed to this forum, I found this thread:
http://social.technet.microsoft.com...t/thread/73394a76-4dab-4f6b-abaf-b794c57a750c
However it's solution (which involved deleting more from the registry, and a hidden folder) did not work for me either.
This has turned into a huge problem, and I'm begining to feel desperate to solve it.
I'm running Windows Server 2008 R2. Recently, apparently after installing some automatic updates when the server shutdown unexpectedly several odd errors occurred on the machine. First to be noticed was that faxes were no longer being received. Upon further checking, the fax service had stopped working, and could not be restarted, as had the Windows Event Log. After searching for a long time, a solution was found here: http://social.msdn.microsoft.com/fo.../thread/c75ae899-d05b-411d-a7f2-00fdd33b8589/
The subinacl.exe fix described in the post did not work, but the deleting of a corrupted windows log folder did, and the event log and fax services would start again.
I thought that my problem was solved, however the fax service is still broken.
In trying to configure the server to once again receive faxes with Windows Fax and Scan, as it had done just fine before, I came across another error. When setting up the first fax account by following the wizard initiated by selecting "new fax" for the first time, or by going through tools->fax accounts->add options, the wizard errors with this message: "There was an error in configuring the account. Please contact your administrator". Having looked at several other forums (this problem was much harder to find information on then the first error described), this solution seemed to be what several posts pointed to:
http://www.vistaheads.com/forums/mi...ax-scan/50649-fax-account-wizard-error-2.html
This solution involved deleting the registry keys for the accounts through regedit. I tried this, and it did not work.
There doesn't seem to be much more I can do. I was ready to try a system restore on the server, but apparently there haven't been any restore images saved, so even that isn't an option.
After being directed to this forum, I found this thread:
http://social.technet.microsoft.com...t/thread/73394a76-4dab-4f6b-abaf-b794c57a750c
However it's solution (which involved deleting more from the registry, and a hidden folder) did not work for me either.
This has turned into a huge problem, and I'm begining to feel desperate to solve it.
