ADSM-L

Wassup with Expiration at 3.1.2.50??

2000-05-16 10:12:30
Subject: Wassup with Expiration at 3.1.2.50??
From: Alan Cheski <Alan_Cheski AT GULF DOT CA>
Date: Tue, 16 May 2000 08:12:30 -0600
I upgraded our NT ADSM Server from 3.1.2.0 to 3.1.2.50 so that we could get
Netware long filename support. Now, when expiration runs, I see the process
dmcsvc.exe taking 100% of the cpu and chewing up over 300M of memory. This
degrades the performance of the server and the expiration runs for 12 hours. It
says it was successful and examined only 600,000 objects. Has anyone else had
this problem and found a solution?

Alan Cheski
Gulf Canada Resources
<Prev in Thread] Current Thread [Next in Thread>
  • Wassup with Expiration at 3.1.2.50??, Alan Cheski <=