Lync Mobile client signs out - Error- IIS reset on Front End - WAS Errors

Question

I have a very limited understanding of Lync dependency's & how to trace the issue I'm now seeing. Would appreciate any direction or information to assist.
We have Primary & Secondary Pools - both pools seem to be effected at different times. The Mobile Clients will error & not sign in until iisreset
is done on the effected Front End.
This issue has started a few weeks ago. Before that this has happened maybe twice in a year.
A few weeks ago we did move the FileStore location of the Primary Front End only (off a Siffs Application store to the local drive of the Primary Front End)– AV scan
exclusion was set for FileStore location.
Also some Windows 2008R2 patches were applied.
The Deployment Wizard has been rerun incase something was broken by MS updates.
The Window Event log is clean apart from:
WAS events: (1 to 4 are grouped)
5013 - A process serving application pool 'LyncUcwa' suffered a fatal communication error with the Windows Process Activation Service. The process id was '24076'. The data field
contains the error number.
5011- The Windows Process Activation Service failed to generate an application pool config file for application pool 'LyncExtFeature'. The error type is '7'.
5189 - A process serving application pool 'LyncIntFeature' suffered a fatal communication error with the Windows Process Activation Service. The process id was '17216'. The data
field contains the error number.
5011 - A process serving application pool 'LyncUcwa' exceeded time limits during shut down. The process id was '12520'.
The Windows Process Activation Service failed to generate an application pool config file for application pool 'LyncIntReach'. The error type is '7'. To resolve this issue, please
ensure that the applicationhost.config file is correct and recommit the last configuration changes made. The data field contains the error number.
  Schannel: Same Error event happens twice within a few seconds
ID 36888 -
The following fatal alert was generated: 10. The internal error state is 1203.
ID 36888 -
The following fatal alert was generated: 10. The internal error state is 1203.
From What I’ve read SChannel doesn’t seem to be an issue.
Another set of WAS events:
5011 - A process serving application pool 'LyncUcwa' suffered a fatal communication error with the Windows Process Activation Service. The process id was '19132'.
5011 - A process serving application pool 'LyncIntFeature' suffered a fatal communication error with the Windows Process Activation Service. The process id was
'23876'.
5011 - A process serving application pool 'LyncIntReach' suffered a fatal communication error with the Windows Process Activation Service. The process id was
'9876'.
5011 - A process serving application pool 'LyncExtFeature' suffered a fatal communication error with the Windows Process Activation Service. The process id was
'21804'.
5138 -
A worker process '6620' serving application pool 'LyncUcwa' failed to stop a listener channel for protocol 'http' in the allotted time.
5013 - A process serving application pool 'LyncUcwa' exceeded time limits during shut down.
Our Exchange UM started to generate errors recently but not sure if that’s a result of the iisreset for WWW Pub – but these events don’t match any timing of Front End events:
Windows Process Activation Service
11/13/2014 04:06:37 PM
LogName=System
SourceName=Microsoft-Windows-Service Control Manager
EventCode=7031
EventType=2
Type=Error
ComputerName=Pxxx.xxx.com.au
TaskCategory=The operation completed successfully.
OpCode=The operation completed successfully.
RecordNumber=62445
Keywords=Classic
Message=The Windows Process Activation Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 0 milliseconds: Run the configured recovery program.
World Wide Web Publishing Service
11/13/2014 04:06:37 PM
LogName=System
SourceName=Microsoft-Windows-Service Control Manager
EventCode=7034
EventType=2
Type=Error
ComputerName= Pxxx.xxx.com.au
TaskCategory=The operation completed successfully.
OpCode=The operation completed successfully.
RecordNumber=62444
Keywords=Classic
Message=The World Wide Web Publishing Service service terminated unexpectedly.  It has done this 2 time(s).
I’m not sure where to go with this now. Any direction would be appreciated.
Thank you
 

Answer 1

Hi Davej006,
Web sites and Web applications depend on the availability of Internet Information Services (IIS) application pools. IIS application pools in turn depend on the Windows Process Activation Service (WAS). If WAS is not running or errors occur
during the startup or shutdown of an application pool, Web sites and Web applications may not be available.
And based on my understanding, if some program works sometime and does not in other times, RAM is the problem.
You could refer to the following article to troubleshoot your problem.
http://technet.microsoft.com/en-us/library/cc735271(v=ws.10).aspx
Hope it can be helpful.
Best regards,
Eric