SSIS Excel Connection manager validation is taking forever. The same package works when running Visual Studio in administrator mode. The Excel file I am reading is from a local folder.
I set the Security of both Package and project to "DontSaveSensitive"
After spending almost the whole day, I found out that the TargetServerVersion did not match the target SQL server. Fixing that resolves the issue.
I am trying to connect Excel to my company's Oracle Database. According to the following instructions it should be fairly easy: https://www.wikihow.com/Connect-Excel-to-an-Oracle-Database.
However it has been impossible and quite frustrating so far.
I have followed two different approaches that I've found online.
FIRST APPROACH: installed ODAC from Oracle's Universal Installer
I went to this site https://www.oracle.com/database/technologies/dotnet-odacdev-downloads.html and downloaded the ODAC 12.2.0.1.1 file.
Then, I went through the installation process basically just clicking 'next' on every step.
Note 1: (I don't know if this might be important), in the Database Connection configuration tab I did not fill in any of the information (simply because I didn't know what to put there). It said that if information wasn't filled in, it would not create the TNSNAMES.ORA file.
Note 2: After finishing the installation it says 'run the SQL scripts located in the ... directory after the install'. Which I didn't do, again, because I didn't know how.
After the installation finished a directory was created in the following location: C:\app\client\myUserName\.
The directory goes all the way down to C:\app\client\myUserName\product\12.2.0\client_1, and it contains a bunch of files and folders.
I noticed that no environmental variable was created.
SECOND APPROACH: installed ODBC instant client
I went to this site https://www.oracle.com/database/technologies/instant-client/winx64-64-downloads.html and downloaded both instantclient-basic-windows.x64-19.6.0.0.0dbru.zip and instantclient-odbc-windows.x64-19.6.0.0.0dbru.zip.
Then I created the directory C:\Oracle\instantclient_19_6 and unziped both folders contents into it.
Finally, I ran odbc_install from the command_line, as an administrator, but got Oracle ODBC Driver with same name already exists.
Note: in this case I also noticed that no environmental variable was created.
RESULTS:
When I go to Excel and click on Data\From Database\From Oracle Database I keep getting the same error as before: The recommended provider ('Oracle.DataAccess.Client') is not installed. You can continue with your current provider, however it has been deprecated and may not work properly.".
I was able to solve it by installing the 64 bits version of Oracle's client. Its located at https://www.oracle.com/database/technologies/112010-win64soft.html, file win64_11gR2_client.zip.
Although the message "The recommended provider ('Oracle.DataAccess.Client') is not installed. You can continue with your current provider, however it has been deprecated and may not work properly." remained, I was able to connect after ignoring it.
I have also tried a bunch of approaches and finally got rid of the 'Oracle.DataAccess.Client is not installed' error.
Install Oracle Client for Microsoft Tools:
ODP.NET, Oracle Developer Tools for Visual Studio (Code), and ODAC
https://www.oracle.com/database/technologies/net-downloads.html
Oracle Client for Microsoft Tools installs and configures ODP.NET to support 64-bit Microsoft tool connections with Oracle database. It supports connecting with Power BI Desktop, Power BI service, Excel, SQL Server Analysis Services, SQL Server Data Tools, SQL Server Integration Services, SQL Server Reporting Services, and BizTalk Server.
I have installed Oracle Client for Microsoft Tools 19.17 for (Microsoft Windows x64 (64-bit)) (V1032890-01.exe).
Alternatively, you could follow the learn more link:
Connect Microsoft Tools to Oracle Databases
https://www.oracle.com/database/technologies/appdev/ocmt.html
Tutorials > Power BI Desktop: Connect to Oracle Database
https://www.oracle.com/a/ocom/docs/database/microsoft-powerbi-connection-adw.pdf
I have SSIS package that imports excel data . When I ran the package locally it works but when I deploy it to server I get the following error.
''The requested OLE DB provider Microsoft OLEDB.4.0 is not registered. If the 64 bit driver is not installed run the package in 32 bit mode .''
To solve the problem , I have installed a 64 bit driver access database Engin. I have also changed run 64 bit to false under solution property.
does anyone has a suggestions?
Run64BitRuntime(Default true) under project property is a Visual Studio environment setting, and doesn't apply to packages run outside of BIDS.
If at all you need to run the package with 32 bits outside BIDS, then enable 32 bit runtime under SQL server jobs -> General tab
I'm trying to run a job in SQL Server Management Studio that executes a SSIS package. The SSIS package copies data from an excel file to a database.
I installed the 64-bit version of Microsoft Access Database Engine (https://www.microsoft.com/en-us/download/details.aspx?id=13255). When I tried to run the SSIS package by itself (through Data Tools, not as a job) it displayed an error about ACE.OLEDB not being registered. I got the same error when running the SSIS package as a job.
I uninstalled the 64-bit version and installed it's 32-bit counterpart. It works when I run the SSIS package by itself. When I try to run the package as a job I get the following error:
"The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not
registered. If the 64-bit driver is not installed, run the package in
32-bit mode"
I edit the job step, go to 'execution options' and tick the 'use 32 bit runtime' box. When the box is ticked and I run the job I'm getting the following error:
"An OLE DB error has occurred. Error code: 0x80004005. An OLE DB
record is available. Source: "Microsoft Access Database Engine"
Hresult: 0x80004005 Description: "Unspecified error".
I also tried installing JET.OLEDB instaed of ACE.OLEDB but nothing works. I can run the SSIS package by itself but when I try to run it as a job step in SQL Server Management Studio I always get the two errors mentioned above depending on whether the 32 bit box is ticked or not.
It turns out that the proxy account which was used to run the job didn't have the right permissions.
https://support.microsoft.com/en-us/kb/933835
I'm using CruiseControl.net with Visual SourceSafe and every now and again the build fails with this error:
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: No VSS database (srcsafe.ini) found. Use the SSDIR environment variable or run netsetup.
The documentation says this is due to running the CC.net service as Local System which doesn't have permission to connect to other machines. I am running the service under that user, but the build works 19 times out of 20 so I don't think it's a lack of permissions.
Has anyone else experienced this?
This seems to be related to builds running while I'm not logged into the machine.