OK, just an off the wall, slightly related observation. On an NT Domino server just using normal TSM archive, I hit a Dr. Watson error and was dumped back to a C:\> prompt from my dsmc session. What my problem was.... I was performing an archive, using a management class that didn't have an archive copy group associated with it. Totally my fault from a tsm server admin point of view because I guess way back I just didn't get that copy group defined BUT for "dsmc" to just die with a Dr. Watson error ??????????
now knowing that TDP in general saves things in the form of "archives" (at least TDP/R3 does) I would wonder if maybe something like what I described above is being seen... might be worth while just to query your mgmt classes & archive copy groups to double check everything is as you expect (mine wasn't !) Dwight -----Original Message----- From: Jeff Rogers [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 18, 2001 3:55 PM To: [EMAIL PROTECTED] Subject: TDP Domino crashing I had TDP for Domino running on a schedule, and all was good. Particulars: Client: BA 4.2.1 - TDP Domino 1.1.2.0 - Domino 5.07a, NT4 SP latest. Server: TSM 4.1.4.0 - AIX 4.3.3 Suddenly one day, we started getting a "Dr. Watson" errors on the Domino Server every morning, the offending app is domdsmc.exe, it is the usual "memory can not be read" error. Odd thing is, I can run the script (batch file) manually and it runs to completion. Any ideas?
