<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems</link><pubDate>Mon, 30 Mar 2020 01:28:31 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Jesse Dringoli</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Current Revision posted to OpenUtilities Wiki by Jesse Dringoli on 3/30/2020 1:28:31 AM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.140&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;Promis.e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and web sites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of Promis.e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Requirements for a successful connection:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in Promis.e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to Promis.e and Bentley Substation&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and Promis.e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]] dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server...&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;The SQL Server version must be compatible with the Bentley software that is trying to connect. Refer to the compatibility chart for the software:&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The SqlServerProject.sql script from pre-SELECTseries 4 era software also created the above login.The SqlServerProject.sql script included with recent releases no longer creates this login.&lt;/p&gt;
&lt;p&gt;If the SQL Server was originally installed via a promis.e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right-click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case, only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case, the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the Promis.e or Bentley Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;In single-user environments, the SQL Server hosting the project database is often installed on the user&amp;#39;s workstation. Since the SQL Server service is set to start Automatically by default, rebooting the workstation often resolves the problem of a stopped service.&lt;/p&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right-click it and select &lt;strong&gt;Start&lt;/strong&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start &lt;strong&gt;Automatically&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right-click the &lt;strong&gt;Protocols for&lt;/strong&gt; the instance name, and select &lt;strong&gt;Properties&lt;/strong&gt;.&amp;nbsp; Enable the &lt;strong&gt;TCP/IP&lt;/strong&gt; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a required structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of Promis.e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the &lt;strong&gt;Object Explorer&lt;/strong&gt; to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For SQL Server 2014 the files are often located in a path similar to&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2005, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right-click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" height="500" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right-click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2014&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2014?&lt;br /&gt;&lt;a href="https://technet.microsoft.com/en-us/library/ms191464(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://technet.microsoft.com/en-us/library/ms191464(v=sql.120).aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="https://msdn.microsoft.com/en-us/library/cc646023(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/cc646023(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="https://technet.microsoft.com/en-us/library/ms177440(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://technet.microsoft.com/en-us/library/ms177440(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="https://msdn.microsoft.com/en-us/library/ms181087(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/ms181087(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005 (not compatible with recent versions of Promis.e and Bentley Substation)&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backward compatible, meaning SSMS 2014 can manage SQL Server 2008, but SSMS 2008 cannot connect to SQL Server 2014.&lt;/p&gt;
&lt;p&gt;SSMS is not included with Promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Promis.e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/p&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, Administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, en, SELECTsupport, Problem Solving&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/35</link><pubDate>Tue, 14 Nov 2017 23:34:06 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 35 posted to OpenUtilities Wiki by Matt_P on 11/14/2017 11:34:06 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.140&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;Promis.e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and web sites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of Promis.e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Requirements for a successful connection:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in Promis.e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to Promis.e and Bentley Substation&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and Promis.e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]] dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server...&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;The SQL Server version must be compatible with the Bentley software that is trying to connect. Refer to the compatibility chart for the software:&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The SqlServerProject.sql script from pre-SELECTseries 4 era software also created the above login.The SqlServerProject.sql script included with recent releases no longer creates this login.&lt;/p&gt;
&lt;p&gt;If the SQL Server was originally installed via a promis.e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right-click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case, only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case, the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the Promis.e or Bentley Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;In single-user environments, the SQL Server hosting the project database is often installed on the user&amp;#39;s workstation. Since the SQL Server service is set to start Automatically by default, rebooting the workstation often resolves the problem of a stopped service.&lt;/p&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right-click it and select &lt;strong&gt;Start&lt;/strong&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start &lt;strong&gt;Automatically&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right-click the &lt;strong&gt;Protocols for&lt;/strong&gt; the instance name, and select &lt;strong&gt;Properties&lt;/strong&gt;.&amp;nbsp; Enable the &lt;strong&gt;TCP/IP&lt;/strong&gt; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a required structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of Promis.e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the &lt;strong&gt;Object Explorer&lt;/strong&gt; to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For SQL Server 2014 the files are often located in a path similar to&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2005, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right-click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" height="500" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right-click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2014&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2014?&lt;br /&gt;&lt;a href="https://technet.microsoft.com/en-us/library/ms191464(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://technet.microsoft.com/en-us/library/ms191464(v=sql.120).aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="https://msdn.microsoft.com/en-us/library/cc646023(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/cc646023(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="https://technet.microsoft.com/en-us/library/ms177440(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://technet.microsoft.com/en-us/library/ms177440(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="https://msdn.microsoft.com/en-us/library/ms181087(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/ms181087(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005 (not compatible with recent versions of Promis.e and Bentley Substation)&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backward compatible, meaning SSMS 2014 can manage SQL Server 2008, but SSMS 2008 cannot connect to SQL Server 2014.&lt;/p&gt;
&lt;p&gt;SSMS is not included with Promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Promis.e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/p&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, en, SELECTsupport, Problem Solving&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/34</link><pubDate>Thu, 26 Oct 2017 14:13:20 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 34 posted to OpenUtilities Wiki by Matt_P on 10/26/2017 2:13:20 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.73&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;Promis.e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and web sites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of Promis.e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Requirements for a successful connection:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in Promis.e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to Promis.e and Bentley Substation&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and Promis.e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]] dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server...&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The SqlServerProject.sql script from pre-SELECTseries 4 era software also created the above login.The SqlServerProject.sql script included with recent releases no longer creates this login.&lt;/p&gt;
&lt;p&gt;If the SQL Server was originally installed via a promis.e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right-click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case, only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case, the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the Promis.e or Bentley Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;In single-user environments, the SQL Server hosting the project database is often installed on the user&amp;#39;s workstation. Since the SQL Server service is set to start Automatically by default, rebooting the workstation often resolves the problem of a stopped service.&lt;/p&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right-click it and select &lt;strong&gt;Start&lt;/strong&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start &lt;strong&gt;Automatically&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right-click the &lt;strong&gt;Protocols for&lt;/strong&gt; the instance name, and select &lt;strong&gt;Properties&lt;/strong&gt;.&amp;nbsp; Enable the &lt;strong&gt;TCP/IP&lt;/strong&gt; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a required structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of Promis.e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the &lt;strong&gt;Object Explorer&lt;/strong&gt; to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For SQL Server 2014 the files are often located in a path similar to&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2005, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right-click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" height="500" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right-click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2014&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2014?&lt;br /&gt;&lt;a href="https://technet.microsoft.com/en-us/library/ms191464(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://technet.microsoft.com/en-us/library/ms191464(v=sql.120).aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="https://msdn.microsoft.com/en-us/library/cc646023(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/cc646023(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="https://technet.microsoft.com/en-us/library/ms177440(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://technet.microsoft.com/en-us/library/ms177440(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="https://msdn.microsoft.com/en-us/library/ms181087(v=sql.120).aspx" rel="noopener noreferrer" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/ms181087(v=sql.120).aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backward compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;/p&gt;
&lt;p&gt;SSMS is not included with Promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis.e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis.e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;Promis.e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/p&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, en, SELECTsupport, Problem Solving&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/33</link><pubDate>Wed, 11 Jan 2017 21:57:01 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 33 posted to OpenUtilities Wiki by Matt_P on 1/11/2017 9:57:01 PM&lt;br /&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.73&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;Promis.e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and web sites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of Promis.e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Requirements for a successful connection:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in Promis.e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to Promis.e and Bentley Substation&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and Promis.e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]] dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server...&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The SqlServerProject.sql script from pre-SELECTseries 4 era software also created the above login.The SqlServerProject.sql script included with recent releases no longer creates this login.&lt;/p&gt;
&lt;p&gt;If the SQL Server was originally installed via a promis.e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right-click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case, only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case, the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the Promis.e or Bentley Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;In single-user environments, the SQL Server hosting the project database is often installed on the user&amp;#39;s workstation. Since the SQL Server service is set to start Automatically by default, rebooting the workstation often resolves the problem of a stopped service.&lt;/p&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right-click it and select &lt;strong&gt;Start&lt;/strong&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start &lt;strong&gt;Automatically&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right-click the &lt;strong&gt;Protocols for&lt;/strong&gt; the instance name, and select &lt;strong&gt;Properties&lt;/strong&gt;.&amp;nbsp; Enable the &lt;strong&gt;TCP/IP&lt;/strong&gt; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a required structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of Promis.e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the &lt;strong&gt;Object Explorer&lt;/strong&gt; to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For SQL Server 2014 the files are often located in a path similar to&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2005, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right-click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" width="679" height="500" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right-click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backward compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;/p&gt;
&lt;p&gt;SSMS is not included with Promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis.e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis.e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;Promis.e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " width="189" height="60" /&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, en, SELECTsupport, Problem Solving&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/32</link><pubDate>Wed, 11 Jan 2017 21:28:42 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 32 posted to OpenUtilities Wiki by Matt_P on 1/11/2017 9:28:42 PM&lt;br /&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.73&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;Promis.e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and web sites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of Promis.e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Requirements for a successful connection:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in Promis.e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to Promis.e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and Promis.e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]] dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server...&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The SqlServerProject.sql script from pre-SELECTseries 4 era software also created the above login.The SqlServerProject.sql script included with recent releases no longer creates this login.&lt;/p&gt;
&lt;p&gt;If the SQL Server was originally installed via a promis.e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case, only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case, the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the Promis.e or Bentley Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;In single-user environments, the SQL Server hosting the project database is often installed on the user&amp;#39;s workstation. Since the SQL Server service is set to start Automatically by default, rebooting the workstation often resolves the problem of a stopped service.&lt;/p&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right-click it and select &lt;strong&gt;Start&lt;/strong&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start &lt;strong&gt;Automatically&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right-click the &lt;strong&gt;Protocols for&lt;/strong&gt; the instance name, and select &lt;strong&gt;Properties&lt;/strong&gt;.&amp;nbsp; Enable the &lt;strong&gt;TCP/IP&lt;/strong&gt; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a required structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of Promis.e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the &lt;strong&gt;Object Explorer&lt;/strong&gt; to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For SQL Server 2014 the files are often located in a path similar to&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2005, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right-click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" width="679" height="500" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right-click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backward compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;/p&gt;
&lt;p&gt;SSMS is not included with Promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis.e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis.e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;Promis.e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " width="189" height="60" /&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, en, SELECTsupport, Problem Solving&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/31</link><pubDate>Thu, 01 Sep 2016 16:58:23 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 31 posted to OpenUtilities Wiki by Matt_P on 9/1/2016 4:58:23 PM&lt;br /&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.57&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;Promis.e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of Promis.e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Requirements for a successful connection:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in Promis.e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to Promis.e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and Promis.e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]] dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server...&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The SqlServerProject.sql script from pre-SELECTseries 4 era software also created the above login.The SqlServerProject.sql script included with recent releases no longer creates this login.&lt;/p&gt;
&lt;p&gt;If the SQL Server was originally installed via a promis.e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the Promis.e or Bentley Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a required structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of Promis.e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For SQL Server 2014 the files are often located in a path similar to&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2005, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" width="679" height="500" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;/p&gt;
&lt;p&gt;SSMS is not included with Promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis.e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis.e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;Promis.e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " width="189" height="60" /&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, en, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/30</link><pubDate>Mon, 12 Oct 2015 16:04:45 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 30 posted to OpenUtilities Wiki by Matt_P on 10/12/2015 4:04:45 PM&lt;br /&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.137&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis.e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis.e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Requirements for a successful connection:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis.e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis.e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis.e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]]&lt;i&gt;&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server...&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The SqlServerProject.sql script from pre-SELECTseries 4 era software also created the above login.The SqlServerProject.sql script included with recent releases no longer creates this login.&lt;/p&gt;
&lt;p&gt;If the SQL Server was originally installed via a promis.e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis.e or Bentley Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a required structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis.e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For SQL Server 2014 the files are often located in a path similar to&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For SQL Server 2005, a typical path is:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;/p&gt;
&lt;p&gt;SSMS is not included with promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis.e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis.e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis.e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, en, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/29</link><pubDate>Fri, 29 May 2015 19:48:07 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 29 posted to OpenUtilities Wiki by Matt_P on 5/29/2015 7:48:07 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.137&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]]&lt;i&gt;&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;. If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;If SQL Server Management Studio is not installed, see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &lt;strong&gt;&amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;/p&gt;
&lt;p&gt;SSMS is not included with promis.e and Bentley Substation packages that include SQL Server 2014 Express. See [[Install SQL Server Management Studio]].&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Install SQL Server Management Studio]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/28</link><pubDate>Tue, 17 Mar 2015 17:37:49 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 28 posted to OpenUtilities Wiki by Matt_P on 3/17/2015 5:37:49 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration ANSI-IEEE Default&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration IEC Default&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]]&lt;i&gt;&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), &lt;strong&gt;Windows Authentication&lt;/strong&gt; can often be used instead of &lt;strong&gt;SQL Server Authentication&lt;/strong&gt; and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &amp;gt; Project Database.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/27</link><pubDate>Tue, 03 Mar 2015 14:49:56 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 27 posted to OpenUtilities Wiki by Matt_P on 3/3/2015 2:49:56 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unable to connect to database server&lt;/li&gt;
&lt;li&gt;Unable to connect to setup configuration&lt;/li&gt;
&lt;li&gt;Login failed for user &amp;#39;ecaduser&amp;#39;&lt;/li&gt;
&lt;li&gt;You have no available database connection&lt;/li&gt;
&lt;li&gt;Configuration not saved. A network-related to instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.&amp;nbsp; Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
&lt;ul&gt;
&lt;li&gt;(provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)&lt;/li&gt;
&lt;li&gt;(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)&lt;/li&gt;
&lt;li&gt;(provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Configuration not saved:A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]]&lt;i&gt;&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started (for example &amp;quot;The request failed or the service did not respond in a timely fashion&amp;quot;), open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;/p&gt;
&lt;p&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &amp;gt; Project Database.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/26</link><pubDate>Fri, 16 Jan 2015 18:16:10 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 26 posted to OpenUtilities Wiki by Matt_P on 1/16/2015 6:16:10 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]]&lt;i&gt;&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If a non-standard static port is used it is possible to specify the port used for connecting to the SQL Server instead of running the SQL Server Browser service on the server.&amp;nbsp; The format for the Server Name field on Setup is the Microsoft standard convention:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starting the SQL Server Browser Service.&amp;nbsp; The browser service is required when using dynamic ports (default behavior) or a non-standard static port without specifying the port along with the server name.&amp;nbsp; See &lt;a href="#ServerName"&gt;The Server Name must be correct&lt;/a&gt; section regarding the specification of a static port.&lt;/li&gt;
&lt;li&gt;Enabling the TCP/IP protocol for the SQL service&lt;/li&gt;
&lt;li&gt;Adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See the links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &amp;gt; Project Database.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/25</link><pubDate>Fri, 16 Jan 2015 17:09:33 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 25 posted to OpenUtilities Wiki by Matt_P on 1/16/2015 5:09:33 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the [[Setup]]&lt;i&gt;&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the [[Setup]] dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;Instance names are not case sensitive.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If non-standard static ports are used and it is necessary to specify the port used for connecting to the SQL Server, the format is:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio (SSMS) from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog. This may provide a more verbose error message that can be then investigated further. Generally, the settings used to successfully connect via SSMS can be used on [[Setup]] &amp;gt; Project Database.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/24</link><pubDate>Fri, 16 Jan 2015 15:56:02 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 24 posted to OpenUtilities Wiki by Matt_P on 1/16/2015 3:56:02 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specifying a Port&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If non-standard static ports are used and it is necessary to specify the port used for connecting to the SQL Server, the format is:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note there are no spaces between any of the elements and separators in what is specified for the Server Name field.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/23</link><pubDate>Fri, 16 Jan 2015 15:52:42 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 23 posted to OpenUtilities Wiki by Matt_P on 1/16/2015 3:52:42 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this article.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;It is also possible, but not necessarily recommended, to use the IP address of the server in place of the server machine name:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;192.168.1.106&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h3&gt;Specifying a Port&lt;/h3&gt;
&lt;p&gt;If non-standard static ports are used and it is necessary to specify the port used for connecting to the SQL Server, the format is:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;PORT&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p style="margin-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;ENGRSERVER&lt;/span&gt;&lt;strong&gt;\&lt;/strong&gt;&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;strong&gt;,&lt;/strong&gt;49170&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] article.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/22</link><pubDate>Wed, 24 Dec 2014 17:57:21 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 22 posted to OpenUtilities Wiki by Matt_P on 12/24/2014 5:57:21 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this TechNote.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL Server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local (installed on the workstation) or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to the SQL Server using SQL Server Management Studio on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;h3&gt;Wrong login or password&lt;/h3&gt;
&lt;p&gt;Another common cause of connection problems is using the wrong SQL Server Authentication login or password, or the login does not even exist in SQL Server.&lt;/p&gt;
&lt;p&gt;If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;h3&gt;Login does not exist&lt;/h3&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser login that may have once worked may need to be created again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login will not exist or will not be associated with the database.&lt;/p&gt;
&lt;p&gt;In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;h3&gt;SQL Server not configured for SQL Authentication&lt;/h3&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;/p&gt;
&lt;h3&gt;The data files for the database must not be compressed&lt;/h3&gt;
&lt;p&gt;One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - Bentley Substation]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/21</link><pubDate>Fri, 01 Aug 2014 14:08:33 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 21 posted to OpenUtilities Wiki by Matt_P on 8/1/2014 2:08:33 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this TechNote.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to SQL Server with SQL Server Management Studio run on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;p&gt;Another common cause of connection problems is the wrong SQL Server Authentication password.&amp;nbsp; If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser SQL login that may have once worked may need to be created again.&amp;nbsp; If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login may not exist.&amp;nbsp; In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Note that using a forward slash will not work.&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;There should be no leading slashes before the machine name as if this was a UNC path.&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;NOTE: The .mdf and .ldf files for the database must not be compressed.&lt;/b&gt;&amp;nbsp; One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e|Compatibility Chart (promis&amp;bull;e)]]&lt;/p&gt;
&lt;p&gt;[[5930|Compatibility Chart (Bentley Substation)]]&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/20</link><pubDate>Tue, 21 Jan 2014 21:15:55 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 20 posted to OpenUtilities Wiki by Matt_P on 1/21/2014 9:15:55 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt=" " src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this TechNote.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to SQL Server with SQL Server Management Studio run on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the [[Setup]] dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the [[Setup]] dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;p&gt;Another common cause of connection problems is the wrong SQL Server Authentication password.&amp;nbsp; If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser SQL login that may have once worked may need to be created again.&amp;nbsp; If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login may not exist.&amp;nbsp; In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;NOTE: The .mdf and .ldf files for the database must not be compressed.&lt;/b&gt;&amp;nbsp; One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" width="679" height="500" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the&amp;nbsp; [[Compatibility Chart - promis.e|promis&amp;bull;e Compatibility Chart]] and the [[5930|Bentley Substation Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e|Compatibility Chart (promis&amp;bull;e)]]&lt;/p&gt;
&lt;p&gt;[[5930|Compatibility Chart (Bentley Substation)]]&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, SQL Server, error message, Installation/Configuration, how to, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/19</link><pubDate>Tue, 03 Dec 2013 14:38:25 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 19 posted to OpenUtilities Wiki by Matt_P on 12/3/2013 2:38:25 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this TechNote.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to SQL Server with SQL Server Management Studio run on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;p&gt;Another common cause of connection problems is the wrong SQL Server Authentication password.&amp;nbsp; If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser SQL login that may have once worked may need to be created again.&amp;nbsp; If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login may not exist.&amp;nbsp; In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the&lt;strong&gt; SQL Server Browser&lt;/strong&gt; service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;NOTE: The .mdf and .ldf files for the database must not be compressed.&lt;/b&gt;&amp;nbsp; One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the promis&amp;bull;e [[Compatibility Chart - promis.e|Compatibility Chart]] and the Substation [[5930|Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Compatibility Chart - promis.e|Compatibility Chart (promis&amp;bull;e)]]&lt;/p&gt;
&lt;p&gt;[[5930|Compatibility Chart (Bentley Substation)]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, SQL Server, error message, Installation/Configuration, Bentley Substation, SELECTsupport, Problem Solving, Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/18</link><pubDate>Tue, 26 Nov 2013 15:17:53 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 18 posted to OpenUtilities Wiki by Matt_P on 11/26/2013 3:17:53 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this TechNote.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to SQL Server with SQL Server Management Studio run on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;p&gt;Another common cause of connection problems is the wrong SQL Server Authentication password.&amp;nbsp; If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser SQL login that may have once worked may need to be created again.&amp;nbsp; If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login may not exist.&amp;nbsp; In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the SQL Server Browser service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;NOTE: The .mdf and .ldf files for the database must not be compressed.&lt;/b&gt;&amp;nbsp; One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327%28v=sql.90%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the promis&amp;bull;e [[Compatibility Chart - promis.e|Compatibility Chart]] and the Substation [[5930|Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation, Problem Solving, Error Message, Platform Support, Database Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/17</link><pubDate>Wed, 16 Oct 2013 16:26:16 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 17 posted to OpenUtilities Wiki by Matt_P on 10/16/2013 4:26:16 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this TechNote.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to SQL Server with SQL Server Management Studio run on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Notes"&gt;Other Notes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Steps to Resolve&lt;/h1&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;p&gt;Another common cause of connection problems is the wrong SQL Server Authentication password.&amp;nbsp; If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser SQL login that may have once worked may need to be created again.&amp;nbsp; If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login may not exist.&amp;nbsp; In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the SQL Server Browser service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;/p&gt;
&lt;p&gt;For SQL Server 2008, the path would be more like:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;/p&gt;
&lt;p&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;NOTE: The .mdf and .ldf files for the database must not be compressed.&lt;/b&gt;&amp;nbsp; One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="Notes"&gt;&lt;/a&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;SQL Server Management Studio (SSMS) is backwards compatible, meaning SSMS 2008 can manage SQL Server 2005, but SSMS 2005 cannot connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the promis&amp;bull;e [[Compatibility Chart - promis.e|Compatibility Chart]] and the Substation [[5930|Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation use the .NET provider to connect to the SQL Server project database, so some connection issues can be caused by corruption of the .NET Framework.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&lt;a name="ExternalLinks"&gt;&lt;/a&gt;External Links&lt;/h1&gt;
&lt;p&gt;SQL Server Solution Center&lt;br /&gt;&lt;a href="http://support.microsoft.com/ph/14917"&gt;http://support.microsoft.com/ph/14917&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server 2005 Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port for SQL Server 2005&lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server 2008 Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port for SQL Server 2008&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e Installation Guide download page&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation, Problem Solving, Error Message, Platform Support, Database Platform Support&lt;/div&gt;
</description></item><item><title>Troubleshooting Project Database Connection Problems [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems/revision/16</link><pubDate>Tue, 10 Sep 2013 17:16:32 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e09a558b-cb50-4d3e-9ee5-f9846a22363a</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/4532/troubleshooting-project-database-connection-problems#comments</comments><description>Revision 16 posted to OpenUtilities Wiki by Matt_P on 9/10/2013 5:16:32 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;SQL Server&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Database Platform Support&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Overview&lt;/h1&gt;
&lt;p&gt;promis&amp;bull;e and Bentley Substation require a connection to a SQL project database in order to function.&amp;nbsp; If such a connection does not exist, an error message such as the following may be displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to database server&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Unable to connect to setup configuration&amp;rdquo;&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Login failed for user ecaduser&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;You have no available database connection&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The purpose of this document is to serve as a guide for troubleshooting these connection problems when SQL Server is the database server software used.&amp;nbsp; Oracle can be used as the database server software but is not covered in this TechNote.&lt;/p&gt;
&lt;p&gt;This document assumes that Microsoft SQL Server has been successfully installed.&amp;nbsp; If there was a problem during installation, please consult the documentation and websites for SQL Server.&lt;br /&gt;&lt;br /&gt;Some questions to keep in mind while troubleshooting connection problems or requesting technical support include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Was this working at one time? (What might have changed?)&lt;/li&gt;
&lt;li&gt;Is this a new installation of promis&amp;bull;e, Substation, or SQL server?&lt;/li&gt;
&lt;li&gt;Is the SQL Server local or on a network server?&lt;/li&gt;
&lt;li&gt;Was the database recently moved or restored?&lt;/li&gt;
&lt;li&gt;Is any workstation able to connect to the project database?&lt;/li&gt;
&lt;li&gt;Can you connect to SQL Server with SQL Server Management Studio run on the server?&amp;nbsp; When run on the client workstation?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Requirements for a successful connection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#ConnectionEnabled"&gt;The connection must be enabled on the Setup dialog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#SoftwareInstalled"&gt;SQL Server software must be installed on the machine that is to host the SQL Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#LoginValid"&gt;The login must be valid&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServerName"&gt;The Server Name must be correct, including the instance name&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ServiceRunning"&gt;The SQL service must be running on the server machine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#DatabaseExist"&gt;The database must exist and be attached to the SQL Server&lt;/a&gt;, an empty or arbitrarily created database cannot be used, the .mdf and .ldf files for the database must not be compressed.&lt;/li&gt;
&lt;li&gt;&lt;a href="#RemoteConnections"&gt;The server must be configured for remote connections&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Click the Apply button on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog in&amp;nbsp;promis&amp;bull;e/Substation after making changes to see if a connection can be made.&amp;nbsp; A successful connection to the project database is indicated by no error message being returned.&amp;nbsp; The connection is confirmed by the ability to create new projects or open existing projects that are in the database specified on the &lt;i&gt;[[Setup]]&lt;/i&gt; dialog.&lt;/p&gt;
&lt;p&gt;For the remainder of this document, &amp;quot;the software&amp;quot; will refer to promis&amp;bull;e and Bentley Substation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ConnectionEnabled"&gt;&lt;/a&gt;The connection must be enabled on the Setup dialog&lt;/h2&gt;
&lt;p&gt;If everything was working and promis&amp;bull;e/Substation projects could recently be opened and created by the workstation now encountering the problem, sometimes all that is necessary is to enable the appropriate radio button on the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; If neither the &amp;ldquo;SQL Server/MSDE&amp;rdquo; nor the &amp;ldquo;Oracle&amp;rdquo; options are enabled, the software will not have a project database connection even if the remainder of the settings are valid.&amp;nbsp; Unless you know that you are using an Oracle server, enable the &amp;ldquo;SQL Server/MSDE&amp;rdquo; option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="SoftwareInstalled"&gt;&lt;/a&gt;The SQL Server software must be installed on the machine that is to host the SQL Server&lt;/h2&gt;
&lt;p&gt;This means that the promis&amp;bull;e Data Server or Microsoft&amp;rsquo;s SQL Server installation files must be run on the machine that is to act as the server.&amp;nbsp; Running the installation files on a workstation will not install the software onto a network server machine.&lt;br /&gt;&lt;br /&gt;An indication that SQL Server is installed is that a &amp;ldquo;Microsoft SQL Server&amp;rdquo; program group exists in &lt;b&gt;Start &amp;gt; Programs&lt;/b&gt; on the machine hosting the database.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="LoginValid"&gt;&lt;/a&gt;The login must be valid&lt;/h2&gt;
&lt;p&gt;Another common cause of connection problems is the wrong SQL Server Authentication password.&amp;nbsp; If the database was created automatically by the software or by a script from pre-SELECTseries 4 era software, the SQL login created may use the following credentials:&lt;/p&gt;
&lt;p&gt;Login name: &lt;b&gt;ecaduser&lt;/b&gt;&lt;br /&gt;Password: &lt;b&gt;Ecad1pass&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the SQL Server was originally installed via a promis&amp;bull;e 2007 v2.0.x installation file or CD, the password may be: &lt;b&gt;ecadpassword&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;If the SQL Server that is to be used is installed by the user (not by an admin with a different Windows login), Windows Authentication can often be used instead of SQL Server Authentication and requires no password be entered on the Setup dialog.&lt;/p&gt;
&lt;p&gt;It is possible that a database administrator (DBA) created another SQL login with a different name and/or password or created Windows logins for each user, allowing users to select Windows Authentication on the &lt;i&gt;Setup&lt;/i&gt; dialog.&amp;nbsp; Contact the DBA for help in these situations.&lt;/p&gt;
&lt;p&gt;If the SQL Server is configured for Windows Authentication only, the following message can result when trying to connect with SQL Server Authentication: &lt;br /&gt;&lt;br /&gt;&lt;i&gt;&amp;quot;Login failed for user &amp;#39;ecaduser&amp;#39;. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error 18452)&amp;quot; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To be able to connect with SQL Server Authentication, the SQL server must be configured to use &amp;quot;SQL Server and Windows Authentication mode&amp;quot; instead of only &amp;quot;Windows Authentication mode&amp;quot;.&amp;nbsp; To view or modify this setting, connect with SQL Server Management Studio (using Windows Authentication), right click the server name in the Object Explorer, and select &lt;b&gt;Properties &amp;gt; Security&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the database was moved to a different server, the ecaduser SQL login that may have once worked may need to be created again.&amp;nbsp; If the database was created using the SqlServerProject.sql for recent versions of the software, the SQL login may not exist.&amp;nbsp; In these cases, see [[5824|Creating an SQL Server Login]].&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServerName"&gt;&lt;/a&gt;The Server Name must be correct&lt;/h2&gt;
&lt;p&gt;In the Project Database area of the &lt;i&gt;Setup&lt;/i&gt; dialog, the machine name of the computer hosting the project database should be entered into the Server Name field, followed by a backslash ( \ ) and then the SQL instance name:&lt;br /&gt;&lt;span style="color:#993300;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;span style="color:#000000;"&gt;&lt;b&gt;\&lt;/b&gt;&lt;/span&gt;&lt;span style="color:#0000ff;"&gt;INSTANCE&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Standard and higher (non-Express) editions of SQL Server may not use an instance name.&amp;nbsp; In this case only the machine name of the server should be entered into the Server Name field, with no backslash or instance name:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="color:#993300;font-family:courier new,courier;"&gt;SERVERMACHINENAME&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;When the SQL Server is located on the workstation, the text &amp;ldquo;(local)&amp;rdquo; can be substituted for the actual machine name.&amp;nbsp; In this case the workstation is also acting as the server machine:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;span style="color:#993300;"&gt;(local)&lt;/span&gt;\&lt;span style="color:#0000ff;"&gt;BENTLEYECAD&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The name of the SQL instance is most likely either BENTLEYECAD or ECTECAD if the SQL Server was installed via the promis&amp;bull;e/Substation installation.&amp;nbsp; However, it could be the default name of SQLEXPRESS or whatever was specified during a standalone installation of SQL Server Express.&lt;/p&gt;
&lt;p&gt;To verify the names of the installed instance(s), on the server machine select &lt;b&gt;Start &amp;gt; All Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager&lt;/b&gt;, where xxxx is the version such as &amp;quot;2005&amp;quot; or &amp;quot;2008&amp;quot;.&amp;nbsp; In the configuration manager, click on &amp;quot;SQL Server Services&amp;quot; in the left pane and view the instance names in the right pane.&lt;/p&gt;
&lt;h2&gt;&lt;a name="ServiceRunning"&gt;&lt;/a&gt;The SQL service must be running on the server machine&lt;/h2&gt;
&lt;p&gt;To determine if the service is running, select &lt;b&gt;Start &amp;gt; Programs &amp;gt; Microsoft SQL Server xxxx &amp;gt; Configuration Tools &amp;gt; SQL Server Configuration Manager &lt;/b&gt;on the server machine.&amp;nbsp; In the configuration manager, click on SQL Server Services in the left pane and view the instance names in the right pane.&amp;nbsp;&amp;nbsp; The SQL Service for the instance that the software uses must be running in order to connect to it.&amp;nbsp;&amp;nbsp; If the service is stopped, right click it and select &amp;ldquo;Start&amp;rdquo;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/6354.ConfigurationManager.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If the service cannot be started, open the ERRORLOG file with a text editor and look for an error number.&amp;nbsp; Search the internet for the error number/message. &amp;nbsp;&lt;br /&gt;&lt;br /&gt;The ERRORLOG file should be found in a path similar to one of the following:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ &lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\Log\&lt;br /&gt;&lt;br /&gt;If other machines are to connect to the SQL Server, use the SQL Server Configuration Manager to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the SQL Server Browser service and set it to start Automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Expand the SQL Server Network Configuration item in the left pane and right click the &amp;quot;Protocols for&amp;quot; the instance name, and select Properties.&amp;nbsp; Enable the &amp;quot;TCP/IP&amp;quot; protocol.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="DatabaseExist"&gt;&lt;/a&gt;The database must exist and be attached to the SQL Server&lt;/h2&gt;
&lt;p&gt;The project database has a defined schema, or structure.&amp;nbsp; &lt;span style="background-color:#ffff00;"&gt;&lt;strong&gt;An empty or arbitrarily created database cannot be used.&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; Scripts and front-end tools are provided for creating the project database on existing SQL Servers.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;p&gt;The names of promis&amp;bull;e project databases usually begin with &amp;quot;promise&amp;quot;.&lt;/p&gt;
&lt;p&gt;The names of Bentley Substation project databases usually begin with &amp;quot;Substation&amp;quot;.&lt;/p&gt;
&lt;p&gt;To determine what databases are attached to the SQL Server, start Microsoft SQL Server Management Studio (SSMS) on the server machine and connect.&amp;nbsp; Look in the Databases &amp;ldquo;folder&amp;rdquo; in the Object Explorer to determine the name of the database(s).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="/resized-image.ashx/__size/309x0/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/5483.attached.PNG" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;If there is more than one instance, connect to the various instances and look for the project databases.&amp;nbsp; Note the name of the database and the instance it was found in and use these on the&lt;i&gt; Setup&lt;/i&gt; dialog of the software.&lt;/p&gt;
&lt;p&gt;Alternatively, search for the .mdf and .ldf files that constitute SQL databases on the machine hosting the SQL Server.&amp;nbsp; This method does not indicate if the databases are attached, however.&amp;nbsp; For SQL Server 2005, the files are often located in a path similar to:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data&lt;br /&gt;&lt;br /&gt;For SQL Server 2008, the path would be more like:&lt;br /&gt;&lt;br /&gt;C:\Program Files\Microsoft SQL Server\MSSQL10.BENTLEYECAD\MSSQL\DATA&lt;br /&gt;&lt;br /&gt;For example, files named promise2.mdf and promise2_log.ldf indicate a database named &amp;ldquo;promise2&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After determining the database name(s), try specifying it on the Project Database area of &lt;i&gt;Setup&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;If the data files for the project database exist but the database does not appear in the Object Explorer in SSMS, try attaching the database to the server.&amp;nbsp; In SSMS, right click the Databases folder in Object Explorer and select Attach.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;NOTE: The .mdf and .ldf files for the database must not be compressed.&lt;/b&gt;&amp;nbsp; One indication that a file is compressed is that the text of the file name appears blue in Windows Explorer:&lt;/p&gt;
&lt;p&gt;&lt;img title="Compressed &amp;quot;promise&amp;quot; database files" alt="Compressed &amp;quot;promise&amp;quot; database files" src="/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-26/8468.compressed.PNG" height="500" width="679" /&gt;&lt;/p&gt;
&lt;p&gt;Disk clean-up utilities have been known to compress SQL database files.&amp;nbsp; A database with compressed datafiles can appear in the Object Explorer of SSMSE with no &amp;quot;subfolders&amp;quot; within it.&amp;nbsp; To decompress the files:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;li&gt;Select the files in Windows Explorer&lt;/li&gt;
&lt;li&gt;Right click the selection and select Properties&lt;/li&gt;
&lt;li&gt;Click the Advanced button&lt;/li&gt;
&lt;li&gt;Disable the &amp;ldquo;Compress contents to save disk space&amp;rdquo; check box, click OK&lt;/li&gt;
&lt;li&gt;Click OK to exit the &lt;i&gt;Properties&lt;/i&gt; dialog&lt;/li&gt;
&lt;li&gt;Start the SQL Service using SQL Server Configuration Manager&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&lt;a name="RemoteConnections"&gt;&lt;/a&gt;The Server Must Be Configured for Remote Connections&lt;/h2&gt;
&lt;p&gt;If the SQL Server hosting the project database is running on a different machine than the workstation, the server machine must be configured to allow remote connections.&amp;nbsp; This often entails starting the SQL Server Browser Service, enabling the TCP/IP protocol for the SQL service, and adding exceptions to the firewall for the port used by SQL Server or for the SQL Server program.&amp;nbsp; See the&amp;nbsp; links below for more information&lt;/p&gt;
&lt;h3&gt;SQL Server 2005&lt;/h3&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port &lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;SQL Server 2008&lt;/h3&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087.aspx&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;Other Notes&lt;/h2&gt;
&lt;p&gt;You cannot use SQL Server Management Studio 2005 to connect to SQL Server 2008.&lt;br /&gt;&lt;br /&gt;Ensure the version of SQL Server is compatible with the version of the software.&amp;nbsp; Consult the &lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e installation guide&lt;/a&gt; and the promis&amp;bull;e [[Compatibility Chart - promis.e|Compatibility Chart]] and the Substation [[5930|Compatibility Chart]].&amp;nbsp; If the script to create the project database is run on an incompatible SQL server version, the resulting database can be incomplete and will not work.&lt;/p&gt;
&lt;p&gt;If problems persist, try connecting to the SQL Server using SQL Server Management Studio from the workstation using the same credentials as being used on the &lt;em&gt;Setup&lt;/em&gt; dialog..&amp;nbsp; This may provide a more verbose error message that can be then investigated further.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;p&gt;&lt;a href="/Products/w/Products__Wiki/product-technotes-and-faqs.aspx"&gt;Product TechNotes and FAQs&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&lt;a name="ExternalLinks"&gt;&lt;/a&gt;External Links&lt;/h1&gt;
&lt;p&gt;SQL Server Solution Center&lt;br /&gt;&lt;a href="http://support.microsoft.com/ph/14917"&gt;http://support.microsoft.com/ph/14917&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;How to configure SQL Server 2005 to allow remote connections &lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/914277"&gt;http://support.microsoft.com/kb/914277&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;How to: Configure a Firewall for SQL Server 2005 Access&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms175043%28v=sql.90%29.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring a Fixed Port for SQL Server 2005&lt;br /&gt;&lt;a href="http://technet.microsoft.com/en-us/library/ms345327.aspx"&gt;http://technet.microsoft.com/en-us/library/ms345327.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;How to enable remote connections in SQL Server 2008?&lt;br /&gt;&lt;a href="http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx"&gt;http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Configuring the Windows Firewall to Allow SQL Server 2008 Access &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc646023.aspx"&gt;http://msdn.microsoft.com/en-us/library/cc646023.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Configuring a Fixed Port for SQL Server 2008&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms345327%28v=sql.100%29.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SQL Server Browser Service &lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms181087.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms181087.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://docs.bentley.com/product.php?prod=223&amp;amp;"&gt;promis&amp;bull;e Installation Guide download page&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation, Problem Solving, Error Message, Platform Support, Database Platform Support&lt;/div&gt;
</description></item></channel></rss>