Cant Setup SP2 for Forefront Crypt Init Failed error 0x80090016

Hi guys,

im trying to implement TMG SP2 on our accept servers.

The current situations is as follows:

1 EMS server, 1 Internal Array (2 servers) 1x external array (2 servers). Logging is done in a separate SQL server Database.

Current Version is TMG 2010 enterprise Update 1 Rollup 4.

Array is proxy chained upwards.

Ive succesfully upgraded the EMS server to the new version.

When installing SP2 on the first server in the internal array (Reporting server) the setup crashes at the action SetFwsrvSdToCSP

=========================

MSI (s) (34:84) [14:56:02:933]: Executing op: ActionStart(Name=SetFwsrvSdToCSP,Description=Sets the Firewall service security descriptor on the cryptographic service provider...,)
Action 14:56:02: SetFwsrvSdToCSP. Sets the Firewall service security descriptor on the cryptographic service provider...
MSI (s) (34:84) [14:56:02:936]: Executing op: CustomActionSchedule(Action=SetFwsrvSdToCSP,ActionType=25601,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) (34:8C) [14:56:02:938]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3645.tmp, Entrypoint: SetFwsrvSdToCSP
14:56:02 ISA setup CA INFO   : ENTRY: SetFwsrvSdToCSP, PID 4644 (0x1224), Current user is Domain\user
14:56:02 ISA setup CA ERROR  : Crypt.Init failed. Error=0x80090016
14:56:02 ISA setup CA ERROR  : SetFwsrvSdToCSP: SetFwsrvSecurityDescriptor. failed, hr=0x80090016

==========================

ive corrected the NTFS permissions on the folder C:\Programdata\microsoft\crypto\rsa\machinekeys.

restarted the server. Protected storage service is running, the server can contact other servers.

Can anyone give me a hint. I need to upgrade the rest of the servers before i can do this in production environment

also attached an image with the error on screen.

March 6th, 2013 5:11pm

We' ve removed all components from the server. SQL, TMG etc.

After that we installed TMG again. Joined the Array and now its working again.

Think some registry entries were corrupted or security missing.

If anyone had the same issues, what was your solution?


Free Windows Admin Tool Kit Click here and download it now
March 7th, 2013 2:16pm

The permissions are not set properly on the 'MachineKeys' directory.
July 13th, 2013 8:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics