Monday, September 28, 2015

LS Storage Service Events 32023, 32021 and 32019 are continuously logged on FEs

Have noticed these on Lync 2013 as well as SfB server recently. Usually after some kind of loss of network connectivity.

Per MS Support, this is a know bug and has been addressed in Skype for Business Server 2015 CU1 (https://support.microsoft.com/en-us/kb/3061064). Does not seem to be fixed in the Lync 2013 code stream though.

Workaround is to restart the OS on the impacted Lync server. That clears out the issue. 


Log entries look like these:

Log Name:      Lync Server
Source:        LS Storage Service
Event ID:      32019
Task Category: (4006)
Level:         Warning
Keywords:      Classic
User:          N/A

Description: Asynchronous Task timed out for a Storage Adaptor.

Storage Adaptor=36aa818f-00bb-43bc-88e7-6840eca732c6

Cause: Either the Asynchronous Task is hung and/or the Storage Adaptor is not reporting progress.
Resolution: No action needed. The Storage Service will auto heal the Asynchronous Task by attempting a graceful cancellation of the task and restarting it.

Log Name:      Lync Server
Source:        LS Storage Service
Event ID:      32021
Task Category: (4006)
Level:         Warning
Keywords:      Classic
User:          N/A

Description: Request to cancel a Storage Adaptor Asynchronous Task timed out.

Storage Adaptor=36aa818f-00bb-43bc-88e7-6840eca732c6

Cause: The cancel request would have been generated by the system as a result of the task having timed out earlier or the service is shutting down and draining. The Storage Adaptor has failed to cancel the task. Either the Asynchronous Task is hung and/or the Storage Adaptor has not implemented support for cancelling Asynchronous Task.
Resolution: No action needed yet. The Storage Service will check the Asynchronous Task again and log an error event if the condition persists.


Log Name:      Lync Server
Source:        LS Storage Service
Event ID:      32023
Task Category: (4006)
Level:         Error
Keywords:      Classic
User:          N/A

Description: Storage Service failed to stop the Asynchronous Task for a Storage Adaptor.

Storage Adaptor=36aa818f-00bb-43bc-88e7-6840eca732c6

Cause: The stop request would have been generated by the system as a result of the task having timed out earlier or the service is shutting down and draining. The Storage Adaptor has failed to stop the task. Either the Asynchronous Task is hung and/or the Storage Adaptor has not implemented support for cancelling Asynchronous Task.

Resolution: This condition should not be left unattended as data loss can occur. If the problem persists, notify your organization's support team with the event detail.

No comments:

Post a Comment