how can i get bcm running on sql server?

[James]

how can i get bcm running on sql server? i attached the two database files
to sql server and changed the port in the server and client properties, but
when i try to connect with bcm it says:

"No business Contact Manager for Outlook databases could be found on
computer MyServersName. Confirm that a shared database exists, that you
have been given access to the database, and that both computers are using
the same version of Business Contact manager for outlook".

i used svrnetcn.exe and added named pipes and changed the tcp/ip port to
56183. and i also used cliconfg.exe to change the port to 56183.

what did i do wrong?

 

[James]

nm, i just had to share it before i attached it.

 

[guzzi]

i have a shared DB copied to SQL Server, but still can't connect
Tha same error

Please could you please describe you steps?

TIA

 

[James]

i just ran both the client and sever sql utils on the server ( svrnetcn.exe,
cliconfg.exe and changed the port to 56183) i also added named pipes
protocal. i also changed the port on the client computer using these utils.
make sure your xp firewall isn't on. i also added my client computers domain
user to the sql servers user and gave him access to the newly attached db. i
think thats all i did. lemme know how it goes..

 

[James]

also, did you copy the right db? it should be in your C:\Documents and
Settings\YourUser\Local Settings\Application Data\Microsoft\Business Contact
Manager\

 

[test]

Here is how to run BCM from a sql server:

[the already known part]
1. share database in Outlook BCM
2. stop local MSDE sqlserver.exe
3. copy MDF file to SQL server and attach db
(file location: C:\Documents and Settings\YourUser\Local
Settings\Application Data\Microsoft\Business Contact Manager\)
4. add client computers domain user to sql servers user and give access
to the newly attached db

[the new part]
5. Configure outlook BCM to connect to SQL Server:
edit registry settings to match your sqlserver configuration:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Business Solutions eCRM\SQLInstanceName
= enter Name of Instance of your SQL Server (default: empty)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Business Solutions eCRM\SQLPort
= enter 1433 for normal operation

6. Start Outlook and configure Database by entering the server name. In
the drop-down-list the BCM database should appear.

7. Cleanup:
If you want to stop MSDE from running and consuming resources on your
local computer, disable the MSSQL$MICROSOFTSMLBIZ service and remove
the SQL Server Service Manager from the Autostart Folder.

Note: there is no need to change cliconfg.exe or svrnetcn.exe settings.
These are just used by the MSDE engine - and since we don't use it any
more, changes here are not necessary.

Hope this helps,
Ralf.

 

[guzzi]

ok... figured out with that SQLInstanceName, reinstalled server using
Instance Name - BCM, not a 'default' name.
So.. edited registry, placing PORT: 1433 and SQLInstanceName: BCM

So.. next problem accured: started outlook and there is NO! BCM loaded.
Enable BCM (from start menu) doesn't help.

SQL 2000 SP4 server
Outlook 2003 (11.6359.6360) SP1

Please help
TIA

 

[guzzi]

forgot to say
when there is anything else that BCM in SQLInstanceName field (in
registry) it goes well... but can't connect to my new sql server

 

[test]

forgot to say
when there is anything else that BCM in SQLInstanceName field (in
registry) it goes well... but can't connect to my new sql server

Maybe an example for more clarity:
the SQL server instance name is not the database name. When installing
SQLServer, you can optionally specify an instance name. In my setup, my
SQLServer is on a PC named SERVER1 and the instance name is SQL2000. So

SQLInstanceName=SQL2000

If you can connect to your SQL server via ODBC, it should work with BCM too.

Ralf.

 

[guzzi]

all done...

my steps are:

1. install outlook on one of your non-stop running server
2. install BCM2 with MSDE (coz BCM wants it to run smoothly)
3. create a DB and share it with users
4. cloce outlook and stop that MSDE
5. run SQL Server 2000 installation and chose to upgrade an existing
instance (MSDE goes SQL Server 2000)
6. apply SQL Server 200 SP4
7. now any client should be able to open shared DB on the server

Hope this will help