Hi, I have recently upgraded from UNITY 3.1.1 to 3.1.4 due to problems with ports locking up. The upgrade was smooth and cured the port lock up issue. However after one week of perfect operation it now seems that when a call is put through to unity, the system goes through the motions of taking a message and all seems well - but the message is never delivered to the recipients mailbox ! This seems to be the case system wide. Old messages can be deleted but new ones cannot be sent. Exchange is off-box and is Exchange 2000. Below is dump from System Info tool - cheers
Unity server name = 2KS-UNITY
Companion Exchange Server = 2KS-INFO1
Companion Exchange Server Type = Exchange 2000
Unity domain = HC_ADM
Unity verstion = 3.1(4.0)
Cisco Unity TSP version = 126.96.36.199
Exchange version = Exchange 2000 build: 0
SQL Version = Microsoft SQL Server 2000 - 8.00.474
The most likely scenario is that the Unity UMR component is having trouble connecting to your off box Exchange to deliver outside caller messages. In this case you'll see errors in the application event log along these lines and you'll also see a bunch of files in the \commserver\unityMTA directory.
there could be any number of reasons why the connection to Exchange has gone haywire (DNS issues, profile got fouled up, Unity messaging system missing, rights issue on the messages facing service accounts etc...). The place to start is the application event log.
It could also be related to full mailboxes but that's highly unlikely since this is happening for everyone... regardless, these messages would be bounced NDR back to the UnaddressedMessages public distribution list - hopefully you've added a real admin type person to that DL but if not the default member is the Example Administrator account - you can check that inbox for messages.
As a side note - can subscribers leave messages for each other directly (i.e. sub to sub vs. unidentifed callers leaving messages)? If not there may be larger network issues at play - if so that supports the theory of the UMR connection issue since the UMR is only used to deliver unidentified caller messages via the Unity Messaging System account on the companion exchange server.
my guess would be an Exchante MTA type issue then... if no one's messages are getting anywhere that's where I'd look. Take a peek in the event logs on your Exchange servers and see if you find RPC or bindback errors in there - could be a DNS issue tripping the whole system up since the MTA uses remote procedure calls that require DNS to be flying right to get it's job done.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.