Troubleshooting

If the server isn't listening on port 1433, enable remote connections for the SQL server:

  1. In the SQL Server Configuration Manager, expand SQL Server Network Configuration, and then click Protocols for <instancename>.
  2.  In the details pane, right-click one of the available protocols, and then click Properties.
  3. To enable the TCP/IP protocol (or named pipes) for remote connections, set the Enabled box to Yes.

Error Messages and Responses

Below is a listing of some of the errors you may encounter and suggestions on how to address them:

Error Message

Source

Response

Unable to continue, IIS URL Rewrite is not installed

_output

Install URL Rewrite module from https://www.iis.net/downloads/microsoft/url-rewrite#additionalDownloads

IIS site [CUSTOMER_DATABASE] does not exist

_output

Log in to IIS Services and start [CUSTOMER_DATABASE] service

Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Named Pipes Provider: Could not open a connection to SQL Server [53].

logs

Ensure “Main” connection is set correctly and the @REM statement has been removed. If changes need to be made to web.config after initial deployment, then web.config in _CUST directory needs to be updated for the changes to be reflected

Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login failed for user '[DATABASE_USER]’.  Reason: The password of the account must be changed.

logs

Check the DATABASE USER set up in Create Application and Server Database User and ensure that Ensure that user must change password is unchecked

Website cannot be started another website may be using the same port

IIS

Review ‘Netstat’ and ‘Netsh http show urlacl’ command outputs to see whether the port 443 is in use, or reserved

Database connection down.  Description: Provider cannot be found. It may not be properly installed.  Source:ADODB.Connection

Landing page

If multiple servers, ensure that SQL Server Native Client 11 is in the list of ODBC drivers in the application web server ODBC data sources control panel

Unable to continue, sqlcmd.exe was not found.

Command window

If this error is displayed when running deploy-only-CUSTOMERNAME.bat, ensure that sqlcmd was installed.  If it was installed, use “where sqlcmd” to check the path to the executable, then ensure that the path is one of those in the _PremiseDeploy10x.ps1 file in the $pathListSqlcmd variable

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.

0 comments

Article is closed for comments.