Database Admin Tool Issue When Creating Database

[Guest]

When trying to create a new database using the database admin tool for BCM
2007, it comes up with an error saying that it cannot find the list of SQL
server instances. I am trying to do this on MS Small Business Server 2003; MS
SQL Server 2005 is up and running and works without any issues with our other
database. Any reasons why it cannot find it?

 

[Luther]

When trying to create a new database using the database admin tool for BCM
2007, it comes up with an error saying that it cannot find the list of SQL
server instances. I am trying to do this on MS Small Business Server 2003; MS
SQL Server 2005 is up and running and works without any issues with our other
database. Any reasons why it cannot find it?

Can Sql tools, run by the same user, find this Sql instance?

 

[Guest]

Can Sql tools, run by the same user, find this Sql instance?

Well, it is running in the system tray when logged in as that user. When I
go into the server configuration manager then click SQL Server 2005 services,
there is nothing listed though.

 

[Luther]

Well, it is running in the system tray when logged in as that user. When I
go into the server configuration manager then click SQL Server 2005 services,
there is nothing listed though.

The thingy in the system tray could be for another instance or version
of Sql Server. Chances are that your other database is not using the
same instance as BCM, unless it happens to be a MOA or POS database.

The BCM v3/2007 instance is called mssmlbiz. You can double check the
name BCM is using in the Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Business Solutions eCRM
The pertinent key is SQLInstanceName.

You can check the databases on the instance with this command:
sqlcmd -E -S "localhost\mssmlbiz" -Q "select substring(name,1,20),
state_desc from sys.databases"

 

[Guest]

The thingy in the system tray could be for another instance or version
of Sql Server. Chances are that your other database is not using the
same instance as BCM, unless it happens to be a MOA or POS database.

The BCM v3/2007 instance is called mssmlbiz. You can double check the
name BCM is using in the Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Business Solutions eCRM
The pertinent key is SQLInstanceName.

You can check the databases on the instance with this command:
sqlcmd -E -S "localhost\mssmlbiz" -Q "select substring(name,1,20),
state_desc from sys.databases"

That registry key does not exist on the machine.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Business Solutions eCRM is there, but
the SQLInstanceName key is not. Keep in mind, I do not actually have BCM or
outlook installed because this server has exchange server on it. That is why
I am trying to use the databse admin tool instead.
Also the database we have running on our server is called BKUPEXEC. Here is
a command I tried similar to you the one you gave and the results:

C:\Documents and Settings\Administrator>sqlcmd -E -S "localhost\bkupexec" -Q
"select substring(name,1,20), state_desc from sys.databases"
Msg 208, Level 16, State 1, Server FS01\BKUPEXEC, Line 1
Invalid object name 'sys.databases'.

Do I just need to create a new instance?

 

[Luther]

That registry key does not exist on the machine.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Business Solutions eCRM is there, but
the SQLInstanceName key is not. Keep in mind, I do not actually have BCM or
outlook installed because this server has exchange server on it. That is why
I am trying to use the databse admin tool instead.
Also the database we have running on our server is called BKUPEXEC. Here is
a command I tried similar to you the one you gave and the results:

C:\Documents and Settings\Administrator>sqlcmd -E -S "localhost\bkupexec" -Q
"select substring(name,1,20), state_desc from sys.databases"
Msg 208, Level 16, State 1, Server FS01\BKUPEXEC, Line 1
Invalid object name 'sys.databases'.

Do I just need to create a new instance?- Hide quoted text -

- Show quoted text -

The registry keys are important on the client BCM machines that are
trying to reach the database. I don't know if the db admin tool uses
them.

I recall somehting about the value of SQLInstanceName being used when
BCM and the database are on the same machine, and the port number when
the database is on another machine.

One way to find your sql instances on a machine--at least the running
ones--is to look at the machine's services (run services.msc), and
look for services that start with "SQL Server". A typical machine with
BCM installed will have: SQL Server (MSSMLBIZ). You should expect to
find a service named: SQL Server (BKUPEXEC). If you don't find any,
there aren't any sql server instances on that machine (explaining why
the db tool didn't find one), and you should create a sql instance and
then run the tool again. The tool's documentation may have some help
in this area.