Forefront Server Security TechCenter >
Forefront Server Security Forums
>
Forefront Security for Office Communications Server
>
Forefront for OCS R2 - problem after latest Windows Updates
Forefront for OCS R2 - problem after latest Windows Updates
- I had the evaluation version of Forefront installed and working on our OCS R2 Front End Servers with no problems. After installation of the latest round of windows updates (KB956844, KB971961, KB968816 and KB96723 ) I found that the Front End OCS service was unable to start. To resolve this I deactivated the Front End Service and reinstalled it, which solved the problem. However, after this I had an error in Forefront saying "unable to connect to scan job". The services were still running OK, but users were unable to sign into OCS on this server. In an attempt to resolve this I removed and reinstalled Forefront. After doing this I was still getting the "unable to connect to scan job" error and the OCS front end service was unable to restart again. Any ideas on what might be the problem? I don't seem to be able to fully the remove Forefront by Add/Remove programs as configuration settings are still retained from the previous install. At the moment I have removed Forefront from the server again and OCS services are running properly again but obviously don't want to reinstall Forefront again if it's going to break things!
All Replies
- We had the same problems at work. I do not know what Microsoft is doing (After reading about the KB packs I noticed they only run with systems we do not have. It caused system down time for 6 Hours at work on multiple systems, Thank goodness it did not effect our Networks. I fixed it all up hiding the updates and could not get into any systems effected. A start brought me to safe Mode. So finally kb956844 KB971503 killed us and caused the Blue screen of death so staring at a Blank screen, I finally got to the system restore from the Start. and all was OK and I hid the Updates and I contacted Microsoft and they told me, It was not their fault adding that I have to to read about the Updates before I install them. I said, "Why ? I never had to before ?". He suggested that I should buy Vista or buy Windows 7 !?! Oh yeah ? So Days passed with no help and I forgot about it and thought of different ways of resolving it (so I rolled up my sleeves) and I did this : Creating a new Restore Point and backed up the Registry and I removed all Updates and removed all the traces of them in the registry, (this was tricky) and anywhere I seen evidence of them. I re started (Tested the system) all was OK, I then attempted a "Clean Reinstall"; and all problems are now resolved. I am happy camper now. But this trail and error was real time consuming but well worth it. I found the Registry contained evidence of the prior installs, If anyone has the issue with OCS and /or an update problem I suggest this. But backup the registry in case you go wrong. A Reinstall without cleaning the registry, problems will still exist. This worked for me, it might not for you. But in all a registry clean is the way to go. I do not suggest fooling with the Registry but if you know what you are doing and have backed the Registry and Created a Restore Point try this...
- Edited byLepitbull Thursday, November 12, 2009 10:28 PMproblems OCS and KB packs.
- At this time, we haven't had any issues reported regarding any incompatibilities between FSOCS and the mentioned hotfixes. Based on your description of the issue, it appears as though your FSOCS/OCS installation may be in a bad/unexpected state due to the sequence of uninstall/reinstall actions that took place. If FSOCS is installed, you can use the FSCUtility.exe tool to verify that FSOCS is properly integrated:
fscutility.exe /status
For more information about the utility, you can reference a related KB (originally written for FSE and FSSP): http://support.microsoft.com/default.aspx/kb/929076
Other things you may want to check are:
All Forefront services are running (FSCController and ForefrontRTCProxy are the key ones)
There is at least 1 (4 by default) instances of the FSOCScanner.exe process running
The ForefrontRTCProxy application appears in the OCS SIP Application list in the OCS Administration MMC snap-in (and that it is enabled and running)
If you are an Enterprise CAL customer, you may be eligible for CSS support even though you are running an evaluation version of the product. I'd recommend contacting your sales representative to see what support options might be available to you with regards to this issue.
Regards,
ShreyS [MSFT]- Proposed As Answer byShreyS [MSFT] Thursday, September 24, 2009 5:53 PM
- Marked As Answer byJim MoliniMSFT, OwnerMonday, October 05, 2009 5:27 PM
- Unmarked As Answer byNeil_MK Thursday, October 08, 2009 8:52 AM
- Unproposed As Answer byJim MoliniMSFT, OwnerFriday, October 09, 2009 6:06 PM
Once Forefront is installed, it is service dependency for the OCS Front-end service (RtcSrv.exe). Additionally, once the OCS Front-end service is starting, it does not start completely until Forefront is able to establish a connection. If OCS is failing to start, one of these two dependencies may not be functioning in your environment.
I'd recommend checking the Windows Event Log to determine if there is any useful information being generated by either service (ForefrontRTCProxy or RtcSrv) that could help to identify the issue. Additionally, if Forefront is having difficuly connecting to OCS, error detail may be logged in the application ProgramLog.txt. If either of these sources of information do not provide enough detail as to what the issue, please contact CSS; our support teams could assist you in validating your install and configuration.
Regards,
ShreyS [MSFT]- Proposed As Answer byShreyS [MSFT] Thursday, November 12, 2009 1:43 PM
- This problem has now been resolved: After re-installing Forefront, even though it was showing as 'started', I tried re-starting the ForefrontRTCProxy service from services.msc (which also by default restarts the RTC Service) and this resolved the problem. Thanks for your assistance with this.
