Guest

Cisco Unity

Error Messages When Running Directory Walker on Cisco Unity

Document ID: 28785

Updated: Dec 03, 2009

   Print

Contents

Introduction

Directory Walker (DbWalker) is a utility that checks for errors and missing links in the Cisco Unity database, and generates output log files that can be used to analyze errors. DbWalker also gives you the option to automatically fix some of the more common errors encountered. For example, DbWalker can make sure that private distribution lists have members associated with them, or that the language selected for a user is installed on the system.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco Unity (all versions).

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Runtime Error: -2147220299 (0x800404b5)

When DbWalker is run, this error might be encountered when the application tries to connect to the database:

Runtime Error: -2147220299 (800404b5)
Method "~" of object "~" failed.

This applies to all versions of Cisco Unity.

Solution

This error is the result of the application not having the appropriate permissions to connect to the database. In order to correct the problem, log out of Windows and log back in as the Cisco Unity Service account. This account has the required permissions and allows you to attach to the database and correctly run the DbWalker utility.

1555: (error) subscriber transfer string=2940

When DbWalker is run, this error message is received:

1555:(error) subscriber transfer string=2940 fails the current
	 restriction table for transfers associated with the 
  COS this subscriber is assigned to. This is not necessarily 
  an error but may be something you want to check into.

Solution

As the message shows, this is not an error and might not cause any problem. This message is related to the restriction tables. Restriction tables are associated with the Class of Service (COS) to which, in turn, users are associated. Restriction tables dictate what strings you are allowed to enter for transfers, notification dialouts and fax deliveries seperately. If you set up a transfer string, then later change the COS a user is associated with, and/or update the restriction table definitions such that the dial string is no longer allowed, Unity still dials it. The restriction tables are only applied at the time the dial string is changed, not when it is dialed. This is necessary for common help desk scenarios where the administrators can change the dial strings. However, the users are not allowed to do this. Cisco Unity uses the restriction table of the user who performs the change in order to check for legality.

1520: (error) subscriber has NULL for their primary call handler reference - this is not a valid subscriber

While using the DbWalker tool (located in Cisco Unity under [Drive]:\Commserver\Utilities or at Cisco Unity Tools), users can identify database corruption and this error:

1520:(error) subscriber has NULL for their primary call
	 handler reference - this is not a valid subscriber.

Solution

Note: Ensure they all are valid subscribers before you proceed with this step.

Remove subscribers from the SQL and then run RemoveSubscriberProperties. This removes the user from Unity. Next, import the user back to Unity.

1233: (error) the extension number for this object conflicts with one or more objects in the directory

When DbWalker is run on a Cisco Unity server, this error message is received:

1233:(error) the extension number for this object conflicts 
with one or more objects in the directory
All objects found to be using extension #xxxxx

This error message is not a critical error. This shows when the Unity server that is not in use is re-installed into the same active directory once, without the old allsubscribers distribution list being deleted.

Solution 1

You can delete the distribution list from the active directory which is not used, or re-assign a directory number to that distribution list in order to resolve this issue. Complete these steps in order to delete the distribution list:

  1. Run this command from the command prompt in the Cisco Unity server:

    osql -E -d UnityDb -Q "SELECT value FROM
    	 UnitySetupParameters WHERE name = '@SystemId'"

    This gives you a number, which is the active Unity server. Make a note of this number.

  2. Navigate to Programs > Microsoft Exchange > Active Directory Users and Computers.

  3. Go down to Users and search for the user allsubscribers.

    This returns two matches.

  4. You might need to delete the account which does NOT match the number from the first step.

    The account which does not match is not being used.

Solution 2

  1. In the Unity SAWeb page, go to Subscriber > Public distribution list.

  2. Check the Distribution list for duplicate extensions. If you find any, change the extension.

  3. Delete the Distribution List from the Active Directory, which is not being used, as given in Solution 1.

1207: (error) Voice name WAV file missing. Path referenced for file=C:\CommServer\Stream Files\...

In Cisco Unity, Call Handler does not work, and DbWalker reports any of the following error messages:

1207:(error) Voice name WAV file missing. Path 
referenced for file=C:\CommServer\Stream Files\...

Or

1226:(error) set to go to a missing call handler with an ObjectID

Or

1237:(error) the owner for this call hander is a missing 
subscriber with an ObjectID

These error messages are not serious ones. The messages display when the database is corrupted.

Solution

In order to resolve this issue, run DbWalker with the Remove orphaned WAV files automatically option checked. This removes the link. If you choose this option, the missing greeting or recorded name of Call Handler points to the system default. You can use the Audio Text Manager in order to create new call handlers. Refer to Audio Text Manager leavingcisco.com for more information and to download the Audio Text Manager tool.

1203: (error) The primary call handler for this subscriber has its AdministratorObjectID value set to point to a different subscriber

After an upgrade to Cisco Unity 4.x, this error message is displayed when the user runs the DbWalker:

1203:(error) The primary call handler for this subscriber has it's 
  AdministratorObjectID value set to point to a different subscriber. You 
  can fix this in DohPropTest by copying the ObjectID of the subscriber into the 
  AVP_ADMINISTRATOR_OBJECT_ID value for the primary call handler.
This can also, however, mean a there is a 'cross linked' call handler 
  problem where a single primary call handler is being 'shared' by more than one 
  subscriber.
COS Alias=defaultsubscriber
Location Object Alias=default
Voice name WAV file path=C:\CommServer\Stream Files\ESubscriber_SubName_0008a0c3.wav
Location object display name={Default}
Subscriber is assigned to language=English (United States)

The error message in the DbWalker is for the Example Administrator. The account is created as a default account when Cisco Unity is first installed. The error message appears when the value of Mailusers > ESubscriber > AVP_OBJECT_ID is different than the value in CallHandlers > Ch_Esubscriber > AVP_ADMINISTRATOR_OBJECT_ID.

Solution

The values under Mailusers > ESubscriber > AVP_OBJECT_ID and CallHandlers > Ch_Esubscriber > AVP_ADMINISTRATOR_OBJECT_ID must be identical.

Complete these steps in order to make these two values identical:

  1. Run DohPropTest.exe in the C:\CommServer\TechTools folder. DohPropTest asks for a password. (This password changes every day).

  2. In the DohPropTest Logon dialog box, leave the Password box empty and click OK.

  3. On the warning dialog box, click Ignore to start the read-only mode of DohPropTest.

  4. Go to Mailusers > ESubscriber > AVP_OBJECT_ID. Copy the property value and paste it into Notepad.

  5. Go to CallHandlers > Ch_Esubscriber > AVP_ADMINISTRATOR_OBJECT_ID. If the Object Information window pops up, click Close.

  6. Copy the property value and paste into the Notepad you have already opened. Compare the value. The two properties value should be same.

  7. If the values are not the same, make the value for CallHandlers > Ch_Esubscriber > AVP_ADMINISTRATOR_OBJECT_ID the same as Mailusers > ESubscriber > AVP_OBJECT_ID by copying the property value of Mailusers > ESubscriber > AVP_OBJECT_ID into CallHandlers > Ch_Esubscriber > AVP_ADMINISTRATOR_OBJECT_ID.

  8. Run DbWalker again to verify.

  9. Also, change CallHandlers > ch_Defaluttemplate > AVP_IS_PRIMARY to 1.

Alternatively, perform these steps:

  1. Create a new Example Administrator account with a different user ID.

  2. Determine the callhandlers associated with the existing EAdministrator account, and re-associate those with the new Example Administrator account.

  3. Delete the existing EAdministrator account through DohPropTest.

  4. Re-run DbWalker.

1694: (error) The '@PrimaryServer' property could not be found in the 'UnitySetupParameters' table

When upgrading to Unity 5.0(1) from an earlier version of Unity, this error message appears while the user runs the DbWalker:

error: 1694:(error) The '@PrimaryServer' property could not be found 
in the 'UnitySetupParameters' table. This can cause problems 
if you try to upgrade this system to a newer version of Unity.  
Please contact TAC.

This error can occur when the PrimaryServer field under the UnitySetupParameters does not point to the correct primary server name.

This issue is documented in Cisco bug ID CSCsj92828 (registered customers only) .

Note: This issue is resolved in Unity 7.0(2) and later, so should not occur during upgrades to those versions.

Solution

Note: Before attempting this workaround, first make sure this SQL query shows a blank value: select Value from UnitySetupParameters where name=N'@PrimaryServer'

In the Cisco Unity Server, go to HKEY_LOCAL_MACHINE\Software\ActiveVoice\Commserver\1.0\PrimaryServer and make sure it is populated with the correct servername.

If not, run this SQL query to insert the Unity server name in UnitySetupParameters using query analyzer:

INSERT INTO UnitySetupParameters
(Name, [Value])
VALUES ('@PrimaryServer', 'servername')

Where 'servername' is the primary server name of the Unity server.

1183:(error) Notification device:Home Phone has a switch ID that is not valid: 2

When running DbWalker in preparation for Unity 4.2.1 to 5.0.1 upgrade, this error message appears:

1183:(error) Notification device:Home Phone has a switch ID 
that is not valid: 2

Or

1199:(error) Subscriber set to switch ID that is not valid:  2

Solution

You can correct this by going to this notification device for this subscriber in the SQL Query Analyzer and selecting a valid switch for it. Perform these steps:

  1. Open SQL Query Analyzer by Start -> Program Files > Microsoft SQL server >Query Analyzer

  2. Select Windows Authentication, then click OK

  3. Select UnityDB

  4. Enter the command select alias, switchid from subscriber, then click Play button.This will give you all the list of Subscribers with switchID 2

  5. Enter the command update NotificationDevice set switchid ='0' where switchid = '2' , then click Play button to update switchID from 2 to 0.

  6. Enter the command update subscriber set switchid ='0' where switchid = '2', then click Play button to update switchID from 2 to 0.

  7. Enter the command select alias, switchid from notificationdevice, then click Play button. Make sure all of the users now show a switchID of 0.

1439:(error) MWI device:MWI-1 has a switch ID that is not valid: 2

When running DbWalker in preparation for Unity 4.2.1 to 5.0.1 upgrade, this error message appears:

1439:(error) MWI device:MWI-1 has a switch ID that is not valid: 2

Solution

Complete these steps in order to resolve this issue:

  1. Open SQL Enterprise manager by going to Start > Programs > Microsoft SQL Server.

  2. Expand Microsoft SQL Servers > SQL Servers Groups > Local or name of primary > Database > UnityDB > Tables.

  3. Right click Subscribers, then select Open Table > Return all rows.

  4. Click the White SQL box at the top of the screen to show you the query box.

    You can see this SQL query:

    select * from subscriber Add where alias = 'alias name of the subscriber'
  5. Click the Red exclamation mark to run the Query. Scroll over till you see the SwitchID column and change the value manually to 0.

  6. Repeat the same steps for all the subscribers that are giving errors on the DBWalker.

1671:(error) the subscriber is not represented in the global subscriber table

When running DbWalker in preparation for Unity 4.1 to 5.1 upgrade, this error message appears:

1671:(error) the subscriber is not represented in the global subscriber table

Solution

This can be fixed automatically by selecting the Add missing local subscriber entries into the global subscriber table option in the automatic fix options.

1575:(error) the DirectoryID for this subscriber is NULL which is invalid

When running DbWalker in preparation for Unity 4.1 to 5.1 upgrade, this error message appears:

1575:(error) the DirectoryID for this subscriber is NULL 
which is invalid. This usually means this object has not 
synchronized with the directory properly. Please contact TAC
for assistance.

Solution 1

Force a reconnection by using the Domain Controller/Global Catalog (DC/GC) Reconnect Settings tool available at Cisco Unity Tools Depot > Administrative Tools. Refer to Changing the Domain Controller and Global Catalog Server for more information on DC/GC Reconnect Settings tool.

Note: This is not service impacting. Therefore, it is safe to run at anytime. When you force a reconnection, you can monitor it on the Application Log on the Event Viewer. From there, you see a message when the process starts and when it finishes.

Solution 2

In order to resolve this issue, run ADSIEDIT and note the directoryid value of the ObjectGUID attribute. Then, update the directotyID column in the SQL table with this new value.

Solution 3

To resolve the issue, remove the Example Administrator account as described in the document Removing the Example Administrator Account in Cisco Unity 3.x.

1652:(error) no installer account found in the subscriber type (subscriber type of 6)

After running DbWalker on Unity 4.0(4), this error message appears:

1652:(error) no installer account found in the subscriber 
type (subscriber type of 6). Please contact TAC for assistance.

Solution

Complete these steps in order to resolve this issue:

  1. Go to Start > Programs > Microsoft SQL Server and open SQL Enterprise manager.

  2. Expand Microsoft SQL Servers > SQL Servers Groups > Local or name of primary > Database > UnityDB > Tables.

  3. Right click Subscribers, then select Open Table > Return all rows.

  4. Look at a row of alias Installer and check the Subscriber Type value. The proper value is 6. If this is not 6, update it to the same and run DbWalker again.

1619:(error) The MailboxStoreObjectID value referenced for this subscriber is not found in the MailboxStore table in the database

After running DbWalker on Unity 7.x, this error message appears:

1619:(error) The MailboxStoreObjectID value referenced for 
this subscriber is not found in the MailboxStore table in the database. 
This is a serious error, you should contact TAC for help.

Solution 1

This error can occur when the MailboxStoreObjectID under the subscriber table is not the same as the one referenced in the Mailboxstore table in SQL. The MailboxStoreObject ID value that is populated for all Subscribers should correspond to the value as seen under the Mailboxstore table.

Go to SQL Unitydb database > Subscriber table and update the MailboxStoreObjectID for the affected user by taking the value of MailboxStoreObjectID from the "mailboxstore" table:

  1. Go to Start > Programs > Microsoft SQL Server > Enterprise Manager.

  2. Expand to Databases > UnityDb and choose Tables.

  3. In the right-pane, look for the MailboxStore table, right-click it, and choose Open Table > Return all rows.

  4. Look for the affected user(s) and note of the MailboxStoreObjectID value.

  5. Close the table and look for the Subscriber table, right-click it, and choose Open Table > Return all rows.

  6. Click the Show/Hide SQL pane button, and issue this command:

    SELECT     *
    FROM         Subscriber
    WHERE alias = 'aliasname'
    
  7. Click Run.

  8. Replace the value for the MailboxStoreObjectID for that user with the one from the MailboxStore table.

Solution 2

The error message essentially means that although the user's call handler and mailuser accounts are present in the Cisco Unity database, the location of the subscriber mailbox is no longer present in Exchange.

This issue is raised because users are no longer part of the company and their Voice Mail boxes are no longer required. As a result, we can safely remove their remaining information from the Cisco Unity database.

Perform these steps in order to resolve this issue:

  1. Launch the Enterprise Manager.

  2. Choose Microsoft SQL Servers > SQL Server Group > Server Name > Databases > UnityDb > Tables.

  3. Choose Subscriber List.

  4. Right-click Subscriber List > Return All Row.

  5. Locate the affected users to be deleted, and highlight the row on the left column. Then, choose Delete.

  6. Re-run the DBwalker tool.

1605:(error) stranded wav file name=D:\CommServer\Stream Files\alice.tjandra_SubName_0064d8a6.wav

This error message appears when running DbWalker on Unity server:

1605:(error) stranded wav file 
name=D:\CommServer\Stream Files\alice.tjandra_SubName_0064d8a6.wav
You can fix this by selecting the 'Removed orphaned 
WAV files automatically' option and re-running dbWalker.

Solution

In order to resolve this issue, re-run the DbWalker with the Remove orphaned Call Handlers Automatically option checked.

1547:(error) The 'servers' table in UniyDB contains an alias value that does not match the local server name as it should.

This error message appears when running DbWalker on Cisco Unity server:

1547:(error) The 'servers' table in UniyDB contains an 
alias value that does not match the local server name as it should. 
This can cause problems in future upgrades to newer Unity
versions and should be addressed before upgrading. Please contact TAC.

Solution

Perform these steps to resolve the issue:

  1. In Cisco Unity, right-click on My Computers, select Properties, and select Computer Name. It will be in the format <Server Name>.<domain>. Note the <ServerName> portion.

  2. Go to Start > Run, type cmd, and click Ok. Enter these commands in the command prompt window:

    OSQL -E
        1> SELECT @@SERVERNAME
        2> go
  3. If the returned value is not the same as that of <ServerName> from step 1, enter these commands:

    1>EXEC sp_dropserver '<old server name>'
        2> go
        1> EXEC sp_addserver '<new servername>', 'local'
        2> go
  4. Go to SQL Enterprise Manager and drill down to SQL Server Group > Local server > Databases > UnityDb > Tables.

  5. Right-click on Servers in the right pane of the Tables window and choose Open Table > Return all Rows.

  6. If the Alias field does not match the Unity Server Name, manually enter the correct server name.

  7. Restart MSSQLServer and SQL Server Agent services, then restart Cisco Unity.

  8. If the issue still exists, go to the /COMMSERVER/ directory and double-click on ConfigMgr.exe. Go to the Advanced Tab and under the option Select the Re-Configuration Operation, select Reset All Default Configuration Settings while preserving all existing objects.

    Note: Do not check any other options as it would erase the database.

1699:(error) The 'SchemaMajorVersion' value is NULL in the row with 'Alias' value matching the primary server name in the 'Servers' table.

One of these error messages appears when running DbWalker on Cisco Unity server:

1699:(error) The 'SchemaMajorVersion' value is NULL 
in the row with 'Alias'value matching the primary 
server name in the 'Servers' table.

OR

1700:(error) The 'SchemaMinorVersion' value is NULL 
in the row with 'Alias' value matching
the primary server name in the 'Servers' table.  
This can cause problems if you try to
upgrade this system to a newer version of Unity. 

OR

1697:(error) No rows with 'Alias' value matching the primary server name were
found in the "servers" tablel  This can cause problems if you try to upgrade 
this system to a newer version of  Unity.

Solution

To resolve this issue, change the SchemaMajorVersion and SchemaMinorVersion from Null. In order to do this, perform these steps:

  1. In the Cisco Unity server, choose Start > Programs > Microsoft SQL Server > Enterprise Manager to open the SQL Server Enterprise Manager.

  2. Choose Microsoft SQL Servers > SQL Server Group > {local server} > Databases > UnityDb> Tables.

  3. Right-click Servers in the right pane of the Tables window and choose Open Table > Return all Rows.

  4. Find the current server, then manually populate the SchemaMajorVersion and SchemaMinorVersion fields to match the version of Unity currently installed.

Note: For Unity 4.0(5) - Major version is 3 and Minor version is 20, and for Unity 7 - Major version is 3 and Minor version is 21.

1527:(error) smtpAddress value for subscriber is NULL.

This error message appears when running DbWalker on Cisco Unity server:

1527:(error) smtpAddress value for subscriber is NULL. 

Solution

To resolve the issue, perform the steps in the document Unable to Receive Voicemail Messages After a New Subscriber Account is Created.

1246:(error) the recipient for this interview handler is set to a subscriber not in the database.

This error message appears when running DbWalker on Cisco Unity server:

1246:(error) the recipient for this interview handler is set to a
subscriber not in the database.
SubscriberObjectID={4C05A06B-2D4C-4F28-9E7E-78B3DF419B3F}

Solution

This error can be corrected by selecting a valid message recipient on the profile page for this interview handler in the SA. In order to do this, perform these steps:

  1. Open the Cisco Unity SA webpage.

  2. Go to Call Management > Interview handler > Profile Page.

  3. Set Deliver Response To to Example Administrator.

0:(error) Date/Time format problem in Configuration table

This error error message appears when running DBWalker after a DiRT restore on Cisco Unity server:

0:(error) Date/Time format problem in Configuration 
table:-2147467259 ([Microsoft][ODBC SQL Server Driver]Invalid time format).  
Check the LastTimeModified column for all entries
in the Configuration table for correct format.

Solution

In order to correct the error, run this query at the command prompt:

osql -E -d UnityDb -Q "update Configuration set LastModifiedTime=NULL"


1438:(error) No MWI devices found for this subscriber

This error message appears when running DbWalker on the Cisco Unity server:

1438:(error) No MWI devices found for this subscriber. If the MWI is
disabled for this subscriber then this is OK, however it's unusual to have a
production subscriber configured with no MWI device.

Solution

The error message indicates that the particular subscriber does not have an MWI extension associated to it. Complete these steps in order to correct the issue:

  1. Open the Cisco Unity SAWeb Page.

  2. Go to Subscriber and find the subscriber.

  3. Click on the Messages tab for the subscriber.

  4. On the right pane, add the MWI device and let the extension be "X" for the primary extension of the subscriber.

1663:(error) the last modified time for a row in the Configuration table is not valid

This error message appears when running DbWalker on the Cisco Unity server:

1663:(error) the last modified time for a row in the
 Configuration table is not valid.

Solution

In order to resolve this issue, open the SQL query analyzer and run this query:

use unitydb
update Configuration set LastModifiedTime=NULL

Related Information

Updated: Dec 03, 2009
Document ID: 28785