DBwalker has Invalid Switch ID errors

Unanswered Question
Nov 17th, 2008

Hi

We get " switch ID is invalid " errors for about 1000 of these errors for almost all the subscribers in Unity on both the primary and failover servers. What could be causing this issue and how do I fix this ?

Running dbWalker version:4.0.56

Search for '(error)' or '(warning)' to find logged errors and warnings.

Starting walk at:11/15/2008 2:57:07 PM

Local Unity Version=5.0(1.0)

Local server name= MNSVWUNYP002

Backend is Exchange 2000 or 2003

1699:(error) The 'SchemaMajorVersion' 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. Please contact TAC.

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. Please contact TAC.

Checking LastModifiedTime column for all entries in the Configuration table

*** Starting subscriber walk ***

Alias=ajackson

Display Name=Jackson, Angela

Jump to this subscriber in the SA using this link: Open SA to this subscriber

COS Alias=defaultsubscriber

Location Object Alias=default

Subscriber has no voice name recorded

Location object display name=Default

Subscriber is assigned to language=English (United States)

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

This can be fixed by going to the subscriber profile page in the SA and selecting a valid switch for this user.

Subscriber has no private lists

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

1183:(error) Notification device:Pager has a switch ID that is not valid: 0

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this notification device for this subscriber in the SA and selecting a valid switch for it

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

You can correct this by going to this messages page for this subscriber in the SA and selecting a valid switch for it

Thank you

Ranj

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Bradford Magnani Mon, 11/17/2008 - 06:15

Ranj,

You're getting these switch ID mismatches because the current integration ID configured in the Integrations Manager differs from what's currently in the database. These need to match.

If you go to Start > Programs > Unity > Manage Integrations and highlight Properties of the switch you're concerned with, you'll see the Integration ID there. You can then go to the Tools>Subscriber-Phone System Associations option and then re-assign the subscribers to the proper phone system, or to another.

Hope this helps,

Brad

lordshawn Thu, 11/20/2008 - 07:52

IT was probably caused by something deleting the itnergration and/or making changes...which changes the switch ID incrementaly. Or someone could of BUlk Edited the Switch id...

Actions

This Discussion