Answered by:
Lync 2013 Fron-End services crashing

Question
-
Hi,
Lync 2013 Front-End Std services craching every day many times whit errors (some errors below).
Installed new Lync 2013 Fron-End Ent and moved all services and after all sonfiguration was in place the same errors/crashes appeard. Have googled and tried solutions (changed GC etc.)
Servers are Windows 2012. In topology there is also Office Weba Apps 2013 server and Edge server.
Any ideas?
Fault offset: 0x00000000004b20af
Faulting process id: 0x1cf8
Faulting application start time: 0x01cea8213a1862fb
Faulting application path: C:\Program Files\Microsoft Lync Server 2013\Server\Core\RtcHost.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: fbddc99c-1464-11e3-93fd-0050569e73ab
Faulting package full name:
Faulting package-relative application ID:.NET Runtime 1023
Application: RtcHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FAC80F20AF (000007FAC7C40000) with exit code 80131506.
Faulting application name: RTCSrv.exe, version: 5.0.8308.0, time stamp: 0x5050fa6c
Faulting module name: ntdll.dll, version: 6.2.9200.16579, time stamp: 0x51637f77
Exception code: 0xc0000374
Fault offset: 0x00000000000ebd59
Faulting process id: 0x108c
Faulting application start time: 0x01ce7b9f56849cea
Faulting application path: C:\Program Files\Microsoft Lync Server 2013\Server\Core\RTCSrv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: f0f1a3de-e7ce-11e2-93f6-0050569e73ab
Faulting package full name:
Faulting package-relative application ID:Faulting application name: IMMCUSvc.exe, version: 5.0.8308.0, time stamp: 0x5050e305
Faulting module name: System.ni.dll, version: 4.0.30319.18045, time stamp: 0x5126f9e5
Exception code: 0xc0000005
Fault offset: 0x0000000000315e27
Faulting process id: 0x1134
Faulting application start time: 0x01ce7885cb439f3e
Faulting application path: C:\Program Files\Microsoft Lync Server 2013\OCSMCU\IM Conferencing\IMMCUSvc.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\System\577825eedb03a45fd7327050e85d0c44\System.ni.dll
Report Id: 4986c970-e7cf-11e2-93f6-0050569e73ab
Faulting package full name:
Faulting package-relative application ID:Regards,
PriiTWednesday, September 11, 2013 6:37 AM
Answers
-
Hi,
Problem is gone,
Seems that the problem was F-Secure real-time scanner after uninstall and server restart services have not crashed on the new server. Intresting is that on the first Lyns server for some time the F-Secure was uninstalled and aslo exclusions were made (http://technet.microsoft.com/en-us/library/jj205120.aspx) but the services were still crashing.Regards,
PriiT- Marked as answer by Snooz Thursday, September 12, 2013 7:41 PM
Thursday, September 12, 2013 7:41 PM
All replies
-
Hi,
Please make sure all required IIS roles have been installed on Windows Server 2012.
Please refer to this KB article to check Trusted Root Certification Authorities:
http://support.microsoft.com/kb/2795828
Kent Huang
TechNet Community SupportThursday, September 12, 2013 1:47 AM -
Hi,
Problem is gone,
Seems that the problem was F-Secure real-time scanner after uninstall and server restart services have not crashed on the new server. Intresting is that on the first Lyns server for some time the F-Secure was uninstalled and aslo exclusions were made (http://technet.microsoft.com/en-us/library/jj205120.aspx) but the services were still crashing.Regards,
PriiT- Marked as answer by Snooz Thursday, September 12, 2013 7:41 PM
Thursday, September 12, 2013 7:41 PM -
I had the same problem with McAfee Virus Scan.
I had to stop all mc afee services bofore starting the frontend service
Daniel
Thursday, October 3, 2013 4:25 PM -
Hi
I made an support case to F-secure about this same problem, answer was that disabling scanning after update, removes issue with crashing.
PMC -> advanced mode -> F-Secure Anti-Virus -> settings -> Virus definition updates and under that "launch scan after updates".
After doing this, problems with this ended totally, still maintaining protection from F-secure.
This was "workaround" and problems is still under investigation.
BR,
Pertti
- Proposed as answer by Pertti Ahlgren Saturday, February 22, 2014 8:47 AM
- Unproposed as answer by Pertti Ahlgren Saturday, February 22, 2014 8:47 AM
- Proposed as answer by Pertti Ahlgren Tuesday, February 25, 2014 6:05 AM
Saturday, February 22, 2014 8:40 AM