Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Client\s+5\.3\.0\.8\s+strange\s+behaviour\s*$/: 5 ]

Total 5 documents matching your query.

1. Client 5.3.0.8 strange behaviour (score: 1)
Author: Richard van Denzel <RvanDenzel AT SLTN DOT NL>
Date: Thu, 9 Jun 2005 14:46:57 +0200
Hi All, Has anyone seen this behaviour and perhaps knows a cure? Environment: Windows 2003 Small Business Server TSM Client 5.3.0.8 have to give the service a restart. Other Windows 2003 Servers (not
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00166.html (11,047 bytes)

2. Re: Client 5.3.0.8 strange behaviour (score: 1)
Author: Curtis Stewart <Curtis.Stewart AT LAWSON DOT COM>
Date: Thu, 9 Jun 2005 08:03:51 -0500
Are you using dsmcad or dsmc to control the scheduling. I've seen lots of problems with hung schedulers on Windows, at many code levels, when using dsmc sched. Moving to "managedservice schedule" see
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00167.html (11,829 bytes)

3. Re: Client 5.3.0.8 strange behaviour (score: 1)
Author: Richard Sims <rbs AT BU DOT EDU>
Date: Thu, 9 Jun 2005 09:53:33 -0400
Are you using dsmcad or dsmc to control the scheduling. I've seen lots of problems with hung schedulers on Windows, at many code levels, when using dsmc sched. Moving to "managedservice schedule" se
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00169.html (11,240 bytes)

4. Re: Client 5.3.0.8 strange behaviour (score: 1)
Author: Richard van Denzel <RvanDenzel AT SLTN DOT NL>
Date: Thu, 9 Jun 2005 16:12:30 +0200
Curtis, On all servers we use a service (a.k.a. dsmc sched). Richard, The technote comes very close, but on this machine backups all went ok, but when I look in the dsmsched.log the service hangs bet
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00170.html (11,874 bytes)

5. Re: Client 5.3.0.8 strange behaviour (score: 1)
Author: Richard Sims <rbs AT BU DOT EDU>
Date: Thu, 9 Jun 2005 10:28:41 -0400
The technote comes very close, but on this machine backups all went ok, but when I look in the dsmsched.log the service hangs between communication with the server when the next schedule is due (we
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00176.html (11,822 bytes)


This search system is powered by Namazu