Unsolved
This post is more than 5 years old
3 Posts
0
92205
November 27th, 2009 01:00
DSM SA Data Manager Service Slow to Start
Rebuild of PE2950 with W2K3 SP2, SQL2K5, .Net 2.0 & 3.5. After reboot the DSM SA Data Manager Service takes about 10 minutes to start, during this time cannot login either remote or at the console. I cannot find any port conflicts, and once the service has started, everything is ok.
Server is running the latest BIOS, Firmware etc, and Dell Open Manage Ver 6.1
Any ideas anybody, or anyone seen this before ?
No Events found!
tlebel
1 Message
0
December 6th, 2009 11:00
Same problem on PE860, no SQL .If I disable the services, it boots fine.
onegoodsoul
8 Posts
0
December 9th, 2009 05:00
Same issue on a PE2950 with latest BIOS, firmware, etc. - using Openmange 6.1.
Futre
3 Posts
0
December 10th, 2009 05:00
Glad to see I am not the only person with this problem.
Dell have provided this workaround, I have tried it, and it works.
Regardding the Datamanager taking too long to boot, we have found this issue when we install OMSA on a Server that has “SQL Server Integration Services”. Reason for the delay is the race condition which prevents command reaching the storlib. There is a race condition between the SQL integration service and DSM data manager service.
To avoid this a dependency can be created as per the below Microsoft knowledgebase. This will prevent from this condition.
http://support.microsoft.com/kb/193888
There is no eta of a genuine fix, so we'll have to make do with the workaround for now I guess.
Futre
3 Posts
0
December 10th, 2009 06:00
No this was all they provided. Let us know how you get on ?
onegoodsoul
8 Posts
0
December 10th, 2009 06:00
Thanks for the information. Did Dell support supply you with a step by step or did they only direct you to this KB? If they provided a step by step, would you mind posting it here? I could really use it.
Thanks.
react2k
1 Message
0
February 25th, 2010 18:00
Hi,
I encountered this same issue with DSM SA Data Manager from Dell OpenManage 6.2 taking ~10 minutes to start up, getting in the way of all sorts of other services including firewall and remote desktop.
I'm not running SQL Server but it appears a similar race condition was triggered with another 3rd-party service, in this case a "watch folder" style process. Making that service dependent on DSM SA Data Manager with the instructions above was a sufficient workaround to get things back on track.