isNeatPublish Troubleshooting

Failed to connect to server

When deploying, the message "Failed to connect to server" appears.

  • Resolution: The SSIS deployment/publish requires the deployment target SQL Server instance service to be started (also make sure it has a Startup Type of Automatic) as it needs to access the SSIS catalog database. Go to Control Panel | Administration | Local/Services | SQL Server (SQL-Server-instance-name) | right-click and select Start.
    • Note that the SQL Server service name depends on the target instance name

SQL Agent Jobs

If SQL Agent jobs are being published, the deployment may fail if the SQL Agent service is not Started

  • Resolution: Make sure the target server has the SQL Agent server started (and has a Startup Type of Automatic). Go to Control Panel | Administration | Local/Services | SQL Server Agent (SQL-Server-instance-name) | right-click and select Start.
    • Note that the SQL Server Agent service name depends on the target SSRS instance

SSIS project file (.dtproj) import - "A deployment model of Package found - only 'Project' deployment models are supported..."

SSIS project file (.dtproj) import results in message "A deployment model of Package found - only 'Project' deployment models are supported - to convert to a Project deployment model click on the link below"

Convert a project to the project deployment model

  • Resolution 1: As the above link suggests, conversion of the SSIS project from a package to a project deployment model will allow importing of the .dtproj settings.
  • Resolution 2: Manually enter the deployment details - see here.
  • Resolution 3: Import via SSIS deployment file (.ispac) import - see here.