I renewed our SSL and everything looked hunky dory but yesterday when the ol
d
one expired my app started failing. After digging for the reason I tried to
access the Discount Manager asmx page and I got the pop-up saying the cert
was expired.

Now for whatever reason the developers of our site used a non-standard port
for this web service. I've contact VeriSign and MS and this seems to be the
reason for the problem. Now I'm waiting for a call back from Commerce Server
support to assist with this issue but since that might be 24 or more hours
and our site is down. I thought I would see if anyone else might have some
input in getting the web services of FP1 to acknowledge the new cert.

Thank you

[ Post a follow-up to this message ]

Hi,

If the problem is likely the expired certificate getting cached, you
may manually delete it from the server's computer account's Personal
store: open mmc, add Certificates snap-in and select computer
account. Then you can see all the certificates used by Commerce/IIS
in Personal store.

Also is the incident in below article related to your case?

834438 Update VeriSign Web Server Certificates Now for IIS: An
expired VeriSign
http://support.microsoft.com/?id=834438

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

[ Post a follow-up to this message ]

Hi,

Thanks for the suggestions. I have already installed the new intermediate
cert in the KB articlce and deleted the old cert as you suggested.

The problem seems to stem from the port assignment 30443 for this web
service. I wasn't involved in the intial deployment and I'm trying to
understand how this can be addressed and why it was setup this way intially.

I see that a site was created called Commerece Business Management but there
is no directories in this vitual site. This directory has the correct
settings for the SSL port 30443 for the properties.

The FP1 modules are in the placed virtually as part of the site application.
There is  nothing in the properties to to read from this port. When I added
this port to the site it did not correct the problem.

So I'm still plugging away. Although I did make some changes to make the
site useable for time being.


""WenJun Zhang[msft]"" wrote:

> Hi,
>
> If the problem is likely the expired certificate getting cached, you
> may manually delete it from the server's computer account's Personal
> store: open mmc, add Certificates snap-in and select computer
> account. Then you can see all the certificates used by Commerce/IIS
> in Personal store.
>
> Also is the incident in below article related to your case?
>
> 834438 Update VeriSign Web Server Certificates Now for IIS: An
> expired VeriSign
> http://support.microsoft.com/?id=834438
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support

[ Post a follow-up to this message ]

Hi,

Sounds like the problem is specific. Since you've opened a support
incident of it, please work with our Commerce support engineer to
perform some deeper troubleshooting.

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no
rights.

[ Post a follow-up to this message ]