The creation of or connection to the steadyPRINT database on an SQL server failed

Description of the problem

The creation of or connection to the steadyPRINT database fails as a connection to the SQL server is not possible.

Possible error messages in CreateSteadyDB:

• [DBNETLIB][ConnectionOpen (Connect()).]SQL does not exist or access denied.
• Error 27502 – A connection to the SQL server could not be established.
• Login failed for user ‘[USER]’

Possible error messages displayed in the Windows Event Viewer of the SQL Server:

“Login error for the user [USER]. […] A login corresponding to the specified name could not be found. (CLIENT: <namedpipe>)”

Solution

The following items need to be reviewed:

• Check the Firewall Settings of the SQL Server and the system from which you would like to establish the connection.
• Make sure that the service SQL Server Browser runs on the SQL Server which can be started via the Sql Server Configuration Manager under SQL Server Service or the Windows Services.
• Make sure that the Server Authentication is adjusted to SQL Server and Windows Authentication Mode (mixed authentication). This option can be found under Server Properties in the Microsoft SQL Server Management Studio.
• Make sure that the SA user is enabled to create and update the steadyPRINT database.
• Make sure that the SQL Server can be reached via the port 1433 and 1434 (Default):

1. Open the Sql Server Configuration Manager on the SQL server.
2. Go to the node SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for “[INSTANZNAME]”.
3. Make sure that the status of the TCP/IP protocol is Activated on its right side.
4. Open the properties of the TCP/IP protocol and change to the tab IP addresses.
5. Adjust the property TCP port to the required port (Default: 1433) under IPALL.

• Make sure that Named Pipes are activated on the SQL server:

1. Open the Sql Server Configuration Manager on the SQL server.
2. the node SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for “[INSTANZNAME]”.
3. Make sure that the status of the Named Pipes protocol is Activated on its right side.

• Make sure that the specified SQL user exists and is authorized to create the database.
• Complete indication of the databse instance: The required indication for the database is composed of the server name and the database instance. Syntax: [SERVER]\[Instance Name of DB]. Beispiel: SQL-W2k3SQLEXPRESS

Also see

Error when creating tables

ID: 21656 | Zur deutschen Version