08-28-2002 08:13 PM - edited 03-12-2019 08:33 PM
I am installing a 3.x system that is experiencing an exceptionally high rate of these log files. What causes them and how do I possible remedy the situation?
08-28-2002 08:36 PM
How big are those files? How often are new ones generated? How many are there total? You should be cautious about the system resources. Opening and closing tons and tons of these log files has been known to cause odd little problems here and there.
What is the exact version of Unity you're running? Take a look at this link for information on how to control some aspects of the log files.
http://www.cisco.com/warp/public/788/AVVID/unity_trace_maestrotools.html#registrysetting
adam
08-28-2002 08:47 PM
This is actually a known problem with the UMR is having trouble delivering messages to the Exchange server you selected during configuration setup... it's bug # CSCdx93837
Here's the release note for it:
Symptom:
The directory where Unity diagnostic logs are kept, by default this is
\commserver\logs, is growing to over a thousand logs in a short matter of time
(less then an hour). The majority of these log's names start with
diag_AvUMRSyncSvr.
Condition:
Unity 3.0 or higher in a situation where the UMR is failing to deliver voice
messages on to Exchange.
Workaround:
The only real workaround is to stop the AvUMRSyncSvr service, or to fix the
problem with the UMR being unable to deliver voice messages on to Exchange.
The logs that start with diag_AvUMRSyncSvr may be deleted periodically to
allow the logs folder to be managable. Follow the below steps.
1. Go to Start->Run...
2. Enter 'cmd' and then click OK.
3. In the command window browse the logs directory. For example if your
logs were in the default directory on the C: drive you would type
'cd c:\commserver\logs'.
4. Type 'del diag_avumrsyncsvr*.*'
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide