Microsoft App-V (SoftGrid) Error 44955 in Event Log under Windows 2008 R2
After installing the App-V-Server on Windows 2008 R2 i got the following error in the Application Event log:
”Certificate could not be loaded. Error code [-2146893043]. Make sure that the Network Service account has proper access to the certificate and its corresponding private key file.”
Event ID: 44955
Furthermore the following error is displayed under the System Event Log:
”A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x8009030d. The internal error state is 10001.”
Event ID: 36870
For the encryption of the App-V Client/Server communication a Computer-Certificate of the App-V-Server is used. When you open the Services-Panel you can see that the App-V-Server-Service uses “Network Service Account”.
This account has normaly no access to the Computer-Certificate so that the two errors are displayed in the Event Log. To Fix this error you have to give the “Network Service Account” “read” priviliges on the Computer-Certificate.
To do this just open a mmc, add the “Certificate” Snapp-In and choose “Local Computer”:
Now open “Personal” => “Certificates”. Then you can see the Computer-Certificate. Right click on the Certificate and open “All Tasks” => “Manage Private Keys”.
In the permissions add “Network Service” and activate only “read” acccess:
Accept everything with “Apply” and “OK”.
When you now restart the App-V-Service the error shouldn’t be displayed any longer.
Happy Application-Virtualisation 🙂
Hi Jan,
Thank a lot for this information. I am setting up a RTSPS App-V management server I encountered this problem today. Your solution worked fine and I was up and running today with my test App-V mgmt server.
I am linking you to my App-V troubleshooting area for this fix.
http://www.networknet.nl/apps/wp/app-v
Thanks a lot.
This post helped me solve a problem with my Exchange 2010 SP1.
The event was 36870, from source Schannel, but this post also solves that problem. The event content is the same, only the event ID and source change.
Just wanted you to know that 🙂
Thanks a lot!
Good to know – thanks