Microsoft Office Communications Service (OCS) R2 Outage When IM Manager Unable to Roll Over Log Files

Article:TECH173492  |  Created: 2011-11-02  |  Updated: 2011-11-02  |  Article URL http://www.symantec.com/docs/TECH173492
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution

Product(s)

Issue



Users are unable to receive or send OCS messages.


Error



  • The Windows Application Event Log contains the following error message sequence:

Log Name:      Application
Source:        LC Filter Service
Date:          11/2/2011 4:47:22 AM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER01
Description:
Exception occurred during Rollover for E:\RTCFilterServiceNet.log. This may be due to one of the logfiles being locked by some other process or because the path is not accessible. MaxLogFileSize has been incremented to 20971520 and the service will continue logging to the existing file till service restarts.
Exception is :
System.IO.IOException: The process cannot access the file because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.__Error.WinIOError()
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at Imlogic.Beta.Rtc.Utils.MethodLogger.RolloverAndOpenLogFile()

 

which is the followed by the following message repeated many times from the LC Logging Service:

Log Name:      Application
Source:        LC Logging Service
Date:          11/2/2011 4:47:22 AM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER01
Description:
Exception caught -- Cannot write to a closed TextWriter. System.ObjectDisposedException
Server stack trace:
   at System.IO.__Error.WriterClosed()
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.IO.StreamWriter.Write(String value)
   at System.IO.TextWriter.Write(String format, Object arg0, Object arg1, Object arg2)
   at Imlogic.Beta.Rtc.Utils.MethodLogger.LogMessageStatic(Int32 nLogType, String strMethodName, String strLog, Object[] args)
   at Imlogic.Beta.Rtc.Utils.MethodLogger.Dispose()
   at OCSFilterService.OCSFilterService.FilterMessage(Hashtable& msgparam, Boolean& bBlockAction)
   at OCSFilterService.RemotingFilter.FilterMessage(Hashtable& filterparams, Boolean& bBlock)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at IFilterInterface.FilterMessage(Hashtable& filterparam, Boolean& bBlockAction)
   at RTCLoggingService.RTCLoggingService.ProcessMessage(Object senderObj, RequestReceivedEventArgs e, String sender, String recipient, Boolean bIsMPC, Boolean bInBound, String clientIP, Boolean& bBlockMsg, String strcontent, Boolean bInviteMsg)

In many instances the LC Filter Service detects a hung thread and then shuts itself down:

Log Name:      Application
Source:        LC Filter Service
Date:          11/2/2011 4:48:58 AM
Event ID:      0
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      SERVER01
Description:
1 hung request(s) detected. The service will restart

The Windows Service Control Manager detects the service stopped and attempts to restart it:

Log Name:      System
Source:        Service Control Manager
Date:          11/2/2011 4:49:03 AM
Event ID:      7031
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER01
Description:
The LC Filter Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 0 milliseconds: Restart the service.

If the restart is unsuccessful then the following events are reported in the Windows System Event log:

Log Name:      System
Source:        Service Control Manager
Date:          11/2/2011 4:49:12 AM
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER01
Description:
A timeout was reached (30000 milliseconds) while waiting for the LC Filter Service service to connect.

Log Name:      System
Source:        Service Control Manager
Date:          11/2/2011 4:49:12 AM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER01
Description:
The LC Filter Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.


Environment



  • IM Manager integrated with Microsoft Office Communications Service (OCS) R2

Cause



The LC Filter service is unable to roll over its log file and fails.  When the LC Filter Service is unavailable the LC Logging Service blocks messages.


Solution



Symantec is aware of this issue.  This article is updated as more information is available.  Subscribe to this article to receive updates.

Workaround

  • Restart the LC Filter Service to restore service.
  • Ensure that the LC Filter Service is configure to restart automatically.
  • Configure a process monitoring tool such as Microsoft Operations Manager to restart the LC Filter Service if it is not restarted.

 

 


Supplemental Materials

SourceETrack
Value2601921

SourceETrack
Value1498887



Article URL http://www.symantec.com/docs/TECH173492


Terms of use for this information are found in Legal Notices