Unity Hot Issues from Cisco TAC

Unity 7.0(2) Calls to Secondary Active Fail with Wave Errors, Terminated CSCsy62216

Symptom: Unity version = 7.0(2.0) No patches installed Failover TSP 8.3.(1.0) When calls are presented to the active secondary server, calls fail with the following errors: 03/19/2009 5:15:13 PM 1 CiscoUnity_Wav 801 Cisco Unity's multi-media component has encountered a serious error. EXPLANATION: A serious failure has occurred on port 1 during wav media processing. Depending upon the severity of the failure parties on this call could experience unexpected behavior or be disconnected. In some cases further calls on this port will not be handled correctly. TECHNICAL DETAILS: Thread 0x0000171C had a Failure on Port 1 in AvWav DESCRIPTION: File: E:\views\CU7.0.1.28\un_Miu\UnityAvWav\WAV.cpp(2068) Method: WavPlayEx Failure: call to WavOutGetId failed. 03/19/2009 5:15:13 PM 1 CiscoUnity_Wav 801 Cisco Unity's multi-media component has encountered a serious error. EXPLANATION: A serious failure has occurred on port 1 during wav media processing. Depending upon the severity of the failure parties on this call could experience unexpected behavior or be disconnected. In some cases further calls on this port will not be handled correctly. TECHNICAL DETAILS: Thread 0x0000171C had a Failure on Port 1 in AvWav DESCRIPTION: File: E:\views\CU7.0.1.28\un_Miu\UnityAvWav\WAV.cpp(5544) Method: WavStopPlay Failure: call to WavOutGetId failed. 03/19/2009 5:15:13 PM 1 CiscoUnity_Wav 801 Cisco Unity's multi-media component has encountered a serious error. EXPLANATION: A serious failure has occurred on port 1 during wav media processing. Depending upon the severity of the failure parties on this call could experience unexpected behavior or be disconnected. In some cases further calls on this port will not be handled correctly. TECHNICAL DETAILS: Thread 0x0000171C had a Failure on Port 1 in AvWav DESCRIPTION: File: E:\views\CU7.0.1.28\un_Miu\UnityAvWav\WAV.cpp(2136) Method: WavPlayEx Failure: call to GetWavPtr/WavStopPlay failed. 03/19/2009 5:15:13 PM 1 CiscoUnity_Miu 535 Cisco Unity's telephony component has encountered a serious error. EXPLANATION: A serious failure has occurred on port 1 while trying to play a wav file or stream. Depending upon the severity of the failure parties on this call could experience unexpected behavior or be disconnected. In some cases " further calls on this port will not be handled correctly. TECHNICAL DETAILS: Thread 0x0000171C had a failure on port 1 in method CAvMiuWave::Play() DESCRIPTION: AvWav WavPlay failed with 0xFFFFFFFF. DETAILS: FileName: d:\CommServer\Localize\Prompts\ENU\G711\AvSubSignIn\AvSubSignInENU002.wav HWAV: 0x0000001C WavState: WAV_STOPPED. CALLINFO: CallerID: 2429771 CalledID: 5600 RedirectingID: Unknown Origin: Internal Reason: Direct Trunk: 0. CALL SEQUENCE: [17:07:47:192 - 0x00001764] Drop() - S_OK [17:15:13:354 - 0x000027C0] LINE_APPNEWCALL(0x00010AAD) [17:15:13:354 - 0x000027C0] SetEvent(NewCall) [17:15:13:354 - 0x000027C0] SetEvent(CallInfoArrived) [17:15:13:385 - 0x0000171C] Answer() entered [17:15:13:385 - 0x0000171C] lineAnswer(0x00010AAD) - 0x000107BE [17:15:13:385 - 0x000027C0] LINE_REPLY(0x000107BE | 0x00000000) [17:15:13:573 - 0x000027C0] LINECALLSTATE_CONNECTED(0x00010AAD | Active) [17:15:13:573 - 0x0000171C] WaitFor(0x000107BE | CONNECTED) - CONNECTED [17:15:13:573 - 0x0000171C] Answer() - S_MIU_CONNECTED [17:15:13:682 - 0x0000171C] GetMediaLength() entered [17:15:13:682 - 0x0000171C] WavOpen(AvSubSignInENU002.wav) - 0x0000001A [17:15:13:682 - 0x0000171C] WavGetLength(0x0000001A) - 5556 [17:15:13:682 - 0x0000171C] WavClose(0x0000001A) - 0x00000000 [17:15:13:682 - 0x0000171C] GetMediaLength() - 5556 | S_OK [17:15:13:682 - 0x0000171C] Play() entered [17:15:13:682 - 0x0000171C] WavOpen(AvSubSignInENU002.wav) - 0x0000001B [17:15:13:682 - 0x0000171C] WavGetLength(0x0000001B) - 5556 [17:15:13:682 - 0x0000171C] WavClose(0x0000001B) - 0x00000000 [17:15:13:698 - 0x0000171C] WavOpen(AvSubSignInENU002.wav) - 0x0000001C [17:15:13:698 - 0x0000171C] WavSetChunks(0x0000001C) - 0x00000000 [17:15:13:698 - 0x0000171C] WavSetPosition(0x0000001C | 0) - 0 [17:15:13:698 - 0x0000171C] WavSetVolume(0x0000001C | 50) - 0x00000000 [17:15:13:698 - 0x0000171C] WavSetSpeed(0x0000001C | 100) - 0x00000000 [17:15:13:698 - 0x0000171C] WavPlay(0x0000001C) - 0xFFFFFFFF [17:15:13:698 - 0x00002108] SetEvent(WavStopped). "
Conditions: Unity version = 7.0(2.0) No patches installed Failover TSP 8.3.(1.0) Secondary server is active. SKINNY TSP Integration to Cisco CUCM.
Workaround: Contact TAC.
Further Problem Description:

Infinite loop error message CiscoUnity_ConvMsg 10025 cryptic, Terminated CSCsg73411

Symptom: CiscoUnity_ConvMsg 10025 events are cryptic. This is a cosmetic issue only.
Conditions: This occurs in all version of Unity.
Workaround: To locate the object that caught the loop open Cisco Unity Data Link Explorer (UnityDBViewer.exe) from \CommServer\Utilities\DatabaseExplorer. In Cisco Unity Data Link Explorer click 'View' > 'Query Builder'. Run the following query replacing the @GUID in the example with the one in the event log message: SELECT Alias, DTMFAccessId FROM vw_CallHandler WHERE CallHandlerObjectId = '{2FDE35F3-4046-4FAF-BE08-5382D069F39A}'

CiscoUnity_NodeMgr 1088 warnings logged even after failure is resolved, Open CSCtn56601

Symptom: The following warning is logged to the event log every 15 minutes even though replication appears to be functioning properly: Problem Details: Event Type: Warning Event Source: CiscoUnity_NodeMgr Event Category: Run Event ID: 1088 Date: 10/19/2010 Time: 11:17:31 AM User: N/A Computer: UNITY-SERVER Description: Some SQL Server Agent Replication Job(s) failed to run. Check that SQL replication is configured and working properly.
Conditions: Unity 7.0(2) and later with failover configured.
Workaround: Open SQL Enterprise Manager and navigate to (primary server) -> Management -> SQL Server Agent -> Jobs. Look for any jobs listed that have a category with the prefix of "REPL" and that show an error or failure in the "Last Run Status" column. For any jobs that do: 1. If the job shows a Status of "Executing", then the job is actually running and replicating data. You'll need to manually stop/start the job just to clear the error. While this should not impact call processing, it is advisable to do this during a maintenance window and to verify replication afterwords. 2. If the job shows a Status of "Not Running", try manually starting it. If it enters the "Executing" state, the underlying condition has cleared for the moment but you may need to stop/start the job one more time to reset the last run status per above. If the "Last Run Status" time increments but continues to indicate a failure and the job does not run, you'll need to investigate why the job is failing and resolve that condition. In all cases where this error has been thrown, it is advisable to investigate the root cause of the SQL Server Agent job initially failing. This defect does not indicate that the event log error is a false positive, just that under certain conditions it may not clear automatically and continue to be reported.
Further Problem Description: The event log error is thrown based on whether the "Last Run Status" of any of the SQL Server Agent jobs indicates a failure. This is checked every 15 minutes by default. The trouble is that some of the jobs run in such a way that the last run status is not always reset after a failure, even if the job has successfully restarted and is able to run fine. If you are seeing this error reported, the server likely had a problem at some point, but you'll need to verify whether that condition still exists and either resolve it or manually reset the jobs. See above workaround for details.