MSOC - Stand-alone set-up KB967831 failed to install

Locked MSOC - Stand-alone set-up KB967831 failed to install

  • Monday, October 19, 2009 4:03 PM
     
     
    Hi all,

    I am attempting to install the stated kb with no joy, it fails everytime.  So what I have done so far.  Well first step i stopped all services, then yes, i again attempted the install.  You guessed thats why I am here, still no joy.  Next step.... Google, the recommended dose of medication was to install Message Queing as I am not using QoS.  Installed, now I cant even log into Communicator, ow dear Microsoft what have you done this time.  Read a second article installed
    KB972041, horrah, communicator has been revived making my users once again happy.  Now KB967831 is still an available update to install, still failing to install.  Has anyone stumpled across and fixed this issue.

    Thanks for your efforts
    Russell

All Replies

  • Tuesday, October 20, 2009 10:21 AM
     
     
    So to elaborate.  I stopped windows update service, removed old files, manually downloaded kb, installed kb,

    I have also downloaded the KB manually, installed succesfully, rebooted, communicator is fully functionally, ran wuauclt /detectnow strangely kb967831 is still available.

    Any thoughts ?
  • Monday, October 26, 2009 4:17 AM
     
     
    Can you check the file versions mentioned on the KB. I am sure multiple newer KBs have over written this KB, and you no longer ahould need to install this KB.

    Also is there is the even logs ?
  • Monday, October 26, 2009 8:09 AM
    Moderator
     
     
    Hi
    Agree with Sri, you can refer to below link
    http://support.microsoft.com/kb/967831/ 
    And check the version of below file distributes
    Exumrouting.exe  3.5.6907.9
    Microsoft.rtc.mras.dll  3.5.6907.9
    Rtcarcha.dll   3.5.6907.9
    Sipstack.dll    3.5.6907.9
    Wrtces.dll      3.5.6907.9


    Regards!
  • Friday, November 06, 2009 10:03 AM
    Moderator
     
     
    Hi
    Any update for your issue?
    Thanks for your share.

    Best regards!
  • Tuesday, December 08, 2009 9:35 AM
     
     Answered

    Hey it was as simple as not installing the update, i found an article which unfortunetly i did not keep hold of the link for the purposes of this post, although what happens is the communications server switchs to trial and is under the impression the trial period has expired.   The microsoft solution is to uninstall the hotfix and wait for an update which superseded this update.

    Case closed, the KB has been superseded and my communications server is bang up to date.

    Case closed.