06-19-05 07:47 AM
This article mentions a problem similar to yours. I might help.
http://www.kbalertz.com/kb_Q330963.aspx
-tomas
On Fri, 17 Jun 2005 09:41:05 -0700, "SeRGi PeReZ" <SeRGi
PeReZ@discussions.microsoft.com> wrote:
>I have an installation of Commerce Server and SQL Server in two servers and
>different networks, with a Firewall in the middle.
>
>Before installing MSCS I created an Alias with "Client Utility Network"
>configured by TCP/IP and the installation worked correctly. The problem is
>that later the MSCS console did not work, because the connection to the SQL
>Server used by MSCS in "Network Library", used the driver "dbmssocn" and ou
r
>Firewall, only allows connections TCP/IP by port 1433. I modified the
>"Library Network" with the null value and it already connected with SQL
>Server.
>
>During the deploy of the application "PuP" I had the same problem, because
>by defect MSCS uses in "Library Network" the driver "dbmssocn" and when
>relating the resources of application to the corresponding BBDD of Commerce
>and DW, I had to return to modify for each resource so that the "Library
>Network" used the null value in the driver.
>
>The problem that I have now, is that the tool "Commerce Site Packager" make
s
>a last process of connection against a the BBDD and I return to have the sa
me
>error, but in this occasion I cannot modify driver and the MSCS uses in
>"Library Network" the driver "dbnetlib". The error is the following one:
>
>The following error occurred when attempting to connect to the master
>database for DBServer:[DBNETLIB][ConnectionOpen(Connect()).]
>
>How I can solve it? How I can form MSCS so that it always uses by defect
>TCP/IP?
/*-------------------------------
* Tomas Vera
* tomas (at) sbcglobal (dot) net
*-------------------------------
*/
[ Post a follow-up to this message ]
|