Cannot execute SSIS package in SQL Server 2016 - sql-server

I've seen this posted several times, but none of the fixes are working from my instance. I'm using SSDT 2015 to create the package and deploying to a network server using SQL Server 2016. The package target server version is set to SQL Server 2016 and I've changed the run time from 64 to 32 bit (not sure if this is needed, but listed as a fix for this issue). The connection managers are using my local server (different from the server the package is being executed from) and the network server where the package is being deployed. I'm able to successfully run the package in SSDT 2015, but when deployed to the server I get the errors below stating that the connection to my local server could not be established. I the validation of the connection and the data flow to delay validation and the first two tasks run, but again, it cannot connect to my local. Since I'm running the package with my credentials, I'm not sure why it cannot connect. I am a system admin for both Server instances and I've ensured that my login has ssis_admin role assigned on SSISDB. Any assistance would be greatly appreciated.
Data Flow Task:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "localDB\SQL2016.Local" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
ApplicationDataETL:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Login timeout expired".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. ".

Just to update everyone, this was issues that had issues and they had their issues. First, the Integration Services on the network server had been stopped due to logon error, first major issue. Second, in order to allow the network server to have access to my local server, I had to open the configuration manager on my local SQL instance and enable TCP/IP under the configuration settings for my 2016 instance. At this point, I needed to run netstat on the command prompt using my SQL Server Instance ID to determine if it is listening to port 1433. To ensure remote access, I then had to add rules to my firewall to allow TCP 1433, UDP 1434, sqlservr.exe, and sqlbrowser.exe. Once this was all completed, I was then able to connect to my local server through ssms on the network server. Using the proxy account I created for SQLAgent, I the job was then able to process successfully.

Related

Sql jobs failed randomly to acquire connection after the activation of the Always ON feature

Since we activated the Always On mode on our server, we have some issues regarding our SQL jobs (running SSIS package) which failed randomly with this message :
Failed to acquire connection "DB". Connection may not be configured correctly or you may not have the right permissions on this connection.
More details :
This issue did not happen before the activation of the Always On
The connection is defined in an OLEDB component
We have another environment/server with this kind of architecture and there is no issue with it
Trace of the listener :
Message Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 15.0.2000.5 for 64-bit Copyright (C) 2019 Microsoft. All rights reserved.
Started: 2:18:01 PM Error: 2022-02-15 14:18:30.07
Code: 0xC0202009
Source: TestImport Connection manager "DB_PRIMARY"
Description: SSIS Error Code DTS_E_OLEDBERROR.
An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0"
Hresult: 0x80004005 Description: "Login timeout expired".
An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 11.0"
Hresult: 0x80004005
Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".
End Error Error: 2022-02-15 14:18:30.94 Code: 0xC00291EC
Source: Execute SQL Task Link coupons movement to collection Execute SQL Task D escription: Failed to acquire connection "DB_PRIMARY". Connection may not be configured correctly or you may not have the right permissions on this connection.
End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:18:01 PM Finished: 2:18:30 PM Elapsed: 29.984 seconds. The package execution failed. The step failed.
When enabling AlwaysOn, there is only one active database ("master") and synchronous or asynchornous copies that are call replicas ("slave") that you can't access to.
The SQL Agent operates on local database, that can be in the active or slave mode. When active, your job will operate. When slave your job will fail.
So is is necessary to ask is the database is active prior to all execution of SQL server Agent job.
I wrote some UDF to test if the database is reachable or not that you can have at :
SQL agent and AlwaysOn replicas (HADR – Availability Groups), is my database active?
And also to reproduce the SQL Server jobs on all replicas... !

Couldn't able to establish SSIS connection manager with Citrix home page's Visual studio but able to execute SSRS report with run option

We have Visual studio application in Citrix home page which is not able to establish SSIS connection manager, but it is able to execute SSRS report with run option and an error preventing SSRS preview from loading.
Error text:
Test connection failed because of an error in initializing provider. A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. Client unable to establish connection Encryption not supported on the client.
Provider used in SSRS connection : .Net framework data provider for SQL server
Provider used in SSIS connection : Native OLE DB/SQL Server Native Client 11.0
Please let me know if any more details required.

How to fix missing SQL connection manager in SSIS

I am trying to create an OLE DB connection in SSIS that I want to use for this package I am building which basically is supposed to do an ETL having it's source from Excel and the output in a SQL table. However, I am getting the error as below when trying to connect to the server and check in. I am using windows authentication and trying to connect locally using the '.' I also couldn't find the sql server configuration manager in my computer. I reinstalled my management studio 2018 version, but the didn't fix it either. Any insights would help on resolving this issue.
Thanks
Error message:
TITLE: Connection Manager
Test connection failed because of an error in initializing provider.
Login timeout expired A network-related or instance-specific error has
occurred while establishing a connection to SQL Server. Server is not
found or not accessible. Check if instance name is correct and if SQL
Server is configured to allow remote connections. For more information
see SQL Server Books Online. Named Pipes Provider: Could not open a
connection to SQL Server.

OLE DB error: OLE DB or ODBC error:

I am trying to connect from my SSAS server to SQL through SSMS and the connection works fine when I test it. But when I am processing the cube, I am getting the below error message.
OLE DB error: OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.
I have looked the other similar error message that was posted and tried the below options as per the suggestions.
SSAS - OLE DB error in establishing a connection
1. Restart SSAS Service
2. Restart SSAS using local system
3. Trying to change the Provider to Native OLE DB\Microsoft OLE DB Provider for SQL server, but still I am getting the below error
OLE DB error: OLE DB or ODBC error.
I am stuck with this for more than 3 days and not able to progress anything beyond. I tried all other Providers as well and still it doesn't work.
Additionally I made sure that the Windows account I am using in data source of SSAS server is having db_owner on the SQL data base.
Any help would be really appreciated to get me out of this.
I was able to get a solution for this upon trial and error method for selecting the below changes. I have tried to set the
1. Provider as "Native OLE DB/Microsoft OLE DB Provider for SQL Server"
2. Changed the connection from Windows Authentication to SQL connection.
3. The type of Impersonate Account from Windows Authentication to Authenticate by Service Account.
Once the above settings were done, I was able to process the Cube.

Cannot open existing package and msdb from integration system?

I have an sql server and its been installed as new instance called instance2 . Now when i tries to open MSDB folder under stored packages this gives me below error
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
The SQL Server instance specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in %SQL_PRODUCT_SHORT_NAME% Books Online.
Login timeout expired
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
------------------------------
Login timeout expired
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Server Native Client 11.0)
------------------------------
BUTTONS:
OK
------------------------------
Also Once i tried to open the package from visual studio it returns the below error
TITLE: Add Copy of Existing Package
------------------------------
An OLE DB error 0x80004005 (Login timeout expired) occurred while enumerating packages. A SQL statement was issued and failed.
------------------------------
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Login timeout expired) occurred while enumerating packages. A SQL statement was issued and failed.
------------------------------
BUTTONS:
OK
------------------------------
i have two instances: Adventure and instance2 also I added instance name in msdtsrvr.ini but it didn't fix the issue
thank you
The ssis service does not support multiple instances. SSIS will be configured to managed packages on the first instance installed on the machine or the default instance. There is some more information about that here:
https://msdn.microsoft.com/en-us/library/ms137789.aspx
This applies to versions < 2012. 2012 and up support this storage model for backwards compatibility or you could convert to the project deployment model.

Resources