--- title: "ERROR: \"Database Connection Error\" when installing Blueprint Administrator on a remote system" slug: "error-database-connection-error-when-installing-blueprint-administrator-on-a-remote-system" tags: ["database", "Blueprint", "error"] updated: 2024-04-23T19:20:43Z published: 2024-04-23T19:20:43Z canonical: "kb.pharos.com/error-database-connection-error-when-installing-blueprint-administrator-on-a-remote-system" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.pharos.com/llms.txt > Use this file to discover all available pages before exploring further. # ERROR: "Database Connection Error" when installing Blueprint Administrator on a remote system ### Symptoms: - ERROR: "Database Connection Error" - Installing Blueprint Administrator on remote machine results in error ### Environment: - Pharos Systems Blueprint Enterprise - Microsoft SQL Server --- ### Cause: Installing Blueprint Administrator on remote systems create connections to the database (using the credentials gleaned from the Analyst) so that it can do its work. If the Microsoft SQL Server is using non-standard ports and/or SQL Browser is not running, it can fail to make the SQL connection, and so fail to run, even though the initial connection to the Blueprint Analyst server succeeds. ### Resolution: Append the correct TCP port to the server name within the client computer's GlobalConfig.xml file, created during Administrator installation. 1. Open the GlobalConfig.xml file (by default, found in C:\ProgramFiles\PharosSystems\Blueprint) in NotePad. You may need to execute NotePad as an administrator. 2. Find the XML tag. The value within the tag is the name/instance of the SQL Server. 3. Append the TCP port to the server name by placing the port number (for example, 15000) at the end of the server's name with a comma (,) separating the two. This forces the .NET client that we use for the SQL connection to utilize that port number. SQLServerName,15000 **NOTE:** Blueprint Enterprise 5.0 and 5.1 will have two tags; one for the Operational database, and another for the Warehouse database. Ensure that it is modified in both places. They are highlighted in the graphic below. ## Related - [Network Unavailable. The connection was refused remotely. Contact an Administrator" message when configuring Pharos iMFP or Omega Terminals for the Pharos EDI Server](/network-unavailable-the-connection-was-refused-remotely-contact-an-administrator-message-when-configuring-pharos-imfp-or-omega-terminals-for-the-pharos-edi-server.md) - [Pharos Web Remote only displays 100 transactions](/pharos-web-remote-only-displays-100-transactions.md) - [Using WSUS Service and the Pharos Web Pages (Nerve Center, Uniprint, Pharos Remote)](/using-wsus-service-and-the-pharos-web-pages-nerve-center-uniprint-pharos-remote.md) - [Can I run the WCF on another port?](/can-i-run-the-wcf-on-another-port.md)