I've noticed lately that ADSM 3.1.0.6 Client for Win NT frequently gives a
Dr.Watson in DSMCSVC.EXE if the dsm.opt file is configured incorrectly. i.e.
at an adsm server where it is not defined as a node. Has anyone else seen
this behaviour?

Regards,

Nathan



Nathan King
Storage & Automation Management
*  (210) 913-5755
* Pager: 753-5755
* E-mail: nathan.king AT usaa DOT com

The opinions herein are solely author's  and are not necessarily the opinion
of USAA.
***********************************************************
This email transmission and any files that accompany it may
contain sensitive information belonging to the sender. The
information is intended only for the use of the individual
or entity named. If you are not the intended recipient, you
are hereby notified that any disclosure, copying,
distribution, or the taking of any action in reliance on the
contents of this information is strictly prohibited. If you
have received this email transmission in error, please
immediately notify the Security Administrator.
Security.Administrator AT dowcorning DOT com
***********************************************************