• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3106
  • Last Modified:

Can't connect to a Business Contacts Manager Shared Database


I have previously asked this question and then it got deleted because there was no response.  I am re posting this question (as recommended by a moderator) and the answer that I have figured out so that others may benifit from my $200 call to Microsoft.  

Question:
I am running BCM 2007 on a SQL 2005 Express database install and have the database shared.  This is running in a domain environment.  I am able to connect to the shared database perfectly from any computer running on the local network in our Main office.  We have two branch offices and they are connected via VPN tunnels and are on different subnets.  When I attempt to connect to the shared database from one of the computers in these offices I get an error (see attached photo) :

"Cannot fine computer <computername>.  Confirm that the remote computer exists and that it is available on the network."

From this same computer, I can ping the database computer just fine.  I have tried connecting via ip and computer name but get the same error.

I'm not sure what is blocking BCM from connecting to the shared database.
BCM2007-Connection-Error.png
0
ITPro44
Asked:
ITPro44
  • 3
1 Solution
 
ITPro44Author Commented:
After putting in a call to Microsoft's support I was able to get this working.  
   
 It was windows firewall setting.  
   
 1. Open Control Panel and Windows Firewall  
 2. click on the exceptions tab  
 3. Find "Microsoft small business" and click edit (port should be 5356 TCP)  
 4. Then click Change Scope.  
 5. Then select "Any computer including those on the internet"  
   
 This then allowed traffic from the branch offices that were on a different  
 subnet to access this port and the database.  
   
 Here is another article that they referred me to that may help this or other  
 connection problems you may be having.  
   
 http://support.microsoft.com/kb/901164  
  ------------------------------------------------------------------------------------------------  
 Here is some information the support agent email me that also may help.  
   
 "Verify the connection to the SQL database  
 To verify that the Business Contact Manager client can establish a  
 connection to a shared Business Contact Manager database, follow these steps:  
 1.       Log on the Business Contact Manager client computer as a Windows user  
 who is granted access to the database on the Business Contact Manager server.  
 2.       Click Start , click Run , type cmd , and then click OK .  
 3.       At the command prompt, type the following command and then press ENTER:  
 C:\>sqlcmd E -S Server_Name \mssmlbiz,5356  
   
 Note sqlcmd switches are case-sensitive. Server_Name is the name of the  
 Business Contact Manager server.  
 When you run this command, the Business Contact Manager Client tries to  
 connect directly to the remote SQL instance. If the client can establish a  
 connection to the remote instance of Business Contact Manager, an OSQL  
 command prompt appears. An OSQL command prompt is indicated by "1>".  
   
 The appearance of an OSQL command prompt indicates the following:  
 "      The client computer can communicate with the Business Contact Manager  
 database.  
 "      The Business Contact Manager database is successfully configured for  
 sharing.  
 "      The user who performs the test from the Business Contact Manager client is  
 successfully granted permissions to access the database.  
 A successful connection to a remote instance of Business Contact Manager  
 will appear as follows:  
 C:\> sqlcmd E -S Server_Name\mssmlbiz,5356 1>  
   
 If the Business Contact Manager client cannot establish a connection to the  
 remote instance of Business Contact Manager, you may receive an error message  
 that resembles the following in Business Contact Manager when you try to  
 connect to the server:  
   
 Cannot access the database server on computer Computer_Name  
   
   
 This error message may indicate the following possible problems:  
 "      The destination server is unavailable or the Business Contact Manager  
 instance is not running.  
 "      The Microsoft Firewall or a third-party firewall is blocking access to the  
 SQL server.  
 "      The database has not been shared for the user who is trying to access the  
 server. This issue may occur if the Business Contact Manager client and  
 server are in different workgroups or domains. For more information, see the  
 section "Business Contact Manager database sharing configurations"  
0
 
ITPro44Author Commented:
After putting in a call to Microsoft's support I was able to get this working.  
   
 It was windows firewall setting.  
   
 1. Open Control Panel and Windows Firewall  
 2. click on the exceptions tab  
 3. Find "Microsoft small business" and click edit (port should be 5356 TCP)  
 4. Then click Change Scope.  
 5. Then select "Any computer including those on the internet"  
   
 This then allowed traffic from the branch offices that were on a different  
 subnet to access this port and the database.  
   
 Here is another article that they referred me to that may help this or other  
 connection problems you may be having.  
   
 http://support.microsoft.com/kb/901164  
  ------------------------------------------------------------------------------------------------  
 Here is some information the support agent email me that also may help.  
   
 "Verify the connection to the SQL database  
 To verify that the Business Contact Manager client can establish a  
 connection to a shared Business Contact Manager database, follow these steps:  
 1.       Log on the Business Contact Manager client computer as a Windows user  
 who is granted access to the database on the Business Contact Manager server.  
 2.       Click Start , click Run , type cmd , and then click OK .  
 3.       At the command prompt, type the following command and then press ENTER:  
 C:\>sqlcmd E -S Server_Name \mssmlbiz,5356  
   
 Note sqlcmd switches are case-sensitive. Server_Name is the name of the  
 Business Contact Manager server.  
 When you run this command, the Business Contact Manager Client tries to  
 connect directly to the remote SQL instance. If the client can establish a  
 connection to the remote instance of Business Contact Manager, an OSQL  
 command prompt appears. An OSQL command prompt is indicated by "1>".  
   
 The appearance of an OSQL command prompt indicates the following:  
 "      The client computer can communicate with the Business Contact Manager  
 database.  
 "      The Business Contact Manager database is successfully configured for  
 sharing.  
 "      The user who performs the test from the Business Contact Manager client is  
 successfully granted permissions to access the database.  
 A successful connection to a remote instance of Business Contact Manager  
 will appear as follows:  
 C:\> sqlcmd E -S Server_Name\mssmlbiz,5356 1>  
   
 If the Business Contact Manager client cannot establish a connection to the  
 remote instance of Business Contact Manager, you may receive an error message  
 that resembles the following in Business Contact Manager when you try to  
 connect to the server:  
   
 Cannot access the database server on computer Computer_Name  
   
   
 This error message may indicate the following possible problems:  
 "      The destination server is unavailable or the Business Contact Manager  
 instance is not running.  
 "      The Microsoft Firewall or a third-party firewall is blocking access to the  
 SQL server.  
 "      The database has not been shared for the user who is trying to access the  
 server. This issue may occur if the Business Contact Manager client and  
 server are in different workgroups or domains. For more information, see the  
 section "Business Contact Manager database sharing configurations"  
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now