I have a SSIS package connecting to Access DB via SSIS package. The package runs fine in my local. But in Server it's failing with the error message class not reqistered for the connection manager. I do not have Access DB engine or Microsoft office component installed in the server. Do i need to install any component to acquire connection successfully?
Related
I install SQL Server Connector for Power Query for SQL server 2017. Create SSDT SSIS package with power query connector. It works perfect in SSDT! But when I deploy project to SSIS catalog, I get an error:
Credentials are required to connect web source.
Package:Error: The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating.
Moreover, when I import this package from SSIS catalog to new project, power query connection manager go away from project with error:
The connection "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" is not found.
This error is thrown by Connections collection when the specific connection element is not found.
Solved!!! In SSDT I used my own login. But in SSIS catalog used SSIS proxy account that don't have access to web.
After granting access to web to SSIS proxy account it works!
If you met same error just try to run SSDT under proxy account and check web access in data source manager :)
When I reference my SSIS Package (containing an OLEDB connection manager) in the SQL Server Agent from the file system, it returns a "Login failed for user 'SYS\SVC.SQL', which is the SQL Agent's service account.
The same package works fine when I deploy it into the SSISDB. The Package is set to "Don´t save sensitive" and SYS\SVC.SQL connects with Windows Authentication.
Where is the difference?
I have created a SIS Log Provider to write a log entry from a Script Task in a SSIS package. The connection is working a long as I use Windows Authentication, but if I switch to SQL Server Authentication and provide a username and a password no log entry is written. I use the same connection in the package to execute a SQL Task to read from the SSIS Log with no problem. The SQL Server User has read and write access to the SSIS Log.
I have to use SQL Server Authentication because the Windows User Running the SSIS Job and the package doesn't have access to SSIS Log and this could not be changed.
I'm using VS SSDT 2017 and deploy the package to SQL Server 2016.
I tried to store the username and password in the package and to provide the connectionstring and password via package parameters and environment.
No effect as soon as I switch from Windows Authentication to SQL Server Authentication.
Dts.Log(logMessage, 0, emptyBytes);
The above code should write an entry in the SSIS Log, but works only for Windows Authentication.
Edit:
The SSIS Log Provider Type is SSIS log provider for SQL Server.
The connection manager type is OLEDB, the provider type is Native OLE DB/SQL Server Native Client 11.0.
The connection is parameterized for the connection string and the password.
I have a SSIS Package with an OData Source Connection to a SharePoint List. To connect to the list, I have a Service Account, which I add as Basic Authentification in the OData Source Task. With this Credentials I can connect to SP and can choose the collection (also preview of the list).
When I now execute the Package (in VS or from Management Studio) the package always fails with the error Message "Cannot acquire a managed connection from the run-time connection manager".
In Management Studio I run the Package with the Service Account User.
Does everybody know whats my problem here ?
I am using SQL Server 2016.
I am trying to obtain access to SQL Server Native Client OLE DB provider using :
hr = CoCreateInstance(CLSID_SQLNCLI11, NULL, CLSCTX_INPROC_SERVER, IID_IDBInitialize,
(void **) &PIDBInitialize);
and this fails with 80040154 error.
I am using sqlserver 2012 and everything worked perfectly fine as long as my application was running on the same machine as sql server was installed but now that the app is deployed in a different environment in which the app runs on a separate server than the server which has the database and sql server I am failing with this error even though the sql server version on the target server is same as mine.
Any ideas why would this behave in such way?
I appriciate your response.
Thats REGDB_E_CLASSNOTREG so CLSID_SQLNCLI11 is not available, download and install the redistributable package for the Native Client (Matching the bitness of your application).
Download.