Unity Hot Issues from Cisco TAC

Unity failing to connect to SQL causing Unity to stop working as expecte , Terminated CSCsv30015

Symptom: Unity 5.0.1 at times will display the following errors in application log: Source: CiscoUnity_AvRdbSvr Event ID: 21000 Description: Failed connecting to underlying database using: provider=SQLOLEDB;driver={SQL Server};Data Source=Computer Name ;Initial Catalog=UnityDb;Integrated Security=SSPI: 80004005 So during this time Unity appears to be having problem connecting to UnityDb. During this time SQL Enterprise Manager can attach to database. It has been reported that different symptoms are seen during the time of this issue: - When calling into Unity you get RNA - When calling into Unity you get Failsafe - Failover can take place during this event
Conditions: Seen in Unity 4.2.1 and Unity 5.0.1
Workaround: Reboot of systems clears the issue

After loading ES to support AD2008, you can no longer run MSCW , Fixed CSCsv47328

Symptom: After loading ES that has support for AD2008, you can no longer run MSCW. You get the following error: "Cannot Install Cisco Unity This wizard cannot install Cisco Unity on your computer, because the following reasons:"
Conditions: This will happen if you load ES 4 or higher for Unity 7.0 and ES57 or higher for Unity 5.0
Workaround: If you load the AD 2008 XML Test patch (also referred to as Other Patch #103), it will allow you to run MSCW again.
Further Problem Description: This should be listed in CCO install document and on the BU Post Install Instructions as a requirement. This will be required even if you do not have AD2008 in your environment, otherwise MSCW will fail right away with the error above.

ADSchemaSetup should give error message when run on 64bit Windows server , Fixed CSCsl48851

Symptom: When running ADSchemaSetup on a 64bit server you get no error prompting that it will not work.
Conditions: Try running the adschemasetup on a 64-bit server. Logged on as Domain Admin (member of Schema Admin group). Program ADSchemeSetup.exe starts when double clicked and presents window saying 'doubleclick to continue in English'. Doubleclicking closes the window and apparrantly crashes the program. Nothing more comes up on the screen and task manager shows nothing running. There are no errors in the event logs.
Further Problem Description: It should detect 64-bit Windows, display an error message that says what's wrong, and then exit gracefully.
Workaround: Do one of the following: - Run adschemasetup on a 32-bit server. - Extend the schema manually by running one or more of the following commands from the command line (the first command is required): For all Unity systems, the ldifde command line is: ldifde.exe -i -k -c "" "" -s "" -f " \ Schema\LdifScripts\avdirmonex2k.ldf" -j "" If you are using the Cisco Unity Bridge, also run: ldifde.exe -i -k -c "" "" -s "" -f " \ Schema\LdifScripts\omnigateway.ldf" -j "" If Unity system is using VPIM also run: ldifde.exe -i -k -c "" "" -s "" -f " \ Schema\LdifScripts\vpimgateway.ldf" -j "" where: is a literal value is the distinguished name for the domain in which you want to extend the schema. For example, for a domain named voice.cisco.com, you would use "CN=Configuration,DC=voice,DC=cisco,DC=com" is the DC on which you want to run the command is the location where you want log files to be saved For additional information on ldifde, see: - Win2003: http://technet.microsoft.com/en-us/library/cc755456.aspx - Win2008: http://technet.microsoft.com/en-us/library/cc730865.aspx

WTS console mode connections cause Unity call answering failures , Fixed CSCeg39434

Symptom: Calls to Unity and Unity Connection are immediately disconnected. The following errors (or similar) have been seen in the Event Log of the Unity server when this condition is experienced. These are partial captures of the errors observed due to this anomaly. --------------------------------------------------------------- Event Type: Error Event Source: CiscoUnity_Wav Event Category: Error Event ID: 822 Date: 11/19/2004 Time: 10:36:48 AM User: N/A Computer: [UNITYHOSTNAME] Description: Cisco Unity's multi-media component has enountered a serious error. EXPLANATION: A serious failure has occurred on port 1 while querying a wav device for supported playback formats. 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 0x00000788 had a Failure on Port 1 in AvWav DESCRIPTION: File: e:\views\cs_UE4.0.4.108\un_Miu\UnityAvWav\WAVOUT.C(1231) Method: WavOutSupportsFormat Failure: call to waveOutOpen/FormatQuery failed with error(6). For more information, click: http://www.CiscoUnitySupport.com/find.php ------------------------------------------------------------------------- ------------------------------------------------------------------------- Event Type: Error Event Source: CiscoUnity_Wav Event Category: Error Event ID: 801 Date: 11/19/2004 Time: 10:36:48 AM User: N/A Computer: [UNITYHOSTNAME] Description: Cisco Unity's multi-media component has enountered 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 0x00000788 had a Failure on Port 1 in AvWav DESCRIPTION: File: e:\views\cs_UE4.0.4.108\un_Miu\UnityAvWav\WAVOUT.C(1495) Method: WavOutFormatSuggest Failure: call to WavOutSupportsFormat failed. For more information, click: http://www.CiscoUnitySupport.com/find.php ----------------------------------------------------------------- ----------------------------------------------------------------- Event Type: Error Event Source: CiscoUnity_Wav Event Category: Error Event ID: 818 Date: 11/19/2004 Time: 10:36:48 AM User: N/A Computer: [UNITYHOSTNAME] Description: Cisco Unity's multi-media component has enountered a serious error. EXPLANATION: A serious failure has occurred on port 1 while opening a wav device for playback. 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 0x00000788 had a Failure on Port 1 in AvWav DESCRIPTION: File: e:\views\cs_UE4.0.4.108\un_Miu\UnityAvWav\WAVOUT.C(425) Method: WavOutOpen Failure: call to waveOutOpen failed with error(6). For more information, click: http://www.CiscoUnitySupport.com/find.php ----------------------------------------------------------------- ----------------------------------------------------------------- Event Type: Error Event Source: CiscoUnity_Wav Event Category: Error Event ID: 801 Date: 11/19/2004 Time: 10:36:48 AM User: N/A Computer: [UNITYHOSTNAME] Description: Cisco Unity's multi-media component has enountered 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 0x00000788 had a Failure on Port 1 in AvWav DESCRIPTION: File: e:\views\cs_UE4.0.4.108\un_Miu\UnityAvWav\WAV.C(1997) Method: WavPlayEx Failure: call to WavOutOpen failed. For more information, click: http://www.CiscoUnitySupport.com/find.php ----------------------------------------------------------------- ----------------------------------------------------------------- Event Type: Error Event Source: CiscoUnity_Miu Event Category: Error Event ID: 535 Date: 11/19/2004 Time: 10:36:48 AM User: N/A Computer: [UNITYHOSTNAME] Description: 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 0x00000788 had a failure on port 1 in method CAvMiuWave::Play() DESCRIPTION: AvWav WavPlay failed with 0xFFFFFFFF. DETAILS: IStream: 0x016B3CE0 HWAV: 0x000004D4 WavState: WAV_STOPPED. CALLINFO: CallerID: 90003 CalledID: 74000 RedirectingID: Unknown Origin: Internal Reason: Direct Trunk: 0. CALL SEQUENCE: [10:35:22:078 - 0x000000F0] Drop() - S_OK [10:36:47:983 - 0x00000E98] LINE_APPNEWCALL(0x00010001) [10:36:47:983 - 0x00000E98] SetEvent(NewCall) [10:36:47:983 - 0x00000E98] SetEvent(CallInfoArrived) [10:36:48:046 - 0x00000788] Answer() entered [10:36:48:046 - 0x00000788] lineAnswer(0x00010001) - 0x000103E0 [10:36:48:046 - 0x00000E98] LINE_REPLY(0x000103E0 | 0x00000000) [10:36:48:062 - 0x00000E98] LINECALLSTATE_CONNECTED(0x00010001 | Active) [10:36:48:062 - 0x00000788] WaitFor(0x000103E0 | CONNECTED) - CONNECTED [10:36:48:062 - 0x00000788] Answer() - S_MIU_CONNECTED [10:36:48:202 - 0x00000788] Play() entered [10:36:48:202 - 0x00000788] WavOpen(0x016B3CE0) - 0x000004D3 [10:36:48:202 - 0x00000788] WavGetLength(0x000004D3) - 14959 [10:36:48:202 - 0x00000788] WavClose(0x000004D3) - 0x00000000 [10:36:48:202 - 0x00000788] WavOpen(0x016B3CE0) - 0x000004D4 [10:36:48:202 - 0x00000788] WavSetChunks(0x000004D4) - 0x00000000 [10:36:48:202 - 0x00000788] WavSetPosition(0x000004D4 | 0) - 0 [10:36:48:202 - 0x00000788] WavSetVolume(0x000004D4 | 50) - 0x00000000 [10:36:48:202 - 0x00000788] WavSetSpeed(0x000004D4 | 100) - 0x00000000 [10:36:48:499 - 0x00000788] WavPlay(0x000004D4) - 0xFFFFFFFF. For more information, click: http://www.CiscoUnitySupport.com/find.php ------------------------------------------------------------------- ------------------------------------------------------------------- Event Type: Error Event Source: CiscoUnity_PHGreeting Event Category: Error Event ID: 437 Date: 11/19/2004 Time: 10:36:48 AM User: N/A Computer: [UNITYHOSTNAME] Description: An unexpected error occured while trying to play greeting for a subscriber. One possible reason could be that the call was disconnected while waiting for the phrase. This can happen when the Unity system CPU is pegged. Technical details - (PersonalGreeting) greeting for call handler id (null) with alias . returned [0x80004005] on line 3494 of file e:\views\cs_ue4.0.4.121\un_Conv2\AvConvPhoneHandler\AvConvPHGreetingSvr\AvSPlayGreeting.cpp. For more information, click: http://www.CiscoUnitySupport.com/find.php
Condition: This problem may occur in Unity 5.0(1) and earlier, and Unity Connection 1.1 and earlier. The solution has been integrated into Unity 7.0(2), so this problem will not occur in Unity 7.0(2) and later. In addition, the solution has been integrated into PCD v4.1.0.1, which is used to install the operating system for Unity on the following server models (note the solution will also be integrated into later PCD versions developed for future server models). MCS-7825-H4-ECS1 MCS-7835-H2-ECS2 MCS-7845-H2-ECS3 MCS-7845-H2-ECS4 MCS-7825-I4-ECS1 MCS-7835-I2-ECS2 MCS-7845-I2-ECS3 MCS-7845-I2-ECS4
Workaround/Solution Workaround 1. Do not run WTS in console mode. Do not use the /console command line parameter. 2. When initiating a console-mode WTS session, change the audio settings. Select the "options" command button. Select the "local resouces" tab. Change the "remote computer sound" selection to be "leave at remote computer". These settings for the WTS session can be saved to a config file, so that when that config file is used for a future WTS console-mode session, the appropriate audio settings are used such that Unity audio is not adversely affected. Solution 1: Run the latest version of the Server Updates Wizard. The version Server Updates Wizard available applies the Registry change detailed in Solution 2. A future version of Server Updates Wizard, due to post by March 2008, will also have the fix for KB928046. The Server Updates Wizard can be used with either Unity or UnityConnection 1.x. The updates described must be run on each Unity or UnityConnection server. Cisco recommends selected Microsoft updates that are important to protect Cisco Unity, Cisco Unity Connection 1.x, Cisco Unity Bridge, and voice-recognition servers. Cisco Unity Server Updates Wizard may be obtained from cisco.com at: Microsoft Updates for Unity (registered customers only) Information regarding Information on Server Updates Wizard may be found here. Solution 2: If you are running Windows 2003 SP1: Obtain KB928046 from the Microsoft website. Follow the instructions below to install the Microsoft Hotfix. The updates described must be run on each Unity or UnityConnection server. If you have only Windows 2003 SP1 installed, on the Unity or UnityConnection server, do the following: 1. Apply hotfix KB928046. 2. RESTART the Cisco Unity server when prompted. 3. When the Cisco Unity server is back on-line, do the following: Click Start, Click Run, Type Regedit, Click OK. 4. Locate and right-click the following registry subkey: HKEY_Local_Machine\System\CurrentControlSet\Control\Terminal Server. 5. Point to New, and then click DWORD Value. 6. Type DontUnloadConsoleAudio, and then press ENTER. 7. Right-click DontUnloadConsoleAudio, and then click Modify. 8. In the Edit DWORD Value dialog box, click Decimal, type 1 in the Value data box, and then click OK. 9. Exit Registry Editor. If you have Windows 2003 SP2 installed, a hot fix is not necessary. On the Unity or UnityConnection server, do the following: 1. Click Start. 2. Click Run. 3. Type Regedit, and then click OK. 4. Locate and right-click the following registry subkey: HKEY_Local_Machine\System\CurrentControlSet\Control\Terminal Server. 5. Point to New, and then click DWORD Value. 6. Type DontUnloadConsoleAudio, and then press ENTER. 7. Right-click DontUnloadConsoleAudio, and then click Modify. 8. In the Edit DWORD Value dialog box, click Decimal, type 1 in the Value data box, and then click OK. 9. Exit Registry Editor. Note, this problem is communicated in Field Notice 63030: http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_field_notices_list.html

MIU - Exceptions after Unity srvr reboot causes calls no ans. , Fixed CSCef80398

Symptom: Unity ports may not answer calls after a Unity server reboot. When this happens, the following error message will appear in the server application log for every Unity port: Event Type: Error Event Source: CiscoUnity_Miu Event Category: Error Event ID: 522 Date: 21/09/2004 Time: 10:36:17 User: N/A Computer: SERVER Description: Cisco Unity's telephony component has encountered a serious error. EXPLANATION: A serious failure has occurred on port 1 during telephony 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 0x00000B44 had a failure on port 1 in method CAvMiuLine::LineInit() DESCRIPTION: EXCEPTION_ACCESS_VIOLATION (0xC0000005) at 0x5DE33A85. Unable to access data at 0x00000000.. CALL SEQUENCE:
Conditions: This has been seen on both legacy and CCM integrations.
Workaround: Restarting the Unity services after the reboot will make the ports available. A software fix is available for 4.0(4) as an Engineering Special, and is fixed in 4.0(5).
Further Problem Description: It is possible with the software fix that sites may still experience failures. If this happens, the wait time may need to be increased by expanding the following registry key and adding the DWORD MutexSleepTimeMS with a value greater than 500ms (like 1000 for a full second). HKLM\Software\Active Voice\MIU\1.0\Initialization\MutexSleepTimeMS

Home Phone notification device update via TUI puts number in wrong field , Fixed CSCsv53352

Symptom: When users change their Home Phone notification device via the TUI, the updated number is not used. If a previous number was assigned via SAWeb for the user, it remains utilized for all message notification events for the Home Phone number. If the user checks the notification settings via the TUI, they are presented the new number they entered. Found that the Home Phone notification device update via TUI puts new number in the NotificationDevice table DlvdeviceSmtpAddress field instead of the DlvdevicePhoneNumber field by viewing the table in CUDLE. If you go to SaWeb and view the Home Phone notification device for the user, it shows the original number.
Conditions: Unity 7.0(2) base version and Unity 7.0(2) ES8 tested.
Workaround: Make any changes to users Home Phone Notification device via SaWeb. This defect has been addressed in Cisco Unity 7.0(2)ES18 and higher.

Ex2000/2003: MAPI address book providers Global Catalog failover broke , Fixed CSCsj43233

Symptom: 1. Afer addressing a message to another subscriber and sending the message via the telephone user interface (TUI), you do not hear "message sent". Instead you are returned to the main mailbox menu (i.e. "For new messages press 1, to send a message press 2" etc.), and the recipient does not recieve the message.
Conditions: 1. This applies to Cisco Unity 5.0(1) only, this defect does not apply to earlier versions of Cisco Unity. 2. This defect applies to Cisco Unity when when the partner mail server is Exchange 2000 or 2003 only, this does not apply to Cisco Unity when partnered with Exchange 2007. 3. This condition is created when their is more than one available Global Catalog Server and the Global Catalog server that the Cisco Unity servers MAPI address book provider is using to resolve recipient addresses is shutdown or rebooted.
Workaround: * This issue is addressed in a Cisco Unity 5.0(1) Engineering Special and no longer requires nor uses the workaround mentioned below. In the Windows registry, under HKLM\Software\Active Voice\MALEx\1.0\ Change the value specified for "NegoAuth" from 1 to 0 and restart Cisco Unity. NOTE: If Exchange 2007 is the partner mail server this setting must remain set to 1 or you will create a problem with similiar symptoms.
Further Problem Description: The following events are logged in the Windows Application Event Log: Event Type: Warning Event Source: CiscoUnity_MALEx Event Category: Warning Event ID: 30019 Date: 6/28/2007 Time: 7:20:00 PM User: N/A Computer: Description: The MAPI subsystem has indicated that the Global Catalog Server . which is used to resolve addresses for message submission cannot be reached, and that it has switched to using Global Catalog server .. Unity will continue to function using this newly selected Global Catalog server and will not automatically switch back to the original one. If Unity does not have a dedicated connection with sufficient bandwidth to the newly selected server, then there may be significant delays in Exchange access by Unity. Please verify that Unity has a good connection to the new Global Catalog for proper functioning. Event Type: Error Event Source: CiscoUnity_ConvMsg Event Category: Network Event ID: 10015 Date: 6/28/2007 Time: 7:20:00 PM User: N/A Computer: Description: IAvDohMessage::Submit: A recipient possibly lacked an email box: Recipients=([SubscriberA] ) returned [0x80040920] on line 976 of file E:\Views\CU5.0.0.297\un_Core2\ConversationEng\AvStateSvr\AvSMsgSend.cpp Event Type: Error Event Source: CiscoUnity_ConvMsg Event Category: Network Event ID: 10012 Date: 6/28/2007 Time: 7:20:00 PM User: N/A Computer: Description: This message has the following recipients : ([SubscriberA] ). The recipient mailboxes may be disabled or inaccessible, Cisco Unity may be having trouble connecting with the partner server, or the Cisco Unity messaging component may not be properly configured. 979

License Pooling does not work between Unity 4x and 5x versions. , Fixed CSCsg49334

Symptom: The administrator is unable to add or import Cisco Unity subscriber accounts because they have violated licensed counts. Additionally, the licensing applet reports license violations where the number of subscribers utilized has exceeded the licensed number. This occurs even though the customer should have enough licenses in their license pool.
Conditions: This is seen with Cisco Unity 4.x servers when they are in the same license pool as a Unity 5.x server, and the 4.x systems are relying on the 5.x server's license counts. This will not occur on the Unity 5.x server, even if it is in the same license pool as Unity 4.x servers. For 4.2(1) systems, this is fixed in 4.2(1) ES86. For 4.1(1) systems, this is fixed with 4.1(1) ES47. For 4.0(5) systems, this is fixed with 4.0(5) ES92.
Workaround: Apply the ES appropriate to the Unity 4.x version you are running.

NodeMgr on Secondary cycles between Failover/Failback, no errors on Pri. , Terminated CSCse36945

Symptom: In a Unity failover pair, although the Primary Unity system is operating properly, the Secondary Unity begins the failover process initially logging on the Secondary: Event Type: Error Event Source: CiscoUnity_NodeMgr Event Category: Run Event ID: 1011 Date: 5/10/2006 Time: 1:27:27 AM User: N/A Computer: UNITY-SECONDARY-SERVER Description: AvCsNodeMgr hasn't heard from partner UTY-AMS-501 in 30391 ms, disconnecting. For more information, click: http://www.CiscoUnitySupport.com/find.php This initiates the failover process on the Secondary Unity system activating it's Unity services and operations, but then re-establishes connectivity with the Primary and fails-back usually within a 1 minute period. This typically occurs so quickly the TSP's are never initiated on the Secondary and no services are disrupted on the Primary. During the period that the Secondary system is activating services, the directory monitor of both the Primary and Secondary can be in operation at the same time, potentially leading to duplicate entries within the SQL database. These entries typically show up as duplicate DTMFAccessID's associated to the same ParentObjectID.
Conditions: In this scenario, the Secondary Unity server losing connectivity with the Primary Unity system is due to the Node Manager on the Primary system taking over 30 seconds to process a snap shot file, during which it does not respond to the keep-alives sent between the failover pair. This missing of keep-alives initiates the failover process on the Secondary. On many occasions an error is logged on the Primary which may be an indicator that the Node Manager is cycling on the Secondary: Event Type: Warning Event Source: CiscoUnity_NodeMgr Event Category: Run Event ID: 1057 Date: 5/10/2006 Time: 2:05:28 AM User: N/A Computer: UNITY-PRIMARY-SERVER Description: Snapshot file \\CCM-NJUNITY002\Snapshot\PDS1.txt busy, file replication cycle skipped. For more information, click: http://www.CiscoUnitySupport.com/find.php This error is not always present when the Node Manager is cycling on the Secondary.
Workaround: An ES is under development to fix this issue. The following is an immediate workaround: Through the Failover Monitor, go to 'Configure' and increase 'Missed events before failover' to at least 90 (assuming the system is setup with the default interval of 1000ms) giving the Node Manager thread 1.5 minutes to complete the file process. This workaround's only impact is the Secondary Unity system will take an extra 60 seconds before initiating failover due to missing keep-alives from the Primary system.
Further Problem Description: The Primary server event logs reflect none of this activity directly, in fact the Primary is never aware that the Secondary has gone into a temporary active state.

CuMDBStoreMonitor repeatedly reporting mailstore has come online , Terminated CSCsx59710

Symptom: Getting the following application log message every 15 seconds. Never see any indication that the store has gone offline. 2/4/2009 3:05:57 PM 4 CiscoUnity_AvWm 29017 The following Information Store has come back online: CN=Mailbox Store (SERVER) CN=First Storage Group CN=InformationStore CN=INET-SERVER8 CN=Servers CN=Main CN=Administrative Groups CN=COLLEGE CN=Microsoft Exchange CN=Services CN=Configuration DC=ohio DC=edu Parent process: CuMDBStoreMonitor.exe
Conditions: Unity 5.0(1) on MS Windows Server 2003. Partner mailstore is Exchange 2003 SP2. Messages started after a reboot of the server after several months of working fine.
Workaround: If you stop and start the CuMDBStoreMonitor service, the messages will stop. But they start again after a reboot

Failsafe when entering invalid password for non-English TUI , Fixed CSCso77907

Symptom: When a user tries to login over the phone and enters an invalid password, Unity returns with an error message (failsafe) and disconnects the call. An error similar to the following will be seen in the application event log: Event Type: Error Event Source: CiscoUnity_PhraseServer Event Category: None Event ID: 10002 Date: 3/24/2008 Time: 1:24:12 AM User: N/A Computer: UNITY501 Description: (ScriptSingleUse.cpp) Script: subauthenticate_DEU.ps (PhraseDispatch) -- Could not find entry for InvalidPwd
Conditions: This problem may occur with Unity 4.2(1) and Unity 5.0(1) when the user is set to use a language other than US English. This problem does not occur when user is set to use US English.
Workaround: For Unity 5.0(1): Contact TAC to obtain Other (Non-Unity) Patch #99. Please note that 5.0(1)ES22 or later is a pre-requisite before installing the above patch. For Unity 4.2(1): Contact TAC to obtain Other (Non-Unity) Patch #100. Please note that 4.2(1)ES127 or later is a pre-requisite before installing the above patch.

Unity Multi Lingual, invalid password hears Failsafe Message , CSCso89768

Failure to create search folder results in MWI failure , Fixed CSCta29127

Symptom: Message waiting lamps are not synched on Unity startup.
Conditions: The Exchange server associated with a Subscriber is unable or unwilling to create the Unity Search Folders on the mailbox.
Workaround: Use DohPropTest or BulkLogout to logout, and then login the Subscribers on the mailstore in question

Alt extension is blank on saweb when changing the UnityMsgstoreSvc cred. , Fixed CSCsl17919

Symptom: After a change has been made to the password on the account that Cisco Unity Message Store Services log on as (typically UnityMsgStoreSvc, although the actual account name may differ), Cisco Unity may display a DCOM error and fail to display the Alternate Extensions page for subscribers when administrators attempt to browse to this page in the Cisco Unity Administrator. When accessing the alternate extension page, the following error is generated in the system event log: Event Type:Error Event Source:DCOM Event Category:None Event ID:10004 User:N/A Computer:UNITY50PRI Description: DCOM got error "Logon failure: unknown user name or bad password. " and was unable to logon DOMAIN\UnityMsgStoreSvc in order to run the server: {70722675-CFCA-42F9-98E6-74F6E7AD042A}
Conditions: This problem was observed in Unity 5.0(1). It is likely to occur in any version of Unity.
Workaround: To resolve this issue, you must update Component Services with the new password. Do the following procedure: Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Administrative Tools > Component Services. Step 2 In the right pane, expand Component Services > Computers > My Computer > COM+ Applications. Step 3 Right-click Cisco Unity and click Properties. Step 4 Click the Identity tab. Step 5 Enter and confirm the new password. Step 6 Click OK to save the changes, then close the Component Services window. Step 7 If the Cisco Unity Administrator is open, close it. Step 8 Open the Cisco Unity Administrator and browse to a Subscriber > Alternate Extensions page. The Alternate Extension page should display correctly.

AvCsMgr leaks found in Unity 5.0 , Fixed CSCsz16712

Symptom: Event Log errors (and diagnostic errors) referencing the Windows error code for out of memory, 0x8007000E.
Conditions: IStream::Stat method should use STATFLAG_NONAME to avoid leaking name info for the stream in many places, including voice mail messages, voice names, outgoing messages, etc. Leaking MAPI property holding the Global Catalog (GC) when the profile GC name is retrieved
Workaround: These are fixed in the latest 7.0 release, and in Cisco Unity 5.0(1) Engineering Special 75 and later.

Failover: Unitydb Configuration table lastmodifiedtime value is negative , Fixed CSCef60341

Symptom: When running the Unity Failover Configuration Wizard, the following error may be seen: "The SQL snapshot agent failed to complete in a reasonable amount of time. As a result, the Cisco Unity Failover will not work properly. Disable all Cisco Unity replication using the SQL Enterprise Manager and run this wizard again." In addition,failover or non-failover configuration, you may encounter the following error when launching the Dc/GC tool from the Tools Depot: "configuration database not found on local system". Returning all rows from the Configuration table in the UnityDb database (in SQL's Enterprise Manager), does not display any rows, but errors with "Invalid Time Format".
Conditions: Unity 4.0(x) versions with Failover. The SQL enterprise manager may display replication errors like ""The process could not bulk copy out of table '[dbo].syncobj_xxx]" and "Details: Invalid time format (Source: ODBC SQL Server Driver (ODBC);Error number: 0 The Configuration table may contain negative values for entries in the LastModifiedTime column. This is fixed in Cisco Unity 4.2(1).
Workaround: Update the Configuration table with the following case-sensitive sql statement (from a command line): osql -E -d UnityDb -Q "update Configuration set LastModifiedTime=NULL" Re-run the Failover Configuration Wizard.

Read-only AD 2008 pop-up erroneously displayed , Fixed CSCsz56759

Symptom: You receive the following pop-up, even though Unity is not in a 2008 domain or pointed to a read-only DC: Cisco Unity requires read-write access to Active Directory, but the Cisco Unity server is currently communicating with a read-only Active Directory 2008 domain controller. Cisco Unity will not function properly until you run the DC/GC Reconnect Settings Tool to change the domain controller that Cisco Unity communicates with. For more information, see the help for the tool.
Conditions: Unity 5.0(1) ES56 through ES74. Unity 7.0(2) ES7 or later This can occur, regardless of the version of the domain controllers in your active directory in the following cases: 1. When you are logged on to the Cisco Unity server with a local administrator account. If you do not see any CiscoUnity_DSAD warnings and errors in Event Viewer, then you can safely ignore the error message. 2. When you are logged on to the Cisco Unity server with a domain account, and Unity is unable to reach a DC, you will see event log messages similar to the following: Event Type: Warning Event Source: CiscoUnity_DSAD Event Category: Warning Event ID: 1017 Date: 5/11/2009 Time: 3:37:34 PM User: N/A Computer: UNITY Description: The Cisco Unity service that monitors Active Directory (AvDSAD) is skipping a synchronization cycle because it failed to connect to domain controller DC1.unity.local. Ensure that the server is accessible and is configured as a domain controller, and that no DNS issues exist. The service has failed to connect to this domain controller for 2 consecutive synchronization cycle(s). After 15 consecutive failed connection(s), The Cisco Unity service that monitors Active Directory (AvDSAD) will attempt to connect to a different domain controller. Diagnostic Info: Domain Controller: DC1.unity.local Binding String: LDAP://DC1.unity.local:389/ROOTDSE Error Code: ERROR_DS_UNAVAILABLE Description: The directory service is unavailable. Event Type: Warning Event Source: CiscoUnity_DSAD Event Category: Warning Event ID: 1090 Date: 5/11/2009 Time: 3:40:07 PM User: N/A Computer: UNITY Description: The Cisco Unity service that monitors Active Directory (AvDSAD) is skipping a synchronization cycle because it failed to connect to domain controller DC1.unity.local. The service has failed to connect to this domain controller for 15 consecutive synchronization cycle(s). The Cisco Unity service that monitors Active Directory (AvDSAD) will attempt to connect to a different domain controller. Diagnostic Info: Domain Controller: DC1.unity.local Binding String: LDAP://DC1.unity.local:389/ROOTDSE Error Code: ERROR_DS_UNAVAILABLE Description: The directory service is unavailable. Event Type: Error Event Source: CiscoUnity_DSAD Event Category: Error Event ID: 1103 Date: 5/11/2009 Time: 3:40:22 PM User: N/A Computer: UNITY Description: Unity currently is unable to locate a writable Domain Controller, and Unity will not function properly under this configuration. Please re-connect the Unity server to a writable Domain Controller with the DC/GC connection manager. 0x0000054B: The specified domain either does not exist or could not be contacted.
Workaround: The text of the pop-up warning message pertaining to AD 2008 read-only DCs can be ignored, but if you are logged on to the Cisco Unity server with a domain account, it does still indicate a failure connecting to AD. See the application event log for the specifics of what happened and when. In Cisco Unity 5.0(1) ES75 and later, the text of the message pop-up has been updated to: "Cisco Unity was unable to locate a Windows 2000, Windows 2003, or a writable Windows 2008 domain controller in the Active Directory forest. Cisco Unity will not function properly until this is resolved. To change the domain controller that Cisco Unity communicates with, run the DC/GC Reconnect Settings Tool in Tools Depot. For more information, see the help for the tool. To troubleshoot the problem, enable the Directory Monitor diagnostics. "

Permission Wizard fails to set permissions when multiple OU's selected , Terminated CSCsy08721

Symptom: Permission Wizard allows multiple OU's to be selected via the ADD pushtile, yet some permissions for those multiple OU's may not be correctly applied. (Permissions are not set which allow import via Bulk Import tool.)
Conditions: Permission Wizard 3.0.0.1 when run against multiple OU's. When attempting Bulk Import, system may generate the following error: (Error) Sync failed: . Error: LDAP_INSUFFICIENT_RIGHTS The Cisco Unity server must have permissions to create/modify objects in the directory. Please run the Cisco Unity Permissions Wizard to grant Unity the appropriate permissions.
Workaround: Run Permission Wizard against a single OU at a time. Alternately you may try running PW against the root OU.
Further Problem Description:

primary active but ports unregistered after reboot when sec. offline , Fixed CSCsq76448

Symptom: Primary ports are deactivated after a reboot. AvCsNodeMgr places the devices out of service.
Conditions: First saw this when they rebooted both servers at the same time, the secondary server was always the one that would be active. Tried booting primary with secondary powered off, and the ports still show as not registered in CCM. As the primary starts up, this is the first event starting deactivation; The Failover service (AvCsNodeMgr) is deactivating the Active Directory monitor on this server. See the following in the app log; 6/6/2008 19:00:45 PM 4 CiscoUnity_DSGC 1027 AvDSGlobalCatalog service started. This Unity server is not currently the active server so it will not monitor the Active Directory Global Catalog for changes. The active Unity server will assume responsibility for synchronizing the Unity database with the Active Directory Global Catalog. And the following in the Notifier traces; 19:00:57:618 (AvDiagnostics_MC,642,NodeMgr,13) [Thread 4556] PingThread: remote server MDC-UNITY-02 is not connected ...snip... 19:00:57:618 (AvDiagnostics_MC,642,NodeMgr,15) [Thread 4556] ActOnNoRemoteStatus unknown status 19:00:57:617 (AvDiagnostics_MC,754,NodeMgr,1) [Thread 4556] Method [> CAvNodeMgrService::StartDeactivation()] entered.
Workaround: Generally restarting Unity from the system tray will result in the ports registering and the server being active.

Upgrade of SQL Weekly/Nightly Backup Jobs Causes Upgrade To Fail , Terminated CSCso38223

Symptom: The upgrade installation process stops at the end when running SQL scripts. The following general error will be given: Error: Setup was unable to configure default settings on your system.
Conditions: This error has many different causes. This defect covers an upgrade failure to 5.0(1) when the SQL Weekly or Nightly backup jobs are owned by the built-in SQL 'sa' account.
Workaround: Change the owner of the Weekly and Nightly Backup Jobs to a domain account with SQL admin access vs. the built-in 'sa' account and re-run the upgrade.

Heap Corruption Appearing in AvCsMgr , Fixed CSCsb93268

Symptom: Unity's AvCsMgr service terminates unexpectedly during normal operation.
Conditions: This has been observed in a Unity 4.0(5) server with 72 voicemail ports and dual integration.
Workaround: The only workaround at this time is to reboot Unity.

Unity 4.2 Stops Answering Calls; AvArbiterSvr.dll Exception Occurred , CSCsi04112

Symptom: Server running Unity software version 4.2(1) stops answering calls intermittently. Calls transferred to voicemail ring continuously.
Conditions: The following error is recorded in the application log of event viewer: CiscoUnity_AvCs,100,Exception occurred and handled. File: E:\Views\CU4.2.0.110\un_Core1\Arbiter\AvArbiterSvr\AvArbiterWorkerThread.cpp at Line: 209 - Error: 80004005H Call stack: 0x5FEAFAAD AvArbiterSvr.dll: CiscoUnity_AvCs,100,Exception occurred and handled. File: E:\Views\CU4.2.0.110\un_Doh1\Dal\DalDb\AvDalDbDirStream.h at Line: 102 - Error: 80004005H Call stack: 0x5F9B2FED AvDalDbSvr.dll:
Workaround: none.

Subscriber not able to toggle between Standard and Alternate greeting , Fixed CSCsg52066

Symptom: Subscribers are not able to toggle between their standard and alternate greetings. When they attempt to turn on their alternate greeting via the TUI, they are just presented with the conversation they just heard (conversation loop). The alternate greeting is not turned on and the subscriber has no way to do this from the TUI. In the application log, we see the following error: Event Type: Error Event Source: CiscoUnity_ConvSubscriber Event Category: Error Event ID: 119 Date: 10/27/2006 Time: 1:22:07 PM User: N/A Computer: UNITY Description: An unexpected error has occured while a subscriber is on the phone with Unity. This can potentially result in the subscriber hearing the failsafe conversation. Technical details are - IAvDohMailbox::UpdateAlternateGreetingRule returned [0x80004005] on line 3414 of file e:\Views\cs_CU4.1.0.59\un_Conv1\Scripted\ConvSub\SubGreetings.cpp. From the Exchange server, we see the following error: Severity: Error Maintenance Mode: False Domain: XXXXXXX Computer: XXXXXXXXXXXXX Time Last Modified: 10/27/2006 1:22:10 PM Resolution State: New Time in State: 10/23/2006 1:55:30 PM Problem State: 0 Repeat Count: 44 Name: MAPI session closed due to excessive number of store objects in use. Source: MSExchangeIS Ticket Id: Owner: Description: Mapi session "/o=ORG/ou=First Administrative Group/cn=Recipients/cn=Unity_UNITY" exceeded the maximum of 50 objects of type "objtRulesView". Time of Last Event: 10/27/2006 1:22:07 PM Time Raised: 10/23/2006 9:55:29 AM Alert Id: c3f1e8ca-c19e-4ce9-adab-2ad4d1d28447 Rule Id: e13f000c-15ac-4825-8180-ef69dda627a0 Rule Name: MAPI session closed due to excessive number of store objects in use. CustomField1: CustomField2: CustomField3: CustomField4: CustomField5: Time Added: 10/23/2006 9:55:30 AM Time of First Event: 10/23/2006 9:55:29 AM Time Resolved: Resolved By: Modified By: NT AUTHORITY\NETWORK SERVICE Computer Custom Data 1: Computer Custom Data 2: Maintenance Mode End: Maintenance Mode User: Maintenance Mode Reason:
Conditions: This issue only occurs with Microsoft Exchange as the message store. This problem may occur in Unity 4.2(1) and earlier. It is fixed in the latest Unity 4.2(1) ES, and also fixed in Unity 5.0(1) and later.
Workaround: Restart Exchange information store, or reboot Exchange server. See MS article 830829 OR: Set the Alternate greeting from SA web. This will require the system admin to manually paste in the alternate greeting if it needs to be changed.
Further Problem Description: Issue is related to Unity opening too many MAPI sessions with Exchange - specifically with the objtRulesView component. Microsoft has a limit of 50 per client as a security measure. While this limit can be raised, it needs to be increased in increments of 100 (150, 250, etc). There is a MS article that discusses this - kb 830829 We turned on the following traces: DOH 10 Alcommon 10 MALEX (all) Subscriber Conversation (all) Reproduce the issue and then gather the AvCsMgr trace. In the trace, we see the following: 13:22:07:400 (AvDiagnostics_MC,1440,MALEx,1) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] Diagnostic: Thread: 00001128 Instance: 07fa71d4 - UpdateAlternateGreetingRule Entry 13:22:07:415 (AvDiagnostics_MC,1433,AlCommon,10) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] Error in CAvMALExMailbox::UpdateAlternateGreetingRule - GetTable Failed - File: e:\Views\cs_CU4.1.0.59\un_Doh1\MalMapi\MALEx\AvMALExMailbox.cpp Line: 107 Error: Unspecified error Thread: 00001128H Instance: 07FA71D0H 13:22:07:416 (AvDiagnostics_MC,1440,MALEx,1) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] Diagnostic: Thread: 00001128 Instance: 07fa71d4 - UpdateAlternateGreetingRule Exit 13:22:07:462 (CiscoUnity_ConvSubscriber,119,-1,-1) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] An unexpected error has occured while a subscriber is on the phone with Unity. This can potentially result in the subscriber hearing the failsafe conversation. Technical details are - IAvDohMailbox::UpdateAlternateGreetingRule returned [0x80004005] on line 3414 of file e:\Views\cs_CU4.1.0.59\un_Conv1\Scripted\ConvSub\SubGreetings.cpp. (null) 13:22:07:463 (CiscoUnity_ConvMsg,10001,-1,-1) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] Running conversation SubMenu on Port 3 Running conversation SubSetupMenu on Port 3 Running conversation SubGreetingsConv on Port 3 (null) 13:22:07:462 (AvDiagnostics_MC,119,Subscriber Conversation,15) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] IAvDohMailbox::UpdateAlternateGreetingRule 13:22:07:463 (AvDiagnostics_MC,1398,CDE,15) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] Exiting method ToggleAlternate_OnEntry normally for state [d:\commserver\localize\scripts\subgreetingsconv.cde!ToggleAlternate] 13:22:07:462 (AvDiagnostics_MC,1394,CDE,10) [Thread 4392] [Port 3] [524A21C71E7947D8B92D67820FE9BD7C] Port [3] OnEntry for state [d:\commserver\localize\scripts\subgreetingsconv.cde!ToggleAlternate] returned [0]

Adding ports does not increment values in NotificationMWI table , Terminated CSCsg38021

Symptom: After adding additional ports to a telephone Integration, or changing ports used in Unity Telephone Integration Manager (UTIM), MWIs on other Integrations fail. Application Log will also show errors similar to: Event Type: Error Event Source: CiscoUnity_Notifier Event Category: Run Event ID: 1041 Date: 10/16/2006 Time: 11:04:34 AM User: N/A Computer: Unity Description: Failed to set message waiting lamp for User1, ext 1234, switch 0, cluster 1, reason: no suitable port. Verify the MWI port configuration.
Conditions: The second integration must be an integration which relies on Port Memory for MWI. The failing integration maybe with PIMG, TIMG or voice boards.
Workaround: The workaround is to manually update the values of the MWI ports for each MWI device affected. Ideally, the following steps should be done after the port add/delete as been saved in UTIM and Unity has been stopped. To perform this task, you must know exactly how many ports were added or deleted to each Integration. If more than one Integration was changed, repeat the steps for each, starting with the lowest Integration. Ideally this process should be done when Unity is first stopped after ports have been added or deleted. While running the update at a different time may still be effective, it does increase the risk that one or more subscriber MWI will be out of sync. Typically, this means some subscriber MWI lamps will be stuck in a lit state. Such MWI will need to be manually reset via PBX administration. 1) Open the Cisco Unity Data Link Explorer (found in Tools Depot) 2) Select Query Builder from the View menu 3) (optional) Enter and Execute the following query: UPDATE NotificationMwi SET MwiPortNumber = MwiPortNumber + '0' WHERE MwiPortNumber > '0' Note running this query with the 0's in place, no rows will be affected. This is a good way to test run the syntax of your query. 4) (optional) Enter and Execute the following query: UPDATE NotificationMwi SET MwiPortNumber = MwiPortNumber + '0' WHERE MwiPortNumber > '0' -- replace 0 with the last port of the Integration Note, you want to use the port number that was valid BEFORE the add/delete. This query may shows rows were affected, however no values will be changed since only 0 is being added. The number of rows affected by this query tells how many of the previous results will directly be impacted by the add/delete. Thus if 0 rows are affected, no further updates are needed. 5) Execute the following query to update the impacted MWI devices: UPDATE NotificationMwi SET MwiPortNumber = MwiPortNumber + '0' -- replace 0 with the port number difference WHERE MwiPortNumber > '0' -- replace 0 with the last port of the Integration The first 0 should be replaced with the number of ports added or deleted to the Integration. Use a negative value if more ports were deleted than added. Replace the second zero with the port number of the Integration BEFORE any add/delete was performed. 5) You are now ready to either start Unity or Stop/Start the AvNotifierMgr service Example of Workaround: Suppose you started with the following config... Integration 1 - ports 1-8 Integration 2 - ports 9-32 Integration 3 - ports 33-48 Then added 8 ports to Integration 1 and deleted 16 ports from Integration 2, giving you... Integration 1 - ports 1-16 Integration 2 - ports 17-24 Integration 3 - ports 24-32 The port changes will not be active until Unity is restarted. When this occurs, the following two queries should be executed in order to ensure Port Memory associates are preserved. -- query 1 UPDATE NotificationMwi SET MwiPortNumber = MwiPortNumber + '+8' WHERE MwiPortNumber > '8' -- query 2 UPDATE NotificationMwi SET MwiPortNumber = MwiPortNumber + '-16' WHERE MwiPortNumber > '32'
Further Problem Description: This only occurs after adding additional ports to the first integration and where the second integration relies on port memory, or . The problem is caused because the MWIPortNumber field in the NotificationMWI table does not get modified when the port numbers change.

Supported "Format preference for incoming mail" setting needs documented , Fixed CSCsz56550

Symptom: Cannot forward voicemails. Voicemails are not saved properly in Domino. Not able to listen to them via the TUI or the Notes Client.
Conditions: Have Domino as your mail store. Have the "Format preference for incoming mail" field on the Mail tab of the Person document not set to "Keep in sender's format"
Workaround: Set the "Format preference for incoming mail" field on the Mail tab of the Person document to "Keep in sender's format" This was in the following document but not put in the current documentation. "DUC: Release Notes for Domino Unified Communication (DUC) 1.2.2 for Cisco. This document states the following: * Mail preferences for Domino Web Access and Notes subscribers To ensure proper functionality, set the "Format preference for incoming mail" field on the Mail tab of the Person document to "Keep in sender's format" or "No Preference."

Outlook icon for a VM does not change from a closed envelope , Terminated CSCsj92177

Symptom: When Outlook users in a unified messaging environment listen to a voicemail the icon does not change to an open envelope as it does on other messages when they have been opened.
Conditions: This happens wether they have VMO installed or not
Workaround: None

Realspeak engine buffer overflow results in email TTS failure , Fixed CSCsd26042

Symptom: An initial failsafe message is heard by a user playing back an email message via the Realspeak TTS engine. Unity later fails to play back any email message. To confirm the initially affected user as well as identify this specific defect, run the workaround below and then enable diagnostics (MalEx 12 and TTS): The TTS engine diagnostic shows the following error: < CAvRealSpeakMapper::startGenerating(CAvString&)] exited with value [0x8000FFFF; -2147418113]." Note the timestamp of this failure. Open the AvCsMgr trace and click on the line with the timestamp closest to the one for the error above. Do a find and search _up_ for "] Mailbox - Logon" -
Conditions: This issue may occur in Unity 4.2(1) and earlier. The problem is fixed in the latest Unity 4.2(1) ES, as well as Unity 5.0(1) and later.
Workaround: Restart the Unity server.

Security scanner indicates security vulnerabilities in Cisco Unity , Fixed CSCsu72988

Symptom: Some security scanners indicate vulnerabilities in the version of Tomcat running on Cisco Unity. These are low severity vulnerabilities on the Cisco Unity server and can be mitigated by limiting access to the web interface from untrusted networks. These vulnerabilities have been resolved in Unity version 8.x and later by an upgrade to the Tomcat version used by Cisco Unity.
Workaround: Do not allow Unity servers access from untrusted networks.
Further Problem Description: The tomcat versions running on Unity is vulnerable to the following CVE's. CVE 2007-1358 This is a cross site scripting vulnerability. CVE 2007-3382 CVE 2007-3385 CVE 2007-5333 These are reconnaissance vulnerabilities that may lead to leakage of session IDs

Domino Message Count Incorrect When Multiple Notfications are Recieved , Fixed CSCsv92044

Symptom: Should Unity receive multiple notification packets from multiple Domino servers, for the same Unity subscriber account, for the same notification event, Unity will ignore the included message count and therefore decrement the message count understood by Unity for each received packet. This will result in improper MWI function.
Conditions: Unity 7.0(2) with Domino Mailstore The Domino servers are in a cluster DUC 1.2.3, DUC 1.2.4, or DUC 1.2.5
Workaround: This problem has been fixed in Unity 7.0(2) Engineering Special 24 and later.
Further Problem Description: It is believed that this should not happen, even when there are multiple "Notifier Lines" within the Subscriber's Domino Mail File.

Heap Corruption in AvDSAD , Fixed CSCsd33741

Symptom: The symptoms of this problem may vary. However, so far there are two main symptoms: 1. After a while of working normally, the Unity server will cease functioning in the ability to import Unity subscribers. In this condition, the following error message may be seen in the event log: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10010 Date: 1/16/2006 Time: 11:04:43 AM User: Computer: Description: The server {20CEEB42-9402-11D4-A10A-00C04F2B5734} did not register with DCOM within the required timeout. Note that the GUID (20CEEB42-9402-11D4-A10A-00C04F2B5734) in the event log must be the same as it correponds to the AvDSAD COM object. If this message is seen and the GUID is different, then it is not this issue. 2. The AvDSAD may fail repeatedly to complete its synchronization cycle. Examining AvDSAD diags will show the following message: "Exception caught in SynchronizeDirectory()"
Conditions: Unity 4.0(5) connected to Exchange2000 or Exchange2003. AvDSAD diagnostic flag "Directory Property Access" is enabled. This issue is resolved in Unity 4.2(1) and later.
Workaround: Disable the AvDSAD "Directory Property Access" flag and restart the AvDSAD.

Unity 7.0(2) - Conversation throws exception in event log. , Fixed CSCtd01796

Symptom: Unity throws conversation expetion in event log.
Conditions: Seen in Unity 7.0(2) ES26. CiscoUnity_AvCs 100 Exception occurred and handled. File: h:\views\cuesb3_view\un_doh1\doh\src\AvDohPropertyManagerImpl.h at Line: 636 - Error: 80070057H Call stack: Exception Caught : 0xc0000005 Exception Flags : 0x00000000 Prev. Exception Record: 00000000 Exception Address : 7C815E7C NumberParameters = 2. Param[0] = 0x00000000 Param[1] = 0x00000000 Thread ID: 3128 Processor Context: ESI:00000000 EDI:00000000 CS:EIP:001B:7C815E7C SS:ESP:0023:06D3D060 EBP:06D3D094 DS:0023 ES:0023 FS:003B GS:0000 Flags:00010246 EIP: (Module:Offset) ntdll.dll:0x15e7c Process Name: AvCsMgr.exe CiscoUnity_ConvMsg 10053 spMessage->Commit(vaIDs.put() vaResults.put()) returned: 0x80070057 CiscoUnity_ConvMsg 10053 ProcessSendMessage(common_diag spMessage pEventID) returned: 0x80004005 Error is benign.
Workaround: None.

SA incorrectly reports Standard Greeting as being disabled. , Fixed CSCsg36208

Symptom: Under the greetings settings for a Call Handler's Standard greeting, Status is set to 'Disabled' and is greyed out preventing change. The Standard Greeting still functions normally.
Conditions: Reported on a customer system running Cisco Unity 4.2(1). New install.
Workaround: To correct this status displayed in the SA and/or if the Standard Greeting truly is disabled then latest version of DBWalker run without any options selected will correct this. It will display the following message: Greeting rule Standard 1195:(error) Standard messaging rule was disabled, which should never be possible. 1253:(fixed) Standard messaging rule automatically enabled. If running DBWalker does not correct the problem contact TAC for further assistance. NOTE: The Standard Greeting is designed such that it can never be disabled, it plays all the time unless overridden by another greeting.

SA: Sub template phone password not saved , Fixed CSCef07484

Symptom: When trivial passwords are allowed, changes to the phone password on the Subscriber Template > Passwords page in the Cisco Unity Administrator (the SA) are not saved. Steps to reproduce: 1. In the SA, go to the Subscribers > Account Policy > Phone Policy page, and uncheck the check box "Check against trivial passwords for extra security" so that trivial passwords are allowed. Save the page. 2. Go to the Subscriber Template > Passwords page, change the phone password to any legit number -- trivial or non-trivial -- it doesn't matter. 3. Save the page, and it appears as if the new phone password has been saved. 4. Browse away from the page, and then browse back to the Subscriber Template > Phone Password page, and the old password is back.
Conditions: This problem was found in the released version of Unity 4.0.(4) on both Exchange and Domino systems.
Workaround: This defect is fixed in 4.0(5) and 4.0(4) ES48. Alternatively, changes to the phone password on the subscriber template are saved when trivial passwords are not allowed. (That is, the check box "Check against trivial passwords for extra security" on the Subscribers > Account Policy > Phone Policy page is checked.) Alternatively, change the phone password in the UnityDb SQL database instead of the SA. Open the SubscriberTemplate table. Change the value in the PwDtmf column of the row corresponding to the template that you want to modify.

PIMG RTP port range out of normal Cisco range , Fixed CSCsi17684

PIMG's default RTP port range of 49000 to 50000 is out of the normal Cisco RTP port range of 16384 to 32767. The values can be adjusted by modifying the following two parameters in PIMG's config.ini file: ; Start Port for RTP: Number between 6000 - 65000 gwRTPStartPort = xxxxxx ; End Port for RTP: Number between 6000 - 65000 gwRTPEndPort = yyyyyy

Information Store offline/online causes resync only to partner store , Fixed CSCsq21207

Symptom: When a Unity server has subscribers homed on multiple Exchange stores, an offline/online event should trigger a resync of the Exchange mailboxes across all Exchange information stores where subscribers are homed. However, as a result of this defect the resync is only triggered for the partner Information Store
Conditions: This problem may occur when Unity has subscribers homed on more than one Exchange server of any version. This problem may occur in Unity 5.0(1) and 7.0(2). It is resolved in the latest Unity 5.0(1) ES.
Workaround: Restarting AvMessageStoreMonitor service will resync non-partner Information Stores after an offline/online event.
Further Problem Description: This was reproduced in the customer's environment which is Exchange 2007. They failed over from the active to passive node in an Exchange 2007 cluster. This caused Unity to detect the Information Stores as offline and then online. When this type of event happens Unity performs an mwi resync. We only resync the partner Information Store. All the non-partner stores MWI will be broken on until we restart AvMsgStoreMonitorSvc. This is reproduced by doing the following: Create a user on the partner Information Store. Create a user on a non-partner Information Store. Confirm MWI is working for both. Stop the Exchange Information Store Service on the Exchange 2007 server. This will give the offline status. Restart the service after about 30 seconds. Unity will see the Information Store as back online. We will log a complete resync event only for the partner Information Store. Event Type: Warning Event Source: CiscoUnity_ExchangeMonitor Event Category: Run Event ID: 1031 Date: 5/9/2008 Time: 5:51:03 PM User: N/A Computer: XXXXXX Description: Completed resyncing mailboxes on the following Information Store: XXXXYZ We never see an event for the other Information Stores. If you test, MWI works fine on the partner Information Store Users after the above event. The non-partner Information Store users will not work until we reset AvMessageStoreMonitor service.

Garbled characters on Unity System Administration when remote accessing , Terminated CSCsi43384

Symptom: Japanese characters in Unity System Administor Pages gets garbled, when doing remote access from a client PC using JPN Language to Unity server using ENU Language.
Conditions: Unity server: - OS: Windows Server 2003 R2 Enterprise Edition / English - Unity Version: 4.2(1) - Unity Language: English, Japanese, Spanish, French Active Directory: - OS: Windows Server 2003 R2 Enterprise Edition / English Exchange: - OS: Windows Server 2003 R2 Enterprise Edition / English - Exchange Version: Exchange Server 2003 SP2 Enterprise Edition / English
Further Problem Description: Not only doing remote access from a client PC with JPN OS, also on Unity server after applying JPN Language Pack of Internet Explorer, the same garbled characters are seen.
Workaround: Please perform the following steps; 1. Open "Regional and Language Options" in Control Panel. 2. Check "Install files for Asian languages" in Languages tab. 3. Select "Japanese" in "Language for non-Unicode programs" in Advanced tab. 4. File installation starts automatically (Windows Server 2003 SP and Windows Server 2003 Standard Edition Software are required in this step). 5. After finishing the installation, restart Unity Server.

Upgrade or rerunning Unity Setup fails after installing certain ESs , Fixed CSCsv99163

Symptom: Unity upgrade will fail if an upgrade is launched after installing certain ESs (see list below under conditions). Unity Setup will also fail if it is rerun without a version upgrade. The Setup wizard will hang while executing UnityDbEx.sql. A look at the latest OSQL* file in Commserver\Logs will show repeated errors of this kind: fn_MatchString Msg 3729, Level 16, State 1, Server XXXXX, Line 1 Cannot DROP PROCEDURE 'fn_MatchString' because it is being referenced by object 'CN_TextName'.
Conditions: Unity 4.2(1)ES162 to 4.2(1)ES165 (inclusive) or Unity 5.0(1)ES56 to 5.0(1)ES64 (inclusive) or Unity 7.0(2)ES9 to 7.0(1)ES15 (inclusive) The defect is triggered by running Unity Setup, such as when upgrading Unity to a different version.
Workaround: Obtain the appropriate non-Unity patch (should correspond to the version of Unity you are upgrading to, or which you are reinstalling) from the list below: Unity 4.2(1) Patch 111 Unity 5.0(1) Patch 112 Unity 7.0(2) Patch 113 Follow the instructions provided with the patch to recover your Unity system, and to start Unity upgrade or installation again. After Unity upgrade or re-run of Setup, install the ES appropriate to your Unity version, from the following list: 4.2(1)ES166 or higher 5.0(2)ES65 or higher 7.0(2)ES17 or higher

Mailbox logons fail in Windows 2008 based domain , Fixed CSCsz20178

Symptom: When calling in to check messages, callers will here "Your messages are not available now". The following events are repeatedly logged in the Windows application event log: Event Type: Error Event Source: CiscoUnity_MALEx Event Category: Error Event ID: 30003 Date: 4/20/2009 Time: 4:22:38 PM User: N/A Computer: (Unity Server Name) Description: An attempt to access the Primary Exchange Mailbox Store by CsBMsgConnector via MAPI has failed. The MAPI subsystem return the following error: The information store could not be opened.. Event Type: Error Event Source: CiscoUnity_MALEx Event Category: Error Event ID: 30012 Date: 4/20/2009 Time: 4:22:38 PM User: N/A Computer: (Unity Server Name) Description: An occurred which prevents successful Exchange access by CsBMsgConnector via MAPI. This is typically an indication of configuration issues with Unity, Exchange, or the MAPI subsystem. Verify that the Unity services accounts are granted the correct permissions and that there are no issues with installation. The SysCheck utility may assist in diagnosing the problem. Event Type: Error Event Source: CiscoUnity_Doh Event Category: Error Event ID: 32013 Date: 4/20/2009 Time: 4:22:38 PM User: N/A Computer: (Unity Server Name) Description: Doh logon failed due to messaging component logon error: 8004052eH
Conditions: The symptoms listed in this defect may be caused by various conditions. This specific issue occurs only on Cisco Unity for Exchange when the Cisco Unity servers MAPI profile is configured to use use a Windows 2008 Global Catalog server. To determine which Global Catalog server your Cisco Unity servers MAPI profile is configured to use perform the following: 1. Go to the Start menu and choose Run. 2. Type regedit.exe and click OK. 3. Expand the HKEY_CURRENT_USER registry hive to the following location: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles 4. Expand the Unity System Profile key 5. Click on the key that begins with dca 6. In the right pain there will be a string value that lists the name of the Global Catalog server currently being used my MAPI. If you have determined that a Windows 2008 GC server is being used, refer to the MS KB article referenced in the workaround section of this defect to enable logging on the Global Catalog server and determine if your issue is caused by limited NSPI sessions.
Workaround: If you have determined that that the issue you are seeing is due to limited NSPI sessions, refer to the KB article below for information on how to change the NSPI max sessions per user limit. Note: Cisco recommends changing the NSPI max sessions per user to 0x00002710. After modifying the registry on the Global Catalog, the Unity server must be restarted to take advantage of the new limit. No restart of the Global Catalog is required. http://support.microsoft.com/kb/949469/en-us%20
Further Problem Description: The following events are logged in the Windows application event log each time a subscriber attempts to login to their mailbox via the telephone user interface (TUI): Event Type: Error Event Source: CiscoUnity_MALEx Event Category: Error Event ID: 30003 Date: 4/20/2009 Time: 5:17:29 PM User: N/A Computer: (Unity Server Name) Description: An attempt to access the Primary Exchange Mailbox Store by AvCsMgr via MAPI has failed. The MAPI subsystem return the following error: The information store could not be opened.. Event Type: Error Event Source: CiscoUnity_MALEx Event Category: Error Event ID: 30012 Date: 4/20/2009 Time: 5:17:29 PM User: N/A Computer: (Unity Server Name) Description: An occurred which prevents successful Exchange access by AvCsMgr via MAPI. This is typically an indication of configuration issues with Unity, Exchange, or the MAPI subsystem. Verify that the Unity services accounts are granted the correct permissions and that there are no issues with installation. The SysCheck utility may assist in diagnosing the problem. Event Type: Error Event Source: CiscoUnity_ConvSub Event Category: Network Event ID: 1000 Date: 4/20/2009 Time: 5:17:29 PM User: N/A Computer: (Unity Server Name) Description: An unexpected error has occured while a subscriber is on the phone with Unity. This can potentially result in the subscriber hearing the failsafe conversation. Technical details are - IAvDohMailUser::get_Inbox returned [0x8004052e] on line 1312 of file E:\views\CU8.0.0.170\un_Conv1\Scripted\ConvSub\MsgCount.cpp. Event Type: Error Event Source: CiscoUnity_MALEx Event Category: Error Event ID: 30003 Date: 4/20/2009 Time: 5:17:29 PM User: N/A Computer: (Unity Server Name) Description: An attempt to access the Primary Exchange Mailbox Store by AvCsMgr via MAPI has failed. The MAPI subsystem return the following error: The information store could not be opened.. Event Type: Error Event Source: CiscoUnity_ConvSub Event Category: Network Event ID: 1394 Date: 4/20/2009 Time: 5:17:29 PM User: N/A Computer: (Unity Server Name) Description: The description for Event ID ( 1394 ) in Source ( CiscoUnity_ConvSub ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: msg.GetMessageCount(spMailUser.get(), spNP, pSM) returned: 0x8004052E, 534, E:\views\CU8.0.0.170\un_Conv1\Scripted\ConvSub\MsgCount.cpp, .

Unity AD sync - offer setting to disable sync'ing Scope DL's , Fixed CSCsw25257

Symptom: High LDAP queries on distribution lists on Domain Controllers coming from Unity.
Conditions: Scope Distribution Lists are used in Unity for directory handlers. For deployments that do not use directory handlers but have lots of distribution lists, the sync with Active Directory can result in many uneeded LDAP queries if, for example, there is just one directory handler that is not actually used in production.
Workaround: This is a request for a feature - a setting should be offered to allow completely disabling Scope DL syncing. For this reason, a software fix is required.

Unity has permissions issues , Fixed CSCeg82247

Symptom: Many Unity SRs are resolved by correcting permissions; this DDTS is tracking those SRs until a utility to check permissions set is built.
Conditions: All versions of Unity
Workaround: Manually compare customer's Unity service accounts permissions vs. these documents (dependent on the version of Unity you have as to which document you will use) - http://www.ciscounitytools.com/HelpFiles/PW3x/PWHelpPermissionsSet.htm - http://www.ciscounitytools.com/HelpFiles/PW403+/PWHelpPermissionsSet_ENU.htm

Exchange 2007 DOH logon/send fails if public folder database dismounted , Terminated CSCsq31845

Symptom: With Exchange 2007, if the public folders database need to be installed and mounted or Unity will not be able to send or retrieve messages and Unity will be forced into UMR mode.
Conditions: With Exchange 2007, if the public folders database need to be installed and mounted or Unity will not be able to send or retrieve messages and Unity will be forced into UMR mode. The diagnostics will show 8004011D as the primary/first failure code. 14:55:50:643 (AvDiagnostics_MC,1440,MALEx,13) [Thread 4844] Diagnostic: CAvMapiWrapper::OpenExchangePrivateStore failed with error 0x8004011D. Subsequent errors might be of the form: 14:55:50:676 (AvDiagnostics_MC,1440,Doh,16) [Thread 4844] Diagnostic: IAvMALSession::Logon failed with error 0x8004052E.
Workaround: With Exchange 2007, the public message folder must be installed and mounted: http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/installation/guide/umexnofo/5xcuigumenofo060.html#wp1942680

MWI issues with Exchange 2007 and Windows Server 2008 , Fixed CSCsu62686

Symptom: MWI does not function properly - either there is a very long delay in lighting MWIs, or MWIs do not light at all.
Conditions: This problem may occur with Unity 5.x or later, for users with mailboxes hosted on an Exchange 2007 server running on Windows Server 2008.
Workaround: Install Exchange 2007 SP1 Rollup 4 or later on each Exchange 2007 server running on Windows 2008 that is homing Unity subscriber mailboxes. The rollup is referenced by KB 952580, and is currently located here: http://support.microsoft.com/?kbid=952580
Further Problem Description: This is an Exchange 2007 problem that impacts Unity. This defect is only to track this issue. The specific problem that causes the issue is documented by Microsoft in KB 951251: http://support.microsoft.com/kb/951251

MSCW should enable logs to see why users are created , Open CSCtd28917

Symptom: When running the Message Store Configuration Wizard with Unity, it will occasionally create duplicate user accounts in Active Directory for all Unity Subscribers. This defect is so Unity will automatically enable the correct logs when the MSCW is run so we are able to determine root cause for this and eventually resolve this.
Conditions: We have only seen this issue occur when running MSCW on an inactive Unity failover server, but it is possible to occur at other times as well.
Workaround: If you have had duplicate AD accounts created you can perform one of the following to resolve the issue: You can use the Migrate Subscriber Data Tool (http://ciscounitytools.com/App_MigrateSubscriberData.htm) to change the Unity subscriber to use the correct AD account again. You will then need to delete the invalid AD accounts. or Stop AvDSAD and AvDSGlobalCatalog services from services.msc. Delete duplicate AD accounts and set the directoryid field in the subscriber table in SQL to NULL. Then run \commserver\configurationsetup\setup.exe /sync on the Unity server so it gets the correct directoryid for the users. or *** Before starting the below steps, first verify that all the AD permissions are correct. You can do this by running permissions wizard in report mode and making sure there are no errors listed. *** (1) Install COBRAS export on the Primary Unity server and run it to export all of your subscribers including their voice messages: http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html (See the help link on that page as well for more details on usage of this tool). (2) Force Unity into UMR mode by following steps 1 - 4 here http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note 09186a0080117807.shtml#topic2 (don't do step 5. don't restart any Unity services) (3) Stop the following two services on the Primary unity server: AvDSAD AvGlobalCatalog (4) Delete the duplicate accounts from active directory (a) Right-click on the NA -> USERS OU, select Find (b) Select "Custom Search" from the drop-down (c) Select the Advanced Tab (d) Enter CiscoEcsbuUMLocationObjectID=* (e) Click Find (f) Locate the 7 accounts which should not be deleted. Move them to a different OU temporarily (not a child OU). (g) Delete the remaining duplicate accounts from the Users OU (5) Run the following command from the command prompt on the Unity server: osql -E -Q "use unitydb update Subscriber SET DirectoryId = NULL" (6) Start the following two services on the Primary unity server: AvDSAD AvGlobalCatalog (7) Run the following command from the Start menu: D:\CommServer\ConfigurationSetup\Setup.exe /sync (8) Remove the registry keys previously set in step 1 (9) Install COBRAS Import on the Primary Unity server and run it to import the back-ups of message that you took in Step 2: http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html (See the help link on that page as well for more details on usage of this tool).

Setup: Re-running setup part 1 fails to create UnityDb. , Terminated CSCdz26707

Symptom: On initial Unity installation, when the Cisco Unity Setup program is cancelled and then subsequently run again, this may cause Cisco Unity to think it's an upgrade and therefore, the upgrade scripts are run on a non-existent UnityDb database. This results in a failure near the end of the Unity Setup program. Tempu.log entry has the following: 2006-06-16T16:22:32 - Beginning to install configuration, new install = 0 new install = 0 is only expected on Unity upgrades. This indicates that Unity thinks it is in upgrade mode, not initial install mode. OsqlDump_*.Log shows: "Could not locate entry in sysdatabases for database 'UnityDB'. No entry found with that name. Make sure that the name is entered correctly." In upgrade mode Unity expects UnityDB to already be created, so this failure occurs.
Condition: This problem may occur in any version of Unity. It should only occur when installing Unity initially, not on upgrades.
Workaround: 1) Run ConfigMgr.exe, which is located in the Commserver directory. 2) After the initial prompt, choose Advanced and check "Run database configuration script". This runs C:\CommServer\Localize\DefaultConfiguration\ENU\DefaultDatabase.sql and will create the UnityDb with default settings. NOTE: If this is run on a system with existing objects (subscribers, call handlers, etc), all non-default Unity objects will be wiped out.

PIMG - MWI port memory broken in Dialogic versions 6.0 and 6.0su1 , Fixed CSCsy26512

Symptom: Analog and digital Dialogic media gateways running software versions 6.0 (6.0.103) and 6.0su1 (6.0.110) may not use the port tag specified in the SIP NOTIFY message. This could cause MWI To fail on legacy PBX integrations that require port memory.
Condition: Unity and or Unity Connection integrations utilizing analog or digital Dialogic media gateways tinterfacing with legacy PBXs requiring port memory for MWI.
Workaround: Upgrade to Dialogic software version 6.0su2 (6.0.121).

Update DST for US on Service Engines such as AIM-CUE NM-CUE NM-NAM NM-CE , Fixed CSCsh30313

Symptom: NM-CUE, NM-CE, NM-NAM, do not currently have support for the changes to DST( Daylight Saving Time) for US Timezones. They will be 1 hour offset between the new and old dates in spring and fall. ie: March 11, 2007 -> April 1, 2007 the timestamps will be 1 hour behind. October 28, 2007 -> November 4,2007 the timestamps will be 1 hour behind. Resolution: Upgrade to newer version of software for the modules.
Workaround: On the NM-CUE module, change the timezone setting to be 1 hour east on March 11, 2007 and change it back to its original setting on April 1, 2007. This would also need to be repeated for the Oct 28->Nov 4 dates. Each succeeding year would have different actual dates. On August 8, 2005, President George W. Bush signed the Energy Policy Act of 2005. This Act changed the time change dates for Daylight Saving Time in the U.S. Beginning in 2007, DST will begin on the second Sunday in March and end the first Sunday in November. The Secretary of Energy will report the impact of this change to Congress. Congress retains the right to resume the 2005 Daylight Saving Time schedule once the Department of Energy study is complete. Before this change, DST( Daylight Savings Time) was the first Sunday in April, and the last Sunday in October for the US.

AvWM wrongly detects exchange server as being down . , Fixed CSCsb43902

Symptom: After Upgrading to Unity 4.0.5 you start seeing these type of messages in Event Viewer: CiscoUnity_AvWM: Error accessing server: "Name of Server". ::RpcMgmtIsServerListening:1715. Process: AvCsMgr ProcessID: 3772 ThreadID: 6104 For more information As a result you will not be able to log into mailboxes that are on that server and you will get the UMR greeting when logging in.
Conditions: This might happen if you have either a second NIC on your exchange server which has a bogus adress or a modem which created a ppp connection. Eg ipconfig /all - you will see your NIC but as well eg the below: PPP adapter {23F75FF8-D979-4374-9AAD-60DC8A2DA95A}: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface Physical Address. . . . . . . . . : 00-53-45-00-00-00 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.234.235 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled
Workaround: Disable Modem Remove second NIC or disable it properly

Conversation traces not enabled using Macro Conversation State Traces , Fixed CSCsq92171

Symptom: Enabling the Macro Conversation State Traces does not enable correct conversation micro traces
Conditions: Unity 5 and Unity 7
Workaround: Enable the "Conversation" micro trace

UmrSynchSvr process leaks Notes handles in Unity for Domino , Fixed CSCso00238

Symptom: The AvUmrSyncSvr service may stop responding after processing many messages due to a leak of Notes resources when messages are sent. Messages will accumulate in the Unity MTA directory until the service is restarted.
Condition: This problem may occur in Unity 5.0 for Domino.
Workaround: None. Restart AvUmrSyncSvr to recover from this problem.

Add AD 2008 support , Fixed CSCsr90209

Symptom: Unity may not function as expected.
Conditions: Unity may fail when connecting to AD 2008 environment with read only Domain controller present in the environment.
Workaround: Connect to AD 2008 environment without any read only Domain controller in the environment. OR Force Unity to monitor the writable AD throught DCGC Reconnect Settings tool.
Further Problem Description: Unity requires read and write permission to the active directory. Without write permission, it will prevent Unity from creating and updating Unity's objects in AD. In previous version, Unity do not have concept of read only domain controller. It will go out and access any random domain controller or the one that specified by the Administrator.

Broadcast Administrator allows Delivery to PDL , Fixed CSCsh61464

Symptom: When sending Broadcast System Messages in Unity to a Public Distribution List, the message is delivered to the users' mailbox and their MWI is lit.
Conditions: Unity 4.0(5) and later The Feature "Subscriber can send broadcast messages to subscribers on multiple servers" has to be enabled.
Workaround: If you only have one Unity server, only use the "Subscriber can send broadcast messages to subscribers on this server" function. If you have multiple Unity servers, there is no workaround at this time.

Licensing on failover fails, preventing unity startup , Terminated CSCea69507

Release-note Symptom: On a secondary server, Unity won't start. The MIU logs an event log error: unable to read from the license server... information could not be recalculated. The licensing snap-in shows the following error: Unable to recalculate utilization Error number: 0x80043310 License information could not be recalculated 0x80040e07: Operand type clash: unique identifier is incompatible with datetime.
Condition: This problem occurs after installing a secondary server in a failover environment.
Workaround: Using ConfigMgr, choose 'Run Database Extended Script' and click run. This will run the UnityDbEx.sql script and re-create the view.

Cannot delete HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\AvCsNodeMgr. , Terminated CSCsw32396

Symptom: When running the following procedure, http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcuruge150.html#wp1230060. Converting a Primary Server to a Permanent Regular Cisco Unity 5.x Server Without Failover To Delete References to the Node Manager Service on the Primary Serve, Step 13 Delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\AvCsNodeMgr. When you run this step it fails stating it encountered an error when trying to delete the key.
Conditions: When you need to run the procedure Converting a Primary Server to a Permanent Regular Cisco Unity 5.x Server Without Failover
Workaround: You have to stop Unity. After you do this you will be able to delete the key.
Further Problem Description: If they run this procedure and do not delete this key, Unity will not be able to register its ports with Call Manager. There should be a notes before Step 13 stating the following. "If you get an error stating the key cannot be deleted you must stop Unity and try again."

UTIM Failed Loading the MIURegistry Component Error 0x800705 . , Terminated CSCsi54038

Symptom: UTIM will not start while Unity is running Error message displayed with text: "Failed loading the MiuRegistry component. Error 0x8007005. Access is denied In order to use the Telephony Integration Manager your Windows account must be a Cisco Unity administrator and a member of the Administrators group on this computer."
Conditions: Any version of Unity software installed on Windows 2003 operating system.
Workaround: Option 1. Stop the Unity services, UTIM launches without problem Option 2. - Use Process Explorer (available from MS) to change the ownership and access to MTXMiuRegistryReadWrite object. - Launch Process Explorer and select AvCsMgr.exe. - In the bottom pane, locate Mutant object \BaseNamedObjects\MTXMiuRegistryReadWrite. - Double click and change the security settings for this object so that the Local Administrators Group is the owner and has access. - UTIM should now start. Additional Comments: If the problem persists after a restart of Unity or the server, the local security policy likely overrides the default behavior and doesn't make the Administrators Group the default object owner. To change this, reassign the local (or DC) security policy, Security Option "System objects: Default owner for objects..." to Administrators. On Windows 2003 "not defined" should act the same as Administrators. Note this requires rebooting the Unity server.

Change Notes Password does not work for Domino version 6.X or higher , Fixed CSCsb76049

Symptom: Change Notes Password does not work for Domino version 6.X or higher
Conditions: Running Change Notes Password Tool does not allow if ran on Domino 6.X or higher.
Workaround: Workaround: Manually create your own registry key HKLM\SOFTWARE\Lotus\Notes\5.0 and populate it with the same values as the 6.0 key.

SQL templog.ldf fills up availble disk space, causing failsafe . , Fixed CSCsd63155

Symptom: NOTE: When reviewing SQL and MSDE issues on Cisco Unity servers, please note there are three sets of SQL files. This defect pertains only to the TempLog.ldf file. 1. UnityDb.mdf and UnityDb_log.ldf, which contain Unity subscriber data 2. ReportDb.mdf and ReportDb_log.ldf, which contain Unity report data 3. TempDb.mdf and TempLog.ldf, a SQL database (not a Unity database) that contains temporary tables and intermediate results created during SQL query processing and sorting On any version of Cisco Unity running SQL 2000 (4.x through 7.x), the TempLog.ldf (located in the \MSSQL\Data\directory) may grow very large and fill up the available disk space. As a result, SQL/MSDE will not work properly and incoming calls may result in failsafe. The TempLog.ldf grows because of a checkpoint failure on the Microsoft SQL 2000 server and is resolved in a SQL 2000 hotifx available from Microsoft. For more information, see: FIX: Automatic checkpoints on some SQL Server 2000 databases do not run as expected http://support.microsoft.com/kb/909369/ Workaround: Install SQL 8.00.2187 on ALL Cisco Unity systems in your network. Even systems that are not exhibiting this behavior may demonstrate it in the future. There are two options for installing SQL 8.00.2187: 1) Run Server Updates Wizard (SUW) on the Cisco Unity server. Versions of SUW from May 2008 and later will install SQL 8.00.2187. For more information on SUW, as well as download locations, see: http://www.cisco.com/en/US/docs/voice_ip_comm/unity/updates/wizard/2009cuupwz.html 2) Download SQL 8.00.2187 or later (Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187) directly from Microsoft and install on your Cisco Unity servers. Additional Information: FIX: Automatic checkpoints on some SQL Server 2000 databases do not run as expected http://support.microsoft.com/kb/909369/ Cumulative list of the hotfixes that are available for SQL Server 2000 SP4 http://support.microsoft.com/kb/894905/ How to identify your SQL Server version and edition http://support.microsoft.com/kb/321185/

Conversation does not log call handler exit reason properly , Fixed CSCeg07962

Symptom: Call Handler exit methods are not logged accurately in the System Call Handler Traffic Report. Condition: Cisco Unity 4.0(4) and earlier when running the System > Call Handler Traffic report from the Cisco Unity Administrator. Workaround: For 4.0(4), ES56 is available to fix this problem. This problem is fixed in 4.0(5) and later.

Bulk Subscriber Delete fails to delete subscriber's CH , Terminated CSCtc95079

Symptom: Bulk Subscriber Delete or deleting subscribers left orphan call handers.
Conditions: This is a very rare situation. Unity 7.0(2) with Exchange 2003. When deleting subscribers using Bulk Delete or SA webpage, Unity fails to delete the associated CH of the deleted user. Once the CH is orphan, can't add the same extensions back in Unity.
Workaround: Using SQL Enterprise Mgr, locate the CallHandler table and delete the ch_ row of the orphan entry.
Further Problem Description:

Using BulkEdit tool to change password results in blank password , Fixed CSCsr02403

Symptoms: Password is blank after changing it via BulkEdit tool
Conditions: This problem may occur in Unity 4.2(1) and Unity 5.0(1). The issue is fixed in Unity 7.0(2) and later.
Workaround: You can manually set the password via SAWeb Or, to use Bulk Edit but avoid the defect, perform the following before running Bulk Edit. Open a command prompt (DOS) and go to \CommServer\components The type in the following commands; Regsvr32 /u BabelSvr.dll Regsvr32 BabelSvr.dll

MSCW exits without error when trying to connect to Exchange partner . , Fixed CSCsd99610

Symptom: When the Exchange mail store location is chosen in the Message Store Configuration Wizard (MSCW), the wizard exits with no error message.
Conditions: This is usually caused by a failure to move the Unity_ServerName mailbox when the partner server is changed. In the TEMP directory in file tempu.log, the following diagnostic makes the server change clear: Original Exchange server: ORIGINAL_SERVER_NAME Selected Exchange server: NEW_SERVER_NAME
Workaround: In Active Directory Users and Computers (ADUC), use the "Find" function to search for "Unity_". Right-click and choose "Exchange Tasks". Use the wizard to move the mailbox to the new partner server. Then re-run the MSCW.
Further Problem Description: In the vast majority of cases, the core of the problem here is that Microsoft KB 883652 was included in Exchange 2003 SP2 but this was not included in the SP Release Notes, and a Microsoft Exchange SDK update was not provided. Furthermore, the change in KB 883652 violates the rules of COM by redefining an existing interface, which should be immutable. This causes problems in existing applications since they are trying to use the older interface, when the newer interface is installed (by SP2) but has the same IID. The particular method changed was MoveMailbox, which is used by the MSCW if the partner server is changed. The problem is fixed in Unity versions greater than 4.2. A software fix for the affected, released versions of Unity would take longer to apply than the work-around. Further troubleshooting or work-arounds: Make sure the Unity_servername account has a mailbox in the first place. If the Unity_ServerName account in AD does not have a mailbox, use ADUC to add an Exchange mailbox.

WS03: Cannot log back in to SA after timeout , Fixed CSCsc86904

Symptom: Cisco Unity administrators are unable to access the Cisco Unity System Administrator via Internet Explorer.
Conditions: This issue impacts Unity 4.2(1) and Unity 5.0(1) servers that run on Microsoft Windows Server 2003, typically after an SA session has timed out. This issue is fixed in the latest Unity 4.2(1) and 5.0(1) ES. This issue is also fixed in Unity 7.0(2) and later.
Workaround: 1) Restart the WWWP service. or 2) Increase the SA Session Timeout value in Internet Information Services (IIS) Manger from the default of 20 minutes to 180 minutes, or more. Additionally, there is evidence that the issue can be worked around by setting the Idle Timeout to a value lower than the SA Session Timeout. This doesn't prevent the problem, but it does decrease the chances of running into the problem. Following are detailed steps to increase both the session and the idle timeout values, and to set the idle timeout to a value less than the session timeout. To Increase the Session Timeout 1. Go to Start->Programs->Administrative Tools->Internet Information Services (IIS) Manger. 2. In the left-hand pane, expand the tree for the local computer. 3. Right-click the Default Web Site and select Properties. 4. Click the Home Directory tab. 5. Click the Configuration button. 6. On the Application properties sheet, click the Option tab. 8. Increase the session timeout from the default 20 minutes to the desired number (180 minutes or more, is fine). To Change the Idle Timeout 9. In IIS Manager, expand the "Application Pools" folder. 10. Right-click on "DefaultAppPool" and select Properties. 11. Select the "Performance" tab. 12. Change the value in "Idle timeout" to a couple of minutes less than the session timeout for the SA. 13. Press "Apply". 14. Restart the "DefaultAppPool" The result will be that after the timeout fires, the browser window will either close on its own or a dialog box will appear asking if you wish to close the window. A new SA session can be opened by the Unity icon in the System Tray. If you don't see the Application Pools container in IIS Manager, do the following steps to display Application Pools and then adjust the Idle Timeout. (See CSCsi42693 for additional problems that happen when the Application Pools is not displayed in IIS Manager.) To Display Application Pools 1. Open IIS Manager (Click Start > All Programs > Administrative Tools > Internet Information Services (IIS) Manager.) 2. Expand the tree in the left pane. 3. Right-click Web Sites and select Properties. 4. Click the Service tab. 5. In the Isolation Mode section at the top of the page, uncheck the check box "Run WWW service in IIS 5.0 isolation mode". 6. Click OK on the message box to restart IIS. The Application Pools container should now be displayed 7. Close IIS Manager.

Unity 4.2 ENG failsafe on accessing mailbox with * , Fixed CSCse95939

Symptom: Dialing from external PSTN/Mobile phone, users are unable to enter their mailbox after pressing *. They will hear the "system is unavailable" failsafe message. Steps to reproduce: Call from outside (or any extension not associated with a subscriber) to subscriber that has CallForward into Unity. On hearing the subscriber's greeting, press * to access mailbox. Then enter username and password followed by hash. Failsafe is generated.
Condition: ML Unity with ENG loaded, and Default Phone Language set to ENG (UK English). This problem occurs in Unity 4.2(1). The problem is fixed in Unity 5.0(1) and later.
Workaround: This issue can be resolved in Unity 4.2(1) by applying a new SubSignIn_ENG.ps script file that is available from Cisco TAC.

Unity plays deleted e-mail when Text to Speech is disabled on subs COS , Terminated CSCsb97196

Symptom: When a user decides to play their deleted voicemail messages on Unity 4.0.4 SR1, their e-mail messages are played back in addition to their voicemail messages. But their e-mail messages are not played in the In Box.
Conditions: COS on Unity 4.0.4 SR1 is disabled 1. Turning on Deleted Messages in COS > Messages > checking Deleted Messages are copied to the deleted items folder 2. COS > Default Subscriber Template > Licensed Features > Tet-To-Speech for email messages is unchecked. 3. A user who logs into his/her mailbox and presses 3 > 2 > 1 will hear their delete email messages.
Workaround: None

Unity - Add timer for Message Notification caller input... , Open CSCtd21075

This is a request for a feature enhancement. When Message Notification calls them and they are prompted to enter the extension, Message Notification is often turned off during many of their extensions start with 1. They are looking for a wait to extend the time allowed to enter extension before notification is disabled just as with Caller Input extensions. Customer has older version of Unity (4.0(5)), but I do not find on any later version.

MSCW fails to create mail files for default accounts , Terminated CSCsr92707

Symptoms: After a new installation of Cisco Unity with IBM Lotus Domino, in which everything seems to have gone fine, when you open the Cisco Unity System Administrator (SA), and click the Subscribers link, a page is displayed that contains only the following text: error '8004010f' /Web/Common/include/SaConstInc.asp, line 122 You may also see the following error in the Application Log in Event Viewer: Event Type: Error Event Source: CiscoUnity_UMR Event Category: UMR Thread Error Event ID: 137 Description: Attempts to deliver Unity Message Repository messages have failed due to Unity configuration or connectivity issues with the Partner Mail Server. AvUMRSyncSvr will suspend message delivery for 300 s At this point, Cisco Unity will not be able to deliver messages because a mail file for the default user, Unity Messaging, was not created during Message Store Configuration Wizard (MSCW), which is one of the wizards launched from the Cisco Unity Installation and Configuration Assistant (CUICA). In fact, MSCW failed to create mail files for all three default users: Example Administrator, Unity Messaging, and UnityBroadcast [UnityServerName]. If you look in the Domino Administrator, you will see these users listed in the Domino Directory, but when you open their Person documents, the Mail Server and Mail File fields are empty, and their mail files are not on the Domino server. The default users must have mail files in order for Cisco Unity to function properly.
Conditions: This problem has been observed on the following configurations using DUC 1.2.5: -- Cisco Unity 5.0(1) partnered with a Domino 8.0.1 server running on Novell SUSE Linux Enterprise Server (SLES) 10. -- Cisco Unity 7.0(2), partnered with a Domino 8.5 server running Windows, and there are no earlier versions of Domino in the Domino domain. However, the problem could exist in other versions of Cisco Unity, Domino, and DUC. In Cisco Unity 7.0(2), and later, if there are any errors during the creation of the default users, MSCW is supposed to display an error message, and fail. CUICA will not allow you to continue with the setup until MSCW runs successfully. Note however, MSCW may not detect all error conditions that cause the creation of the mail files for the default accounts to fail, and MSCW 7.0(2) may complete without displaying an error message.
Workaround: If the Notes client was successfully installed and configured on the Cisco Unity server prior to launching CUICA, there are several known reasons why MSCW can fail to create mail files for the default users: 1. The UnityServers group does not have permission to create databases and templates in Domino. (This problem was originally reported in CSCsj57016.) 2. The mail file template that MSCW uses to create the mail files for the default users does not exist on the Domino server that Cisco Unity is partnered with. This can happen in a Domino 8.5 configuration where the only mail template on the partner server is mail85.ntf. 3. The network connection with Domino is very slow, and MSCW hits a timeout period while attempting to create the default users. The workaround in this Release Note Enclosure deals with the first two problems. If the workaround does not fix things such that MSCW can create mail files for the default users, see the Further Problem Description for the traces that you need to enable and to provide to Cisco TAC for further assistance. To Make Sure that UnityServers Has the Needed Permissions 1. Open the Domino Administrator. 2. Click the Configuration tab. 3. In the left pane, open the Server document of the Domino server that was specified in MSCW. 3. Click the Security tab. 4. In the Create Databases and Templates field, add UnityServers if it is not already there. 5. Close the Server document. Also check the following, just as a precaution. MSCW usually detects these problems, and displays an error message that indicates what the problem is, but it is best to verify the needed configuration before continuing. 1. Click the People & Groups tab, and then click People in the left pane. 2. Locate the Unity Person document. (This is the user that the Notes client on the Cisco Unity server was configured for.) 3. Open the Person document and make sure the Mail Server and Mail File fields are filed in. 4. Click the Groups tab. 5. Make sure there is a group called exactly "UnityServers" -- no other spellings are allowed. 6. Open the UnityServers group document. Make sure that the Unity Person is in the group, and close the document. 7. Click the Files tab. 8. Right-click on admin4.nsf and select Access Control > Manage. 9. Make sure UnityServers is there, and that when you click on it, the Attributes say Editor. Close the ACL for admin4.nsf. 10. Right-click on names.nsf and select Access Control > Manage. 11. Make sure UnityServers is there, and that when you click on it, the Attributes say Editor and the Delete Documents check box is checked. Close the ACL for names.nsf. If the UnityServers group had all of the correct permissions, do the following: Add a MailFileTmplt Registry Key to the Unity Server 1. On the Unity server, open regedit. 2.. Expand the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Directory Connectors\DirSynchDomino\1.00 3. Add a new String value called: MailFileTmplt 4. Double-click MailFileTmplt. In the value data field, enter the name of a mail template that is available on the Domino partner server. For example, enter: mail85.ntf 5. Click OK, and close regedit. Now clean things up in the Domino Directory, and then re-run MSCW /sync, as follows: Get the Unity Server SystemID 1. On the Unity server with the problem, open regedit. 2. Expand the key: HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Doh\1.0 3. Write down the hex value in SystemID, and then close regedit. Delete the Default Users 4. Start the Domino Administrator. 5. Click the People & Groups tab. 6. In the left pane, click People. You will see the following users: Example Administrator, Unity Messaging, and UnityBroadcast [UnityServerName]. If you have more than one Unity server, you will see these three users for each Unity server. For UnityBroadcast, it is clear which Unity server the user is associated with. But for Example Administrator and Unity Messaging, you have to open the Person documents, and make sure that the number appended to the name in the Short Name field matches the System ID that you wrote down in step 3 above. Repeat steps 8 through 11 for Example Administrator, Unity Messaging, and UnityBroadcast [UnityServerName]. 8. Open the Person document. Confirm that the Mail Server and Mail File fields are blank. This means that the mail file was not created. 9. Close the Person document 10. Click Delete Person. 11. On the Delete Person dialog box, check the box "Delete Users from the Domino directory immediately" and click OK. Delete the Default Groups 11. In the left pane, click Groups. You will see the following groups: allsubscribers[SystemID], systemeventmessages[SystemID], unaddressedmessages[SystemID] The [SystemID] matches the system ID that you wrote down in step 3. If you have more than one Unity server already installed, you will see these three groups for each Unity server. 12. Click allsubscribers and press the space bar to put a check next to it. Repeat to put check marks next to systemeventmessages and unaddressedmessages. 13. Click Delete Group. 14. On the Delete Group dialog box, check the box "Delete groups from the Domino directory immediately" and click OK. Delete the Default Unity Location 15. Click the Files tab. 16. In the Show Me dropdown list above the list of files, select Databases Only. 17. Double-click names.nsf to open it. 18. Within the Configuration tree in the left pane, double-click Unity Locations. In the middle pane, you will see a location called default [SystemID]. The [SystemID] matches the system ID that you wrote down in step 3. If you have more than one Unity server already installed, you will see a default location for each Unity server. 19. Click default [SystemID] and press the space bar to put a check next to it. 20. Click Edit > Delete. 21. Press F9. On the popup message box, click Yes to confirm the deletion. 22. Close names.nsf. Rerun the Message Store Configuration Wizard with the /sync Flag 23. On the Unity server, open a command prompt window. (Click Start > Run. Enter cmd. Click OK.) 24. Change to the drive and directory that Unity is installed in. For example, if Unity is installed in D:\CommServer, enter the following in the cmd window: d: cd CommServer 25. Change to the ConfigurationSetup folder: cd ConfigurationSetup 26. Enter the following to launch Message Store Configuration Wizard again: setup /sync 27. Follow the on-screen prompts. Confirm that the Default Users have Mail Files 28. Go back to the Domino Administrator. 29. Click the People & Groups tab. 30. In the tree in the left pane click People. 31. Open the Person documents for Example Administrator, Unity Messaging, and UnityBroadcast [UnityServerName] and confirm that the Mail Server and Mail File fields have been filled in.
Further Problem Description: If after doing the above workaround the default users still do not have mail files, do the following to gather the applicable log files to send to Cisco TAC. 1. Repeat the above steps to delete the default users, groups, and Unity location from the Domino Directory. 2. On the Cisco Unity server, click Start > Programs > Unity > Unity Diagnostic Tool. 3. Click Configure Micro Traces. 4. Click Next. Scroll down the list and enable the following micro traces: -- DsDomino -- NotesCommon 5. Click Next and then Finish. 6. Click Start New Log Files. 7. Follow the steps above to rerun MSCW /sync. 8. Back in the Unity Diagnostic Tool, click Gather Log Files. 9. Click Select Logs, then click Next. 10. Click the + icon next to AvDsDomino. 11. There will be at least two diag files listed. The most recent one with the trace info from the last run of MSCW should be at the bottom of the list. If you are unsure, select the first two or three from the bottom, then click Next. 12. Click View Directory. 13. The file with the traces enabled will be significantly larger than the one without the traces. To be sure, double-click on the file to open it in Notepad. Confirm that the time listed in the file corresponds to the time that you ran MSCW with the traces enabled. Close the file. Copy this file and send it to Cisco TAC for further assistance. 14. When you are finished troubleshooting with Cisco TAC, unless instructed otherwise, be sure to click Reset to Default Traces in the Unity Diagnostic Tool. Having more than the default traces enabled on a busy Cisco Unity server can take up significant disk space, so you'll want to reset the tracing to the default level.

PermissionsWizard - Sometimes takes many hours to complete , Fixed CSCsb01328

Symptom: Permissions Wizard takes a couple hours or longer to complete.
Conditions: Version 2.1.0.30 or earlier of Permissions Wizard.
Workaround: There is no workaround.
Further Problem Description: ADSI is taking a very long time to update security descriptors.

Unity AvRdbSvr connection to SQL database fails in some instances , Fixed CSCdw91072

Symptom: Callers dialing in to the Cisco Unity system may hear fail-safe message occasionally
Condition: This may happen in Unity version 3.1.X due to Unity losing connection to the SQL database. This can be confirmed by the event viewer error message, Event Type: Error Event Source: AvRdbSvr_MC Event Category: Startup Event ID: 21000 Description: Last Category Failed connecting to underlying database using: provider=SQLOLEDB;driver={SQL Server};Data Source=CISCO-M67DC9AQ4;Initial Catalog=UnityDb;Integrated Security=SSPI: 80004005
Workaround: Stop and restart Cisco Unity services

MSCW Syncer should confirm before creating users in AD , Terminated CSCsq61986

Symptom: Sometimes when running Message Store Configuration Wizard (MSCW), it will create duplicate user accounts in Active Directory for all current Unity subscribers.
Conditions: We have only seen this issue occur when running MSCW on an inactive Unity failover server
Workaround: If you have had duplicate AD accounts created you can perform one of the following to resolve the issue: You can use the Migrate Subscriber Data Tool (http://ciscounitytools.com/App_MigrateSubscriberData.htm) to change the Unity subscriber to use the correct AD account again. You will then need to delete the invalid AD accounts. or Stop AvDSAD and AvDSGlobalCatalog services from services.msc. Delete duplicate AD accounts and set the directoryid field in the subscriber table in SQL to NULL. Then run \commserver\configurationsetup\setup.exe /sync on the Unity server so it gets the correct directoryid for the users. or (1) Force Unity into UMR mode by following steps 1 - 4 here http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note 09186a0080117807.shtml#topic2 (don't do step 5. don't restart any Unity services) (2) Install COBRAS export on the Primary Unity server and run it to export all of your subscribers including their voice messages: http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html (See the help link on that page as well for more details on usage of this tool). (3) Stop the following two services on the Primary unity server: AvDSAD AvGlobalCatalog (4) Delete the duplicate accounts from active directory (a) Right-click on the NA -> USERS OU, select Find (b) Select "Custom Search" from the drop-down (c) Select the Advanced Tab (d) Enter CiscoEcsbuUMLocationObjectID=* (e) Click Find (f) Locate the 7 accounts which should not be deleted. Move them to a different OU temporarily (not a child OU). (g) Delete the remaining duplicate accounts from the Users OU (5) Run the following command from the command prompt on the Unity server: osql -E -Q "use unitydb update Subscriber SET DirectoryId = NULL" (6) Start the following two services on the Primary unity server: AvDSAD AvGlobalCatalog (7) Run the following command from the Start menu: D:\CommServer\ConfigurationSetup\Setup.exe /sync (8) Remove the registry keys previously set in step 1 (9) Install COBRAS Import on the Primary Unity server and run it to import the back-ups of message that you took in Step 2: http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html (See the help link on that page as well for more details on usage of this tool).

Unity - User Network Drops While Call Viewer Open Causes Failover/RNA , Fixed CSCsy68991

Symptom: Unexpected failovers/RNA when network connection to Unity server drops while using RDP and Call Viewer
Conditions: Seen on Windows 2000, Windows 2003 Unity 4.2(1), Unity 5.0(1) Call Viewer v5.0.1.0 Windows Remote Desktop (RDP) is used to connect to the primary Unity server in a fail over pair. Call Viewer is opened in order to monitor calls coming into the server. While Call Viewer is open, if the NIC of the user's machine becomes disabled, or network connectivity drops, RDP puts up its generic error that connectivity to the server has been lost. The very next call presented to the primary will RNA, and cause a fail over. If Unity is standalone (without fail over) calls to voice mail will RNA and users are unable to retrieve voice mail.
Workaround: Do not use RDP in conjunction with Call Viewer. VNC viewer can be used instead. To get Unity answering again: For failover configurations- fail back to the primary For standalone configurations- restart Unity from the system tray
Further Problem Description: NOTE: Fixed in 5.0(1)ES73 and later...

DUC: :ucprofilecountchange remains on mailbox after unity removal , Fixed CSCsl10216

Symptom: Unity application event log shows: CiscoUnity_DominoMonitor 1006 Domino notification received for user not monitored: user database=, handler=unitynotifier f69212f, data=, event=CountChange. If this user was recently imported, the MailBox will be monitored when the corresponding UCAdmin Event is successfully processed. 0x00001EE0
Conditions: Unity using a Domino backend that a Unity Subscriber has been moved to another Unity Server and the original Unity Server is still on-line.
Workaround: Rebuild the affected user mailbox in domino strarting from scratch then reimport into Unity. -or- Use Lotusscript to removed the incorrect profile "ucprofilecountcahnge - unitynotifier XXXXXXX" where XXXXXXXX is NOT the current unity system ID. To find the current unity system ID, on the Unity Server that the Subscriber is currrently on, open a cmd prompt: osql -E -d UnityDb -Q "select value from UnitySetupParameters where name='@systemid' "
Further Problem Description: To verify: Use NotesPeek and open the user database reference in the application event log entry. Open the Profiles Section and see if there is more than one entry for "ucprofilecountchange - unitynotifier XXXXXXX" Where XXXXXXXX is a hexadecimal string refering to the UnitySystemId. Currently, the Agent "Remove Subscriber Properties from Notes" on ciscounitytools does NOT address this issue.

Note on 3GB switch on large port systems is too generic , Fixed CSCsq78907

Symptom: Unity Systems with greater than 96 ports (with DC/GC and/or Exchange onbox) can see crashes and system instability due to Desktop Heap Exhaustion issues. Also noted that Profile Page and Alternate Extension web page may show blank during time of issue. Other symptoms include DCOM error seen in the event log: Event Type: Error Event Source: DCOM Event Category: None Event ID:10010 Date: 6/3/2008 Time: 10:29:08 AM User: N/A Computer: UNITY Description: The server {70722675-CFCA-42F9-98E6-74F6E7AD042A} did not register with DCOM within the required timeout. For more information, see Help and Support Center at . Also can see the following error message: Event Type:Warning Event Source:Win32k Event Category:None Event ID:244 Date:11/4/2009 Time:10:00:46 PM User:N/A Computer:UNITY Description: Failed to create a desktop due to desktop heap exhaustion. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 01 00 56 00 ......V. 0008: 00 00 00 00 f4 00 00 80 ......? 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........
Conditions: The customer might have turned on the 3GB switch in the boot.ini file as per the installation guide http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/installation/guide/vmexfo/5xcuigvmefo040.html#wp1616291). or due to an event log warning.
Workaround: Fine tune the registry key settings HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\SubSystems\Windows http://support.microsoft.com/default.aspx?scid=KB%3BEN-US%3B184802 Or alternatively move the DC/GC or Exchange offbox

Unity TSP can loop continuously when dialout MWI to CME , Fixed CSCsc74166

Problem Symptom: When Cisco Unity TSP is performing MWI dialout to the Cisco CallManager Express integration, the TSP may be sent into a tight loop that appears to continuously dialling out to the CCME MWI port. Additional Information: - Cisco Unity TSP 8.1(1), 8.0(2b) - Cisco Unity 4.0(5), 4.1(1) - Cisco CallManager Express v3.3 - IOS version 12.3(14)T5 SPSERVICES
Conditions: Cisco Unity is configured for dual integration, with Cisco CallManager and Cisco CallManager Express (CCME).
Further Problem Description: Unity MWI dialout currently does not identify specific clusters when multiple integrations exist. It appears that a corner case is hit, when multiple Unity MWI dialout occurs, instead of receiving dialtone, it receives ALERTING/Proceeding signal from CCME, as if there is a call already in progress. There is a possibility that CCME is not placing the previous call on-hook fast enough for the Unity TSP to be ready for the next MWI dialout call. The kick-on effect is causing the TSP to reduce to a tight loop, to appear to be dialling out MWI.

Bulk import not following the correct permissions to import users , Fixed CSCsv74427

Symptom: When trying to import users from Exchange using the Unity 7.0 Bulk Import tool the tool fails with the message "Problems with the header fields. Please view the error log for details." The error log has these details (Error) [DISPLAY_NAME] is an invalid column header for the type of import. To correct the problem, confirm that the column header is appropriate for the type of subscriber you want to create and for the type of import you are trying to perform. Additionally, if you are trying to create Bridge enabled subscriber accounts, confirm that the directory has been configured such that Cisco Unity can store the information required for Bridge Networking. Refer to the Cisco Unity Bridge Networking Guide for details. Furthermore, if you are setting DISPLAY_NAME or HIDE_IN_ADDRESS_BOOK, please make sure that "Allow Cisco Unity to Administer Active Directory" is set in Permission Wizard. Full header: ALIAS,LAST_NAME,FIRST_NAME,DTMF_ACCESS_ID,DISPLAY_NAME,RESERVED2
Conditions: Unity 7.x CUBI and Permission wizard was run with the setting to not allow Unity to create objects in AD which sets the registry key HKLM\SOFTWARE\Active Voice\PermissionWizard\1.0\Restricted Rights to 1
Workaround: Change HKLM\SOFTWARE\Active Voice\PermissionWizard\1.0\Restricted Rights to 0, import the users with CUBI and then change it back to 1.

Upgrades fail after DIRT restore with a new server name , Fixed CSCsk27633

Symptom: Upgrades fails after performing a DIRT restore.
Conditions: - Perform a DIRT backup - Perform a DIRT restore to a new hardware platform and/or a new server name. - After performing the DIRT restore there will be references to the old Unity server name and the new Unity server name in the Servers table in SQL. In addition to this the SchemaMajorVersion and SchemaMinorVersion fields in the Servers table in SQL was set to NULL for the new server. - When you attempt to upgrade it will fail and the following error is displayed when Cisco Unity Setup attempts to execute the SQL scripts: FATAL UPGRADE ERROR: Schema version is not present. B>Workaround: Contact TAC for assistance as this requires making manual changes to the SQL database.

Fix for CSCsr90209 puts TestWritableDomainController.xml in only ENU , Fixed CSCtb46143

Symptom: The Message Store Configuration Wizard cannot be run, and returns only "This wizard cannot install Cisco Unity on your computer because of the following reasons".
Conditions: Unity 5.0(1) or 7.0(2); with ES57 or higher for Unity 5.0, or ES4 or higher for Unity 7.0. Unity server has been installed using the ENG locale, without the ENU locale. If ENU was installed, then please also see CSCsv47328 as a possible cause (not having run the TestWritableDomainController.exe executable provided with the ES patches).
Workaround: Copy the TestWritableDomainController.xml file, from the "\Commserver\SysCheck\ENU\Domain" folder to the "\Commserver\SysCheck\ENG\Domain" folder.

AXP 1.5.1 has severe decline in performance compared to prev. releases , Open CSCtc62474

Symptom: AXP 1.5.1 has significant decline in peformance
Conditions: Memory allocation via mlock and other performance related functions such as dnsQuery show marked decrease in performance.
Workaround: None
Further Problem Description:

Unity 7 Caller System Transfer will not transfer to DNs with *'s , Terminated CSCtc84954

Symptom: Unity 7.0(2) Caller System Transfer does not allow transfers to numbers that include *
Conditions: Hitting the * key during the Caller System Transfer immediately results in a rejected transfer regardless of the transfer restriction table setting. This worked in previous versions of Unity.
Workaround: None

Enabling Unity Failover Should Enable Minimum Amount of Diagnostics , Open CSCsz79969

Symptom: Cause of Unity failover can not be determined with the default level of diagnostics enabled.
Conditions: When a Unity failover occurs and root cause must be determined, failback to primary Unity server must be initiated, macro diagnostic traces skinny, call flow, and conversation state traces must be enabled, and another failover event must occur before TAC engineers can deliver root cause.
Workaround: None.

RSKDataService crashes when having over 128 VM ports configured , Fixed CSCsv93981

Symptom: RSKDataService.exe crashes while trying to start this service.
Conditions: Unity 5.0(1) Single or failover environment with over 128 voicemail ports configured.
Workaround: N/A
Further Problem Description:

CSA 5.2 causes SNMP and RSKdataservice to crash , Fixed CSCsr47291

Symptom: Installing a CSA 5.2 based agent on Cisco Unity causes SNMP and RSKDataService services to crash. Drwatson events will be generated for both services. Restarting the SNMP service will start both services for approximately 30 seconds, then they stop again.
Conditions: The issue has been seen using standalone CSA for Unity versions 3.1(4) and 3.1(5). Both of these agents were built using a 5.2 CSA MC. This bug only addresses the CSA for Unity standalone agent. However, the same issue exists when using managed CSA agents. Please see CSCsu09290 for the mainline CSA bug. The failures occur even when CSA is disabled. The issue only occurs when both CSA and RSK are installed. There is no conflict between CSA and SNMP when the RSK is not installed.
Workaround: Uninstall CSA via add/remove programs and reboot the Unity server. An earlier release of CSA for Unity may be installed instead. For example, CSA for Unity 3.0(2) was built using a 5.0 CSA MC and does not cause the RSK and SNMP failures. Additional Detail CSA for Unity 3.1(4) is included in the Unity SUW 2.0(9). When RSK service is installed, do not use the CSA for Unity included in this Server Update Wizard package. The CSA for Unity 3.0(2), identified as a workaround, is available as a standalone install here: http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=3.0(2)&mdfid=280270882&sftType=Security+Agent+for+Unity+Software It is also included in the Unity SUW 2.0(8) package.

SA: Stops working due to empty NodeValue field in vw_configuration , Fixed CSCee79009
Symptom: Administrative access to the Subscribers page of the Cisco Unity System Administrator web interface returns a blank frame in the browser. A "Page cannot be displayed" error on the top frame and the rest of the page may not load. Attempts at browsing in the SA may result in an IE pop-up error. A service restart and/or reboot of the system does not change the symptom.
Conditions: Unity 4.0(4) integrated with Active Directory and Microsoft Exchange.
Workaround: This defect is fixed in Cisco Unity 4.0(4) SR1 and Cisco Unity 4.0(5) and later. For a manual workaround, see the steps below. NOTE: Running the Message Store Configuration Wizard in Step 7 below will result in Unity services stopping and unavailability of the voicemail system for approximately 5-10 minutes. 1. Open regedit. 2. Select the HKLM/software/active voice/commserver setup/1.0/private registry branch. 3. Select the 'Registry' menu and choose "Export Registry File..." 4. Choose a destination directory and filename (like "Load_after_MSCW.rgs"). 5. Ensure the "Export Range" is specified by the "Selected Branch" radio button and click the "Save" button. 6. Right-click on the HKLM/software/active voice/commserver setup/1.0/private registry key and choose "Delete". 7. Run the Message Store Config Wizard via the ...\CommServer\ConfigurationSetup\Setup.exe. Do not change any of the values displayed in the wizard. The password for the Unity Installation and Directory Services accounts will be required in the process of running this wizard. 8. After the Wizard has completed, open Windows Explorer to the directory of the registry file saved in step 5. 9. Double-click on the .rgs file saved from step 5. 10. Verify SA access to the Subscribers page now functions as expected.

Caller Input [#] not respected for call handlers , Terminated CSCsx67206
Symptom: Using the Opening Greeting call handler, configure the caller to Allow Extension dialing, and for the # key, lock the input and have the action route to Sign-in. Behavior when pressing [#] at the opening greeting: "Sorry the operator is not available." Expected behavior: "Enter your ID"
Condition: This problem has been observed in Unity 7.0(2). It is not known if this problem occurs in earlier versions of Unity.
Workaround: Unlock the [#] key and it will work properly. However, additional incoming digits could cause undesired behavior.

Unity MWI resync performance needs improvement , Fixed CSCsg64120
Symptom: Cisco Unity performance issues occur during the MWI Resync.
Conditions: This poor performance is improved in Unity 7.0(2) or later. The issue is also resolved in Unity 5.0(1)ES 43 and later.
Workaround: The MWI resync is often not required to be run nightly.
Further Problem Description: The Cisco Call Manager integration by default does not enable the MWI resync.

SA does not update CallHandler Message Recipient , Fixed CSCsk06752
Symptom: When trying to change the message recipient in System Administration, Unity allows you to save the change, but it does not get saved to the database. When you go back into the Messages settings, the old value is still there.
Conditions: This issue may occur in Unity 5.0(1). This issue is fixed in the latest Unity 5.0(1) ES, and it is also fixed in Unity 7.0(2) and later.
Workaround: Use Bulk Edit Tool in Cisco Unity Tools Depot to make the change.

Provide a way to disable sticky playback speed keys , Fixed CSCsz93254
Symptom: Unity 7.0.2 message and prompt playback speed seems to be randomly faster or slower than expected. This is most commonly reported by users of a shared mailbox.
Conditions: Unity 7.0.2 introduces a new sticky key feature for Playback Speed. This behavior is not desirable for all users. Following is a link to the release notes describing this new feature. Playback Speed Adjustments Are Saved Across Sessions http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/release/notes/702cur??elnotes.html#wp62222??
Workaround: There is no workaround.
Further Problem Description: It is important to note, this is the designed behavior of Unity 7.0.2. However, this behavior is not desirable for all users. This bug documents a feature enhancement which will allow Unity 7.0.2 to behave similar to Unity 5.0. To resolve this issue, a key called "Conversation - Do Not Save Speed Changes Made By Phone" has been added to the Advanced Settings Tool, which allows Administrators to disable the Sticky Speed feature. To make use of this key, you need to install 7.0 Engineering Special 29 or later, and download and install the latest version of the Advanced Settings Tool from www.ciscounitytools.com.

Unity 5 ES48 & 7 ES20 Missing G.729a files. , Fixed CSCsr46544
Symptom: The following errors are displayed in the application log: (MultiUse.cpp) Script: subnotifier_enu.ps (InitPrompt) -- ($FILE:d:\commserver\localize\scripts\enu\subnotifier_enu.ps $LINE:48) "AvSubNotifierENU013.wav" not found in search path "d:\CommServer\Localize\Prompts\ENU\G729a\" + "AvSubNotifier". (MultiUse.cpp) Script: subnotifier_enu.ps (InitPrompt) -- ($FILE:d:\commserver\localize\scripts\enu\subnotifier_enu.ps $LINE:49) "AvSubNotifierENU014.wav" not found in search path "d:\CommServer\Localize\Prompts\ENU\G729a\" + "AvSubNotifier". (MultiUse.cpp) Script: subnotifier_enu.ps (InitPrompt) -- ($FILE:d:\commserver\localize\scripts\enu\subnotifier_enu.ps $LINE:50) "AvSubNotifierENU015.wav" not found in search path "d:\CommServer\Localize\Prompts\ENU\G729a\" + "AvSubNotifier". (MultiUse.cpp) Script: subnotifier_enu.ps (InitPrompt) -- ($FILE:d:\commserver\localize\scripts\enu\subnotifier_enu.ps $LINE:51) "AvSubNotifierENU016.wav" not found in search path "d:\CommServer\Localize\Prompts\ENU\G729a\" + "AvSubNotifier".
Conditions: Unity 5 ES 48 G729
Workaround: Uninstall ES48 and restore original prompt files

ChangeNotesPassword utility fails , Terminated CSCsx19170
Symptom: The ChangeNotesPassword utility fails with the error: Failed to open registry key SOFTWARE\Lotus\Notes\6.0. Error 00000002
Conditions: This problem has been observed when running the ChangeNotesPassword utility on the following versions of Cisco Unity integrated with IBM Lotus Domino: 1. Cisco Unity version 7.0(2) with Notes 6.5.x, 7.0.x, or 8.0.x installed on the Cisco Unity server. 2. Cisco Unity version 5.0(1) with Notes 7.0.x or 8.0.x installed on the Cisco Unity server.
Workaround: 1. Logon to the Cisco Unity server using the account that you used to install Unity. Open the Notes client on the Unity server and change the password (File > Security > User Security). 2. In Control Panel > Add/Remove Programs, remove the Message Store Configuration Wizard (MSCW). This deletes the old user name, password, and the Domino server name used by Unity. 3. Rerun MSCW (\CommServer\ConfigurationSetup\Setup.exe). You'll get prompted to verify the Domino server and re-enter the Notes password. MSCW will stop and restart the Unity services.

Missing stored procedures after running scripts in UnitydbEx , Fixed CSCsv24693
Symptom: Running the Failover Configuration Wizard or ConfigMgr Tool to restore stored procedures found in UnitydbEx.sqlUnityDbEx.sql on the Cisco Unity server results in the following error, found in the latest OSQL* file in Commserver\Logs. Dropping remaining stored procedures Msg 3729, Level 16, State 1, Server xxxxx, Line 2 Cannot DROP PROCEDURE 'dbo.fn_MatchString' because it is being referenced by object 'CN_TextName'
Condition: This problem will occur on a system that has had one of the following ESs installed: 4.2(1)ES162 5.0(1)ES56 7.0(2)ES9
Workaround: Obtain the appropriate non-Unity patch: Unity 4.2(1) -- Patch 111 Unity 5.0(1) -- Patch 112 Unity 7.0(2) -- Patch 113 Follow the instructions provided with the patch to recover your Unity system, and to start Unity upgrade or installation again. Then install the ES appropriate to your Unity version, from the following list: 4.2(1)ES166 or higher 5.0(2)ES65 or higher 7.0(2)ES17 or higher

running schemasetup errors out , Fixed CSCsk10833
Symptom: Running ADschemaSetup.exe results in an error: Event Type: Information Event Source: Application Error Event Category: (100) Event ID: 1004 Date: 8/16/2007 Time: 8:29:16 AM User: N/A Computer: <system name> Description: Reporting queued error: faulting application ADSchemaSetup.exe, version 0.0.0.0, faulting module msvcrt.dll, version 7.0.3790.3959, fault address 0x00038e21.
Conditions: Microsoft Windows 2003 Unity 5.0(1)
Workaround: Extend the schema manually by running one or more of the following commands from the command line (the first command is required): For all Unity systems, the ldifde command line is: ldifde.exe -i -k -c "" "" -s "" -f " \ Schema\LdifScripts\avdirmonex2k.ldf" -j "" If you are using the Cisco Unity Bridge, also run: ldifde.exe -i -k -c "" "" -s "" -f " \ Schema\LdifScripts\omnigateway.ldf" -j "" If Unity system is using VPIM also run: ldifde.exe -i -k -c "" "" -s "" -f " \ Schema\LdifScripts\vpimgateway.ldf" -j "" where: is a literal value is the distinguished name for the domain in which you want to extend the schema. For example, for a domain named voice.cisco.com, you would use "CN=Configuration,DC=voice,DC=cisco,DC=com" is the DC on which you want to run the command is the location where you want log files to be saved For additional information on ldifde, see: - Win2003: http://technet.microsoft.com/en-us/library/cc755456.aspx - Win2008: http://technet.microsoft.com/en-us/library/cc730865.aspx

PDL Import Fails when names.nsf contains large number of groups , Open CSCtd29669
Symptom: Unity 7.0(2) Domino Integration When trying to import new Public Distribution Lists in the Unity server using the web administration page, the ability for the administration to display the list of groups from the Domino names.nsf fails when the number of groups is quite large.
Conditions: When the number of groups, which are what become the Public Distribution Lists, is quite large the web administration page will fail. The maximum number of groups is not known, but in one customer environment the group count is greater than 12,000.
Workaround: None Known
Further Problem Description:

Cannot record greeting during first time enrollment (failsafe) , Fixed CSCtb63313
Symptom: First Time Enrollment will failsafe before the default greeting is played or a new greeting can be recorded.
Conditions: A Subscriber's greeting type is set to "Blank" in either the Subscriber Template (on import or create) and/or the Subscriber record itself (after import or create).
Workaround: Change the greeting type to "System". The default will then be constructed from the voice name and Cisco Unity prompts. First Time Enrollment will then succeed and allow recording the greeting.

Unity has IP Port conflicts with DNS after MS08-037 installed. , Fixed CSCsv54175
Symptom: Cisco Unity fails to start after a reboot. Using SIP integration Event Type:Error Event Source:CiscoUnity_Miu Event Category:Init Event ID:602 Description: Miu Sip Integration failed to complete initialization on one or more ports. Event Type:Error Event Source:CiscoUnity_CsServices Event Category:Init Event ID:1021 Description: AvCsMgr: Component Miu initialize failed. Turn on diagnostics for component Miu to troubleshoot. Technical Details: IAvCsComponent::Initialize failed with error [0x80004005; E_FAIL] Event Type:Error Event Source:CiscoUnity_CsServices Event Category:Error Event ID:1009 Description: AvCsMgr service failed to initialize the component manager.
Conditions: Cisco Unity 4.x or higher Microsoft DNS Server (not Microsoft DNS Client) on the Cisco Unity server SIP integration Microsoft DNS Server patch has been installed : http://support.microsoft.com/default.aspx/kb/953230 MS08-037: Vulnerabilities in DNS could allow spoofing (or higher, verify with Dnsapi.dll has 5.2.3790.3161 or higher) 1300x port is used by DNS (verify with netstat -anb)
Workaround: Uninstall DNS patches so Dnsapi.dll has version lower than 5.2.3790.3161 Reboot system may clear it Another workaround is to disable the Microsoft DNS Server service, and then to start Cisco Unity. Cisco Unity starts since Microsoft DNS Server has not reserved the ports yet. Then, you can start the Microsft DNS Server service once Cisco Unity is started. This issue has been resolved in Cisco Unity 4.2(1)ES168 and later, 5.0(1)ES67 and later, 7.0(2)ES19 and later.

AvCsMgr should have a dependency to Gateway to prevent being set to AUTO , Terminated CSCsb08982
Symptom: The following error message can occur if AvCsMgr comes up before AvCsGateway Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7031 Date: 5/29/2005 Time: 6:22:17 AM User: N/A Computer: Description: The AvCsMgr service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Condition: This can occur with any version of Unity, and has been seen to occur when the AvCsMgr service start up type is set to automatic.
Workaround: Ensure AvCsMgr service is set to Manual start up type.

Unity 7.0(2) - Bulk Import Exchange Overwrites AD Display Name w/ Alias , Fixed CSCsr16712
Symptom: Display Names are being overwritten in AD when users are imported into Unity 7.0(2) when either "Active Directory" or "CSV" options are used. For the CSV imports, the problem lies with leaving out the DISPLAY_NAME column in the .csv, it's not pulling the Display Name from AD like the tool says it should, it's simply overwriting the Display Name in AD with the ALIAS.
Conditions: Unity 7.0(2) Exchange 2003 and 2007 This issue is fixed in Unity 7.0(2) ES8 and later.
Workaround: This issue is fixed in Unity 7.0(2) ES8 and later. A possible workaround aside from applying the Engineering Special: Use .CSV method and make sure to put DISPLAY_NAME column in the .csv and type in the Display Name you want to have in AD/Unity for each user otherwise it will overwrite that field with the user's alias. Manually typing in hundreds of subscriber's Display Names may not be practical but that's all that can be done at this point.

DSAD Directory monitor fails to monitor other domains , Fixed CSCee50903
Symptom: The following errors are logged in the application event log: Event Type: Error Event Source: CiscoUnity_DSAD Event Category: Error Event ID: 1100 Date: 5/6/2004 Time: 10:51:03 AM User: N/A Computer: Description: The Cisco Unity service that monitors Active Directory (AvDSAD) failed to synchronize data for an object in Active Directory with the corresponding data for the object in the SQL Server/MSDE database on the Cisco Unity server. Unity will not be able to synchronize all changes for this object until this is resolved. However, other objects will continue to be synchronized. Type: AVOBJECTTYPE_MAILUSER Name: CN=SOlivier,CN=Users,DC=child1,DC=goblin,DC=ecsbu-lab-sea,DC=cisco,DC=com Reason: 0x8000FFFF 0x8000FFFF: Catastrophic failure For more information, click: http://www.CiscoUnitySupport.com/find.php Event Type: Error Event Source: CiscoUnity_DSAD Event Category: Error Event ID: 1100 Date: 5/6/2004 Time: 10:51:46 AM User: N/A Computer: Description: The Cisco Unity service that monitors Active Directory (AvDSAD) failed to synchronize data for an object in Active Directory with the corresponding data for the object in the SQL Server/MSDE database on the Cisco Unity server. Unity will not be able to synchronize all changes for this object until this is resolved. However, other objects will continue to be synchronized. Type: AVOBJECTTYPE_SCOPE_DISTLIST Name: CN=ScopeDLTest,CN=Users,DC=child1,DC=goblin,DC=ecsbu-lab- sea,DC=cisco,DC=com Reason: 0x8000FFFF 0x8000FFFF: Catastrophic failure For more information, click: http://www.CiscoUnitySupport.com/find.php
Conditions: When all subscribers are in one domain, the AvDSAD directory monitor only monitors that domain by default. However when a subscriber is a member of a DL in another domain, the AvDSAD directory monitor should add that domain to the list of domains that it monitors at the point it attempts to sync the member of properties for that subscriber. This is not happening. In addition if a scope distribution list contains members in another domain, the AvDSAD directory monitor should add that domain to the list of domains that are monitored however this is not happening. Note that these errors may also be reported if the domain is not reachable as well. To verify that you are running in to this condition, check the ADDomain table in the SQL UnityDB to see if the other domain is listed as a domain to be monitored.
Workaround: If you are running in to this condition, make sure you have rights in the other domain, and import a subscriber from that domain. This should populate the other domain in to the ADDomain table. Once you have done this you can delete the imported subscriber, and make a changed to the user reported in the application event log error and wait for the next directory sync cycle which should correct the problem. Alternatively you can do a total resync once the other domain is populated in the ADDomain table.