none
Cannot Start Lync Access Edge Server - %%-2146762487 RRS feed

  • Question

  • Upon failing to start the Lync Access Edge Server service, I went to the event viewer and found the following:  "The Lync Server Access Edge service terminated with service-specific error %%-2146762487."

    So far the only thing I've found while Googling was that it may be related to certificates. Other errors that appear in Event viewer after the service fails to start include:

    "The following fatal alert was generated: 48. The internal error state is 552."

    "The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate."

    Monday, August 6, 2012 4:29 PM

Answers

  • Hi,

    Looks like something wrong with the external public certificate. Please make sure all the edge extenal services FQDN in the public certificate SAN list. You can have a try to reinstall the public certificate again. Delete the external public certificate from the Edge server certificate folder in MMC. Then import Certificate again in the Certificate Wizard and assign the certificagte to the External Edge interface.

    If the external services port is grabed by other application, it also would cause this issue. Please have a check.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, August 8, 2012 2:29 AM
    Moderator

All replies

  • Did you install the Root Ca certificate on your Edge server?

    And is everything ok with the server certificate for teh Edge?

    Also the needed port 5061 for the Access Edge is not blocked from other applications?


    regards Holger Technical Specialist UC



    Monday, August 6, 2012 5:13 PM
  • Internal and external certs have been assigned. Can you be more specific with your question "And is everything ok with the server certificate for teh Edge?" Port 5061 has been added to the inbound windows firewall (sip/mtls tcp, action - allow, protocol - tcp, local port 5061).

    Monday, August 6, 2012 5:29 PM
  • Hi,

    Looks like something wrong with the external public certificate. Please make sure all the edge extenal services FQDN in the public certificate SAN list. You can have a try to reinstall the public certificate again. Delete the external public certificate from the Edge server certificate folder in MMC. Then import Certificate again in the Certificate Wizard and assign the certificagte to the External Edge interface.

    If the external services port is grabed by other application, it also would cause this issue. Please have a check.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, August 8, 2012 2:29 AM
    Moderator
  • Hi,

    Do you have any luck?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, August 15, 2012 3:01 AM
    Moderator
  • Hi, what I mean is, you should be sure, that the needed port ist not blocked from a other application like teamvieer, damewar, remote access software.

    If the acces service will nort start, normaly the certificate name is wrong or SAN is missing or the port/IP is blocked or mistyped in the topology.


    regards Holger Technical Specialist UC

    Wednesday, August 15, 2012 5:51 AM
  • Are you sure you trust the public CA provider ? check that the public CA's root is in the Intermediate Certification Authorities store on the local computer.

    Wednesday, August 22, 2012 7:44 AM
  • Hi Folks

    I landed on this post after receiving the exact same error code i.e. 2146762487, the issue was resolved in my case by adding the Intermediate certificate into the Intermediate Certificate Store(The root cert was already present)

    Hope this helps anybody else with the same issue!

    Regards

    Mike

    Tuesday, June 16, 2015 7:49 PM
  • My issue was resolved with the same step. after Adding the issuers CA certificate in the intermediate certificate store of the edge server. my issue was resolved. 
    Friday, July 12, 2019 7:29 PM