none
Front-End Server service (RtcSrv) fail to start RRS feed

  • Question

  • Hello all.

    I'm implementing a new Standard OCS2007 R2 on a Windows Server 2008 R2 server. On this first phase will only accessible inside our organization, so no Edge deployment yet.

    I found some weird problems when validating installation, because new users logged in well, but old users (pre-OCS2007 AD prep), although correctly enabled for UC, fail to log in. But that's just for intro purposes.

    As I was trying to figure this out, i notices that the Front-End service was stopped, and so i tried to start. but it fails with the following error:

    The Office Communications Server Front-End service terminated with service-specific error -1007781640.

    I found several info about similar errors, but none with this error nr.

    That's why I come to you.

    Can anyone help me with this issue?

    thanks


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 11:42 AM

Answers

  • Did everyone here apply CU6 which was released last week to your servers?  If so, you need to do the ocs2009-dbupgrade.msi immediately. 

    See here for the issue and resolution if you have applied CU6 either intentionally or via windows update.

    http://www.unplugthepbx.com/Lists/Posts/Post.aspx?ID=26

     


    Mark King | MCTS:UC Voice | MCSE: Messaging | MCITP:Enterprise Messaging | CCNA | www.unplugthepbx.com
    Monday, July 26, 2010 8:43 PM
  • Hello all.

    Thank you for al the help, and finally my FE as started.

    I just runned, again, the OCS2009-dbupgrade.msi in command line mode and after finished, stopped and started services one by one.

    I also did eliminate the HP TEAMING i had with my 2 NIC cards, and enabled only one NIC with the correct IP, DNS and Gateway.

    Anyway, I'm still having trouble with the Validation, because my already existent users, although OCS enabled, fail to authenticate with the following error:

    Failed to establish security association with the server: User paulo.marques Domain <domain>.local Protocol NTLM Server Bell.<domain>.local Target Invalidated

    Guess i have to continue my troubleshooting anyways. I also get a certificate error when login in Communicator.

     

     

     


    Paulo Marques - Computer Engineer - MCSE
    • Marked as answer by Ben-Shun Zhu Wednesday, August 11, 2010 7:55 AM
    Tuesday, July 27, 2010 9:24 AM

All replies

  • Have you installed the proper updates per KB 982021?  Please see the following article as support for Windows Server 2008 R2 requires several fixes.

    Mark

    http://support.microsoft.com/kb/982021/


    Mark King | MCTS:UC Voice | MCSE: Messaging | MCITP:Enterprise Messaging | CCNA | www.unplugthepbx.com
    Monday, July 26, 2010 1:15 PM
  • It would be possible for your to paste the event log pertaining to the service crash for further investigation?
    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    Monday, July 26, 2010 2:34 PM
  • Hello.

    Here is the "friendly" log from event viewer:

    - System

       
    - Provider
          [ Name] Service Control Manager
          [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
          [ EventSourceName] Service Control Manager
       
    - EventID 7024
          [ Qualifiers] 49152
       
      Version 0
       
      Level 2
       
      Task 0
       
      Opcode 0
       
      Keywords 0x8080000000000000
       
    - TimeCreated
          [ SystemTime] 2010-07-26T15:11:45.494611800Z
       
      EventRecordID 4030
       
      Correlation
       
    - Execution
          [ ProcessID] 484
          [ ThreadID] 584
       
      Channel System
       
      Computer Bell.<domain>.local
       
      Security

    - EventData

        param1 Office Communications Server Front-End
        param2 %%-1007781640

     

    In the meantime been checking all updates, and also dependencies with the WMI services, along with SECPOL for another error i'm getting on the event viewer.

    Thank you for all your interest in this, and all help is appreciated.


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 3:21 PM
  • did you moved OCS computer from default OU to other OU? including the other security groups from the default Users OU to different OU?


    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    Monday, July 26, 2010 4:13 PM
  • I didn't move any of the original installation.

    Everything was installed in this physical dedicated server, just for this purpose. I want to add a couple of things, that i'm not sure if they're related.

    I'm running this in a HP DL380G5 server with TEAMING configured for 2 onboard NICs. Can this be a problem?

    Another error i'm getting on the event viewer relates to the Response Group and is as follows:

    - System

       
    - Provider
          [ Name] OCS Response Group Service
       
    - EventID 31178
          [ Qualifiers] 34769
       
      Level 3
       
      Task 2001
       
      Keywords 0x80000000000000
       
    - TimeCreated
          [ SystemTime] 2010-07-26T16:32:51.000000000Z
       
      EventRecordID 3074
       
      Channel Office Communications Server
       
      Computer Bell.<domain>.local
       
      Security

    - EventData

        Bell.<domain>.local
        5061
        Microsoft.Rtc.Signaling.ConnectionFailureException - Unable to establish a connection.
        System.Net.Sockets.SocketException - No connection could be made because the target machine actively refused it 192.168.10.15:5061
        30

     

    I recreate the OCS certificate, but that didn't helped either.

    I also installed the updates from the ServerUpdateInstaller package, downloaded from the Microsoft website. Can this have installed something not supposed to in a Standard pool environment?

    Running out of ideas here. Please try to help me on this.

    Thanks


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 4:40 PM
  • You mean you'd applied this KB 968802? on the server? which regards to certificate, i believe you're using STD edition of OCS server and the certificate cname should be FQDN of OCS server name. just for FYI
    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    • Edited by Arun_Kumar Monday, July 26, 2010 4:51 PM
    Monday, July 26, 2010 4:45 PM
  • yes i did.

    i was following this KB 982021.


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 4:47 PM
  • Alright,

    Let try this.

    Download the OCS2009-DBUpgrade.msi from the below link.

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4

    using the msiexec command we need to extract the OCS2009-DBUpgrade.msi file.

     = > msiexec /a <path of OCS2009-DBUpgrade.msi> /TARGETDIR=<extract folder path>

    Example:

    c:\update>msiexec /a <c:\update\OCS2009-DBUpgrade.msi> /TARGETDIR=<c:\update>

    => cscript dbqfeupdate.wsf /sqlserver:SQLServerName /Role:SE /verbose

    Example:

    c:\update>cscript dbqfeupdate.wsf /sqlserver:SQLServerName /Role:SE /verbose


    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    • Proposed as answer by Arun_Kumar Tuesday, July 27, 2010 2:39 PM
    Monday, July 26, 2010 5:00 PM
  • i receive this error:

    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    LogFile is QFE_DbSetup.log
    Updating SE server database stored procedures. This will take a while ...
    cscript dbsetup.wsf /SqlServer:(local)\rtc /Role:se /Verbose
    .Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Failed to create SQLDMO.SQLServer object (
      name:        Error
      description: Could not create object named "SQLDMO.SQLServer".
      number:      -2147221164
      message:     Could not create object named "SQLDMO.SQLServer".
    )

    I introduced as the sql server, the same server as the ocs server, because it is a local instance of SQL running for OCS. I defined the fqdn name of the server. Not sure if this is the correct.


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 5:22 PM
  • No need to type the instance name for the SQL Server name.

    cscript dbsetup.wsf /SqlServer:<nameofOCSName> /Role:se /Verbose

     

    nameofOCSName = NetBios name of your OCS STD server name.


    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    Monday, July 26, 2010 5:29 PM
  • Just did that and no love...

    i'm climbing walls in here.

    I gather that there is one of the updates KB974571 that apparently makes all sort of mess within an OCS infrastructure

    From what i read, I only had to uninstall this update and reboot server, but this didnt work in my case.

    I'm trying to give you the most feedback i can remember about my OCS deployment, because last friday i only had issues during the validations (OCS), and the only stopped service was the Response group, today response group is running and not the front-end.

    This sucks. I was so carefull on this installation and now this. Don't get it.


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 5:39 PM
  • Okey, let me understand the current situation here.

    All the services running except FE service?

    Even after you uninstall KB974571 you need to run the OCSScanfix.exe on your server, have you done that?

    Could you please start the FE service and paste the detail fresh event log here for me to check little more further? and according to you, you had only applied this KB KB974571 ? there no further changes done on the server as per you knowledge?


    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    Monday, July 26, 2010 5:46 PM
  • That's correct.

    As i already stated, i followed the Microsoft procedure in order to comply my deployment with W2k8R2 supportability, and later i realise that one of the updates, created serious issues with OCS2007.

    I then uninstall this update, but didnt run OCSASNfix.exe again. Untill now. But didnt reboot server yet.

    I tried just now to start the FE service and this is the feedback on the System event viewer log:

    - System

       
    - Provider
          [ Name] Service Control Manager
          [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
          [ EventSourceName] Service Control Manager
       
    - EventID 7036
          [ Qualifiers] 16384
       
      Version 0
       
      Level 4
       
      Task 0
       
      Opcode 0
       
      Keywords 0x8080000000000000
       
    - TimeCreated
          [ SystemTime] 2010-07-26T17:51:26.857991500Z
       
      EventRecordID 4101
       
      Correlation
       
    - Execution
          [ ProcessID] 484
          [ ThreadID] 6804
       
      Channel System
       
      Computer Bell.<domain>.local
       
      Security

    - EventData

        param1 Office Communications Server Front-End
        param2 stopped
        5200740063005300720076002F0031000000

    Binary data:

    In Words

    0000: 00740052 00530063 00760072 0031002F
    0008: 0000

    In Bytes

    0000: 52 00 74 00 63 00 53 00 R.t.c.S.
    0008: 72 00 76 00 2F 00 31 00 r.v./.1.
    0010: 00 00 ..

    Do you think i should reboot the server after the ocsasnfix.exe?


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 5:57 PM
  • sorry...

    i miss this error too. I also got this on the system event viewer:

    - System

       
    - Provider
          [ Name] Service Control Manager
          [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
          [ EventSourceName] Service Control Manager
       
    - EventID 7024
          [ Qualifiers] 49152
       
      Version 0
       
      Level 2
       
      Task 0
       
      Opcode 0
       
      Keywords 0x8080000000000000
       
    - TimeCreated
          [ SystemTime] 2010-07-26T17:51:26.857991500Z
       
      EventRecordID 4102
       
      Correlation
       
    - Execution
          [ ProcessID] 484
          [ ThreadID] 6804
       
      Channel System
       
      Computer Bell.<domain>.local
       
      Security

    - EventData

        param1 Office Communications Server Front-End
        param2 %%-1007781640

    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 5:59 PM
  • Hi, I have the same issue, still stuck, I'll keep an eye on this thread :)

    Monday, July 26, 2010 6:53 PM
  • Yeah.

    This is weird. Been running OCS Best Practices analyzer see if some comes up, but no luck either.


    Paulo Marques - Computer Engineer - MCSE
    Monday, July 26, 2010 7:06 PM
  • Did everyone here apply CU6 which was released last week to your servers?  If so, you need to do the ocs2009-dbupgrade.msi immediately. 

    See here for the issue and resolution if you have applied CU6 either intentionally or via windows update.

    http://www.unplugthepbx.com/Lists/Posts/Post.aspx?ID=26

     


    Mark King | MCTS:UC Voice | MCSE: Messaging | MCITP:Enterprise Messaging | CCNA | www.unplugthepbx.com
    Monday, July 26, 2010 8:43 PM
  • I just did and fixed my issue. thanks!
    Monday, July 26, 2010 9:00 PM
  • Hi, h5tech, how did you fix it? Would you put up resolution to help others? Thanks,

    rochamarques,would you validate FE server again then put up errors here for troubleshooting.


    Best regards,
    Tuesday, July 27, 2010 7:23 AM
  • Hello all.

    Thank you for al the help, and finally my FE as started.

    I just runned, again, the OCS2009-dbupgrade.msi in command line mode and after finished, stopped and started services one by one.

    I also did eliminate the HP TEAMING i had with my 2 NIC cards, and enabled only one NIC with the correct IP, DNS and Gateway.

    Anyway, I'm still having trouble with the Validation, because my already existent users, although OCS enabled, fail to authenticate with the following error:

    Failed to establish security association with the server: User paulo.marques Domain <domain>.local Protocol NTLM Server Bell.<domain>.local Target Invalidated

    Guess i have to continue my troubleshooting anyways. I also get a certificate error when login in Communicator.

     

     

     


    Paulo Marques - Computer Engineer - MCSE
    • Marked as answer by Ben-Shun Zhu Wednesday, August 11, 2010 7:55 AM
    Tuesday, July 27, 2010 9:24 AM
  • The fix can be found here: http://www.unplugthepbx.com/Lists/Posts/Post.aspx?ID=26

    It is an issue with CU6 that requires the ocs2009-dbupgrade.msi prior to installing the CU6 service hotfixes.


    Mark King | MCTS:UC Voice | MCSE: Messaging | MCITP:Enterprise Messaging | CCNA | www.unplugthepbx.com
    Tuesday, July 27, 2010 12:11 PM
  • Paulo,

    Great finally you able to resolve the same, Now lets start a new thread for the new error


    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    Tuesday, July 27, 2010 2:40 PM
  • Thanks Mark A KING
    Christopher - |MCP Windows XP |MCITP:Server Administrator,Database Administrator,Ax2009 Installation & Configuration| CCNA ....
    Tuesday, October 12, 2010 1:35 PM
  • Hi

    My experience was as following:

    1. I had to extract using : msiexec /a e:\install\OCS2009-DBUpgrade.msi TARGETDIR="E:\INSTALL\NEW" <- NEW must not exist !!!
    2. I had to run CMD as administrator, go to E:\install\NEW and execute OCS2009-DBUpgrade.msi

    I was not able to execute: cscript dbqfeupdate.wsf /sqlserver:Name of SQL server /Role:SE /verbose <-

    it gave me error:

    LogFile is QFE_DbSetup.log
    Updating SE server database stored procedures. This will take a while ...
    cscript dbsetup.wsf /SqlServer:(local)\rtc /Role:se /Verbose
    .Microsoft (R) Windows Script Host Version 5.7
    Copyright (C) Microsoft Corporation. All rights reserved.

    Failed to create SQLDMO.SQLServer object (
      name:        Error
      description: Could not create object named "SQLDMO.SQLServer".
      number:      -2147221164
      message:     Could not create object named "SQLDMO.SQLServer".

    Wednesday, November 3, 2010 12:35 AM
  • Dear all.

    I also have problem when start Front-end server.

    I install SQL server 2008 on machine SQL server.

    and install OCS R2 Enterprise on machine OCS server.

    I also have install Microsoft SQL Server 2005 Client Tools on OCS server, but when run the following command:

    OCS2009-DBUpgrade.msi POOLNAME=poolname then receive message error "You must install Microsoft SQL Server 2005 Client Tools before you install Microsoft OFfice Communication server 2007 R2 (KB2032834)"

    Please help me.
    Thanks and BestRegard.!
    Tuesday, November 23, 2010 3:09 AM
  • Tuesday, November 23, 2010 3:09 AM