locked
A/V authentications service won't start RRS feed

  • Question

  • We are receiving this error on our EDGE server. Could someone please help with troubleshooting this error.

    A/V Authentication Edge Service could not be started.

    Exception: System.ArgumentException: Invalid Uri: parsing error; suspect character: '*'
    Parameter name: value ---> Microsoft.Rtc.Internal.Sip.SipException: Invalid Uri: parsing error; suspect character: '*'
    at Microsoft.Rtc.Internal.Sip.SipUri.ParseUriString()
    at Microsoft.Rtc.Internal.Sip.SipUri..ctor(String uri)
    at Microsoft.Rtc.Signaling.SipUriParser..ctor(String value)
    --- End of inner exception stack trace ---
    at Microsoft.Rtc.Signaling.SipUriParser..ctor(String value)
    at Microsoft.Rtc.Signaling.SignalingUri.CheckSipUriString(String uri, String argumentName, Boolean allowEmpty)
    at Microsoft.Rtc.Signaling.RealTimeEndpoint..ctor(String uri, String epid, Boolean disallowParameters)
    at Microsoft.Rtc.Signaling.SipPeerToPeerEndpoint..ctor(String uri, RealTimeServerConnectionManager connectionManager, SipTransportType defaultTransportType)
    at Microsoft.Rtc.MRAS.Core.CreateSipEndpoint(String serverFQDN)
    at Microsoft.Rtc.MRAS.Core.Initialize()
    at Microsoft.Rtc.MRAS.Core..ctor(ServiceStopHandler serviceStop)
    at Microsoft.Rtc.MRAS.Server.OnStart()
    Cause: Internal error.
    Resolution:
    Examine the details in the associated event log entry to determine the potential cause and report to Product Support Services.

    Monday, August 24, 2009 3:54 PM

All replies

  • Can you provide some information on your topology/configuration  such as the following information:

    1. Edge Server FQDN
    2. A/V Edge Role FQDN
    3. Authentication Service FQDN
    4. Certificate SN, SAN
    5. Is this an enterprise pool or standard ed?

    Also, try the following:
    1. Telnet to port 5061 on the front end server, does it connect?

    If you do not feel like posting that you can email me at markk at cdh dot com
    Mark King | C/D/H | MCTS:OCS | MCSE: Messaging | MCITP:Enterprise Administrator | CCNA
    Monday, August 24, 2009 6:27 PM
  • Often times this is caused by a certificate error. Please verify your certificates.
    Mitch Roberson |MCITP:Enterprise Server Admin, Messaging |MCTS:OCS with Voice Achievement |MCT
    Tuesday, August 25, 2009 2:19 AM
  • Are you using wildcards in your certificate like *.domain.com, in OCS is not often recommended to use this kind of character in cert request.

    Regards


    Amado Imperial
    Monday, August 31, 2009 12:10 AM
  • hi
    Any update for your issue.
    Hope it works now!

    Regards!
    Monday, August 31, 2009 8:55 AM
    Moderator