Error 0x800708AD Plesk Server Accounts breaks SqlServer permissions too
I have that same problem (error 0x800708AD) but in my case, after that error happens, when you try to restart SqlServer 2005 Express service, it can't start because permissions.
After that, I have tested it in a virtual machine with a clean installed Windows Web Server 2008 and Plesk 9.5.2.
1.- Check that all works fine (sqlserver service ok, access to databases ok)
2.- Execute Plesk Reconfigurator > Repair Plesk installation > Plesk Server Accounts.
3.- Restart SqlServer service and it can't start anymore.
The errors in eventlog, in the order it happens:
Plesk Reconfigurator
System.Runtime.InteropServices.COMException (0x800708AD): The user name could not be found. (Exception from HRESULT: 0x800708AD)
at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
at reconfigurator.ADGroup.AddUser(trustee t)
at reconfigurator.CheckPleskAccounts.Run()
MSSQLSERVER Event ID 5123
CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'C:\Program Files\Parallels\Plesk\Databases\MSSQL\MSSQL.1\MSSQL\DATA\tempdb.mdf'.
MSSQLSERVER Event ID 17207
FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'C:\Program Files\Parallels\Plesk\Databases\MSSQL\MSSQL.1\MSSQL\DATA\tempdb.mdf'. Diagnose and correct the operating system error, and retry the operation.
MSSQLSERVER Event ID 17204
FCB::Open failed: Could not open file C:\Program Files\Parallels\Plesk\Databases\MSSQL\MSSQL.1\MSSQL\DATA\tempdb.mdf for file number 1. OS error: 5(Access is denied.).
Service Control Manager Eventlog Provider Event ID 7024
The SQL Server (MSSQLSERVER) service terminated with service-specific error 1814 (0x716).
We see that error really in the next reboot of the server, and with a BIG PANIC after trying to start the sqlserver without success after hours we must copy all the databases to another sqlserver and change all the webs to point to the new sqlserver (6 hours after).
With more patience, we discover that managing manually the permissions over the databases the service can start.
We have tried too in the virtual test machine the workaround of the top of that thread (to replace the reconfigurator.exe) but not solve the sqlserver permissions over the databases. The service can't start.
I have attached screen captures of errors.
Any workaround for returning the production server to its initial database permissions state?