locked
S4B Edge Access Edge service error - 1008124857 RRS feed

  • Question

  • Hi,

    I was wondering if someone could help me.

    I did a side by side migration from Lync 2013 to S4B. We never had an Edge server before so I am setting one up for the first time. I'm getting the following error when I try to start the Access Edge Service.

    Windows could not start the Skype for Business Server Access Edge on Local Computer. service-specific error code - 1008124857.

    The logs show event 7034:

    The Skype for Business Server Access Edge service terminated unexpectedly.  It has done this 4 time(s).

    - System

      - Provider

       [ Name]  Service Control Manager
       [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4}
       [ EventSourceName]  Service Control Manager
     
      - EventID 7034

       [ Qualifiers]  49152
     
       Version 0
     
       Level 2
     
       Task 0
     
       Opcode 0
     
       Keywords 0x8080000000000000
     
      - TimeCreated

       [ SystemTime]  2016-08-29T20:18:43.448315300Z
     
       EventRecordID 9888
     
       Correlation
     
      - Execution

       [ ProcessID]  480
       [ ThreadID]  3520
     
       Channel System
     
       Computer S4BEDG.####.com
     
       Security
     

    - EventData

      param1 Skype for Business Server Access Edge
      param2 4
       5200740063005300720076000000


    --------------------------------------------------------------------------------

    Binary data:


    In Words

    0000: 00740052 00530063 00760072 0000


    In Bytes

    0000: 52 00 74 00 63 00 53 00   R.t.c.S.
    0008: 72 00 76 00 00 00         r.v...

    Has anyone seen this one before? all other services are running without issue and I think I have my certs installed correctly. I even checked that the IP addresses of the server match the topology.

    I'm using a single IP/FQDN for Access Edge, Web Conferencing service, A/V Edge service.

    Monday, August 29, 2016 8:25 PM

Answers

  • I found it!

    Whoever configured Lync before me had an entry under SIP Federated Domains, even though there was never an Edge server. Removing it allowed the services to start.

    Thanks again for taking the time to help.

    • Marked as answer by Rdziedzic Monday, August 29, 2016 10:02 PM
    Monday, August 29, 2016 10:02 PM

All replies

  • Hi

    Check output Get-CsAllowedDomain. May be you added domain similar *.yourdomain.com or other your domain.

    Monday, August 29, 2016 8:32 PM
  • The Edge server is not on the local domain so I get the error:

    Cannot find information about the local domain.

    I was under the impression that it should not be in the domain and you should just set the Primary DNS suffix manually.

    Monday, August 29, 2016 8:35 PM
  • Yes, it true. You should run this command on Frontend Server.

    Yet. Did you configure DNS suffix on EDGE server? And did you add this A record to DNS?

    Monday, August 29, 2016 8:44 PM
  • Rdziedzic,

    Type Get-CsManagementStoreReplicationStatus on your front end server in powershell. Check to see if the edges show up as passing.

    Are all services down on your edge? Use Get-CsWindowsService on your edge to check.

    Please double check the edge external IP configuration in the topology again as well. Report back here when finished:)

    -Don

    Monday, August 29, 2016 9:29 PM
  • Hi Don,

    Get-CsManagementStoreReplicationStatus shows the edge server as replicating.

    Get-CsWindowsService

    Shows FabricHostSvc and RTCSRV as stopped. I am able to manually start FabricHostSvc. I'm assuming the Access Edge service is RTCSRV?

    My Internal and External IP addresses in the Topology match the servers addresses.

    Is it a problem that my internal/external are on the same subnet? They are on different Vlans.

    Int:10.1.4.0

    Ext:10.1.5.0

    Thanks for the help all

    Monday, August 29, 2016 9:54 PM
  • I found it!

    Whoever configured Lync before me had an entry under SIP Federated Domains, even though there was never an Edge server. Removing it allowed the services to start.

    Thanks again for taking the time to help.

    • Marked as answer by Rdziedzic Monday, August 29, 2016 10:02 PM
    Monday, August 29, 2016 10:02 PM