Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unity Broken after Windows 2003 Service pack 1 install

Status
Not open for further replies.
Jul 21, 2003
64
US
I installed Service Pack 1 for Windows 2003 on our exchange server and it broke Unity’s ability to speak to Exchange, the error on the Unity server is this:

The Partner Exchange Server EXCH1 is offline during ExchangeMonitor Startup. All message notification processing is disabled until this has been resolved. When the Exchange Monitor detects that this server is back online, registration for notifications will proceed.

Also, Voicemail lamps on the phones do not switch on.
Unity can ping the exchange server fine, and the exchange server has no logs of failed logins or anything like that. What can I do to fix this so Unity can talk to Exchange on a Windows Server 2003 SP1 box?

Btw, Uninstalling Service Pack 1 fixes the problem.

Thank you in advance,

-Mesa


-Mesa
 
Last I checked, Unity isn't approved for Windows 2003.


It is what it is!!
__________________________________
A+, Net+, I-Net+, Certified Web Master, MCP, MCSA, MCSE, CCNA, CCDA, and few others (I got bored one day)
 
The post mentions upgrading the Exchange server, not the Unity server. If you install SP1 on the exchange server that Unity is partnered with then it breaks! In some cases SP1 cannot be uninstalled which leaves you really messed up.
 
Yes the update is actually service pack 1 for windows, not exchange. Right now Exchange is already on SP1.

To many Service packs out there :)

Right now I am looking at the RPC and DCOM security settings that have could have broke it. I noticed in Service pack 1 for server 2003 there are a couple new items.

-Mesa
 
Cisco Systems recommends that if you have a setup like you have to not install service packs or hotfixes to your servers without getting that service pack or hotfix from CCO. Cisco TAC will insist that if you don't get your service packs or hotfixes from CCO then you'll run into the very same issues that your having. I'd suggest that if you want SP1 on your WIN2K3 box that you check on CCO for that service pack.

"I can picture a world without war. A world without hate. A world without fear. And I can picture us attacking that world, because they'd never expect it."
- Jack Handey, Deep Thoughts
 
Can someone give me a link to CCO?
and can someone tell me what it stands for?

Thanks!


-Mesa
 
CCO = Cisco Connection On-line


"I can picture a world without war. A world without hate. A world without fear. And I can picture us attacking that world, because they'd never expect it."
- Jack Handey, Deep Thoughts
 
IPKONFIG: You're missing the point here... we all know that we have to install Cisco approved service packs and hotfixes on our "Cisco" servers... ie CallManager and Unity. With this particular problem if you install Windows 2003 SP1 on a non Cisco server, ie your MS Exchange server that Unity just happens to connect to for UM then it breaks. You cannot install the Cisco patches on these servers because they do not have the Cisco flavored version of Windows on them.
 
Well Cisco released a field notice about Unity and exchange running
On Windows Server 2003 service pack 1. To fix the problem of unity not being able
To talk to exchange you need to:

“Place the UnityMsgStoreSvc account, the account the
AvMsgStoreMonitor service logs on as, in the local Administrators group
on the Windows 2003 SP1/Exchange 2003 server. Once this is complete,
the Unity server (Windows) must be rebooted.” –Cisco Systems.

I did this last night and verified that it works. Yay now all my 2003 systems are SP1 w00h000!!!

Thanks for everyone’s help, I hope this helps others.

-Mesa


-Mesa
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top