Hello,

I have CRM 1.2 installed on my SQL Server. I schedule it to reboot
automatically once per week using scheduled tasks, just to make sure the
automatic updates keep getting applied. The CRM security service refuses to
start automatically - generates the:

"The service did not respond to the start or control request in a timely
fashion."

I've created the dependancy on the SQL Service, but it still does this.
Everything else on the server starts fine and when I manually start the
service... no problem.

I know this is service is notorious for this problem. Surely someone out
there has a solution.

--
thanks,
-Jeff

For me solution was to choose Administrator for account that service uses.
However this seem to work only when you choose it in new install of CRM.

So I would reinstall CRM and then choose Administrator account instead of
default System, when installation wizard asks about which account to use all
services.

Jani Ervast

"Jefffff" <Jefffff@discussions.microsoft.com> wrote in message
news:5BC743EC-F794-4816-B498-BF04064A3557@microsoft.com...

Thanks for your reply Jani. That's interesting that changing the account
solved the problem. However, I'd rather not create an account for this
service or use the administrator account.

Yesterday, as a work around, I decided to set up a scheduled task to start
the service for me 20 minutes after the scheduled reboot. That seems to have
done, because the server rebooted last nigth and all was well this morning,
but I'd still like to get to the bottom of the issue.

Thanks again for your post.

--
thanks,
-Jeff


"Jani Ervast" wrote:

There is a known issue caused by the MSCRM Security Service not having its
sql server dependancy correctly set. On the CRM Server enter this in a
command prompt...
cd Program Files\Microsoft CRM\server\bin\CrmSecurityService –r –s
More details can be found in partnersource article 827622

Regards,
Chris.

"Jefffff" wrote:

Thanks for your reply Chris. I have seen that article and I have created the
dependancy, however I still have the problem.

Maybe I'll just have to live with it until we upgrade to CRM 3.0 (hopefully
that will solve it).

Thanks again for your post.
--
thanks,
-Jeff


"CFEBC" wrote: