Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
OCS A/V Edge Service not starting - strange error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've been setting up a separate OCS AV Edge server (already have the Access and WEbconf edge working as far as I know).  The AV Edge had been working for a few days (I was able to successfully make a call from an external client).  I tried it again last night and it wasn't working.  When I came into work to check out the server, I saw that the Office Communications Server Audio/Video Edge service wouldn't start.  It is set to start as .\RTCProxyService.  The OCS A/V Authentication service starts fine.

     

     

    Event Type: Warning
    Event Source: OCS A/V Edge Server
    Event Category: (1028)
    Event ID: 22021
    Date:  6/20/2008
    Time:  8:40:19 AM
    User:  N/A
    Computer: OCSAV
    Description:
    Failed to notify kernel mode driver of a settings change.

    Driver Name: RTCMRDrv
    Error code: 1450
    Cause: Driver is not responding in a timely fashion.
    Resolution:
    Report to PSS

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    As far as I know, nothing changed with the server - I'm the only one that has access to the server.

     

    Any thoughts?  I've tried rebooting.  I was going to try a re-install, but I thought I'd check here first.

     

    THanks....

    Friday, June 20, 2008 2:29 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Steven,

    Thanks for the reply - actually, I ended up opening a support case with Microsoft and they said it was an easy fix.  Turns out I had to go into the edge config and configure the interfaces - the drop down that used to have the IP address selected was blank - I had to click on it and select the correct interface and then everything was fine.  It would have been nice if the error message was a little more informative, but at least we are up and running now.

     

    • Marked as answer by Jared2958 Monday, February 2, 2009 10:04 PM
    Monday, June 23, 2008 1:58 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    I haven't seen this issue before with OCS but I've worked with kernel-mode driver issues and here's how I would go about isolating:

     

    Run kernrate.exe from the 2003 reskit without switches and let it run for a few minutes and then exit.  It will list the kernel mode drivers running on the system in order of cpu usage.  A pegged one might already clue you in on the cause.  Otherwise, you can disable one at a time in the registry or device manager until your error goes away and then either rollback the driver for that device or disable it for good if it's not required.

    Sunday, June 22, 2008 11:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Steven,

    Thanks for the reply - actually, I ended up opening a support case with Microsoft and they said it was an easy fix.  Turns out I had to go into the edge config and configure the interfaces - the drop down that used to have the IP address selected was blank - I had to click on it and select the correct interface and then everything was fine.  It would have been nice if the error message was a little more informative, but at least we are up and running now.

     

    • Marked as answer by Jared2958 Monday, February 2, 2009 10:04 PM
    Monday, June 23, 2008 1:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm glad you got it fixed - thank you for sharing your resolution.

    Monday, June 23, 2008 4:56 PM