I am running into the typical Security Service startup issue with the
SQL Server installed on the same system as the CRM Server.

I have attempted doing the crmsecurityservice -u which does properly unregister the service.
Re-registering the service with a crmsecurityservice -r -s does re-register the service.

However, it does not add the SQL service dependency on the named sql service instance.
There is no unnamed SQL Service instance on the system.

I did not see an option in the command line for specifying a name for the sql service;
how do I properly setup the dependency? (Or even improperly setup the dependency?)

CRM supports only the default instance

"Aaron J. Millis" <millisa@fnord.io.com> wrote in message
news:yJSdnftg8YYRLobcRVn-rg@io.com...

Peter Lynch <anon@anon.com> wrote:
Er, CRM runs on named instances just fine . . . Manually starting the security service (or starting it with a machine
startup task) works around the issue.

The issue isn't getting it to run, its just getting it to properly acknowledge it's dependency during automatic startup.

Peter said it wasn't supported, not that it won't run. There is a difference.

CRM may run, but you will run into problems with the replication and the SFO
client as the replication does not get setup properly in a named instance.

As for the dependency, you can always add it yourself manually.

Matt Parks
MVP - Microsoft CRM

----------------------------------------
----------------------------------------
On Thu, 12 Aug 2004 14:30:53 -0500, "Aaron J. Millis" <millisa@fnord.io.com>
wrote:

Peter Lynch <anon@anon.com> wrote:
Er, CRM runs on named instances just fine . . . Manually starting the security
service (or starting it with a machine
startup task) works around the issue.

The issue isn't getting it to run, its just getting it to properly acknowledge
it's dependency during automatic startup.