recently installed Unity. Upon reboot, MWI lights do not appear and neither does the envelope. It was working prior to reboot. Looking at event logs, I found the following two errors:<br><br>The description for Event ID ( 100 ) in Source ( AvCs_MC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: h:\commsvr\Sources\AvWM\AvWMServerMgr.cpp, 661, 8004045bH, <br>.<br><br>The description for Event ID ( 110 ) in Source ( AvGaen_MC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: [Microsoft][ODBC Microsoft Access 97 Driver] Can't open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt., 0x80004005, 255, h:\commsvr\Sources\GAEN\AvGaenDbSvr\AvGaenDb.cpp, 0x0000008F, 0x0000008F.<br><br>Unity server does not have an H:\ drive, did not install from and H:\ drive and the commserver directory is on c:\<br><br>Cisco sales rep told me this is why MWI is not coming on anymore, these services need to be started. <br><br>How do I change H:\ drive designation to proper C:\ drive spec? Or is there another solution?<br><br>
First, GAEN is set to be disabled by default... it shouldn't start unless you have a particular need to have it on. GAEN (General Audio Error Notification) is a tool to allow you to get email/voice mail notification if something shows up in the event log that indicates a problem or the HD space gets low or the system was rebooted without shutting down properly etc... it's not a necessary service and has absolutely nothing to do with your MWI lamps working or not.
The "H" drive is the drive we compile the source on... you'll also notice the source file referenced in the event log is not on your system anywhere... we don't send raw source out to the public, of course. The path noted in the errors is for developers to use in tracking down the file that threw the error, not a pointer to a file on your installed system.
The errors you not here are not related to your MWI difficulties... I'll post a message from Aaron here is a second going over some troubleshooting tips for CM MWI problems (we've been getting a lot of folks with configuration issues here... it's tricky stuff with CM). Start there.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...