Yup.  Very.

It is finally resolved.  I'll write a post-mortem in a bit.


On Mon, Jun 2, 2014 at 8:18 AM, Michael B. Smith <[email protected]>
wrote:

>  That's....odd.
>
> Sent from my Windows Phone
>  ------------------------------
> From: Richard Stovall <[email protected]>
> Sent: ‎6/‎2/‎2014 6:42 AM
> To: [email protected]
> Subject: Re: [NTSysADM] CRM 2011 SSL cert error - Completely down
>
>  Still no resolution.  The CRM people are handing it to the Windows team
> because they believe it is an issue with the IIS AppPool not being able to
> read the private key.  (Which is what it looked like all along.)  None of
> the known fixes are working, however.  Ugh.
>
>
> On Sun, Jun 1, 2014 at 10:09 PM, Richard Stovall <[email protected]>
> wrote:
>
>>  Yep.  I have done this before without trouble, but this time it's not
>> working.
>>
>>  I did get a call from PSS (apparently there's one CRM engineer on duty
>> on weekends) about an hour ago and he's (very politely) scratching his head
>> and having me repeat all the troubleshooting steps I've already gone
>> through.  Thanks for checking.  If we ever get this resolved, I'll post the
>> fix.
>>
>>
>>  On Sun, Jun 1, 2014 at 9:50 PM, Susan Bradley <[email protected]>
>> wrote:
>>
>>> Have you reran then claims config wizard and ifd config wizard after
>>> replacing the SSL cert ?
>>>
>>> (passed this onto a crm listserve)
>>>
>>>
>>> On 6/1/2014 11:01 AM, Richard Stovall wrote:
>>>
>>>> Any one out there using CRM 2011 on premise?  I have been for years and
>>>> went to replace an expiring SSL cert today and now cannot successfully
>>>> enable claims or IFD.  Getting the dreaded "keyset does not exist" error.
>>>>  I have granted the network service account access to the private key,
>>>> which is usually the answer, but this does not work in this case.
>>>>
>>>> I'm completely stumped and PSS is apparently not available to work on
>>>> CRM issues on weekends.
>>>>
>>>
>>>
>>>
>>>
>>
>

Reply via email to