SSIS error

Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x00000001
Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
When I re-ran the package it worked fine. Any idea why it failed the first time?
Anonymous

Hi DevCoder,
Have you solved this issue? What's the version of your SQL Server 2012? I would suggest you install the latest Service Pack or CU for SQL Server 2012 to see if this issue still persists.
In addition, please also add "Format=Tabular" in the OLE DB connection string. Here is the sample:
Data Source=localhost;Initial Catalog=AdventureWorksDW;Provider=MSOLAP.5;Format=Tabular;Integrated Security=SSPI;
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Similar Messages

Fetching SSIS error message into Audit table using SP

Hi Experts,
I want to fetch SSIS Error Info along with Task Name into Audit table 'Error_Info' column. This is nvarchar(max) datatype, i wrote below Stored Procedure for this (Column names passing dynamically in SP)
CREATE PROC [dbo].[usp_AuditErrorHandler]
@AuditTableName nvarchar(MAX)
,@Audit_Status nvarchar(100)
,@Audit_ErrorDescription sql_variant
,@Audit_PkgEnd_dttm nvarchar(100)
,@task sql_variant
,@errordescription sql_variant
,@Audit_ID nvarchar(10)
,@LogID INT
AS
BEGIN
DECLARE @STRQuery NVARCHAR(MAX)
SET @STRQuery = '
UPDATE '+@AuditTableName+'
SET '+@Audit_Status+' = ''Failed''
,'+@Audit_PkgEnd_dttm+' = GETDATE()
,'+@Audit_ErrorDescription+' = ''Task['+ @task +']:'+@errordescription +'''
WHERE ' +@Audit_ID+ ' = ' + CAST(@LogID AS NVARCHAR)
The above procedure is working fine in SSMS and inserting complete error info into table, but when i am executing thru SSIS Pkg i am getting error like
"[Execute SQL Task] Error: Executing the query "exec usp_AuditErrorHandler ?,?,?,?,?,?,?,?" failed with the following error: "Incorrect syntax near '@P1'.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not established correctly."
So, i tot of checking with string lenght and modifed the code by adding left () to @errordescription as below.
UPDATE '+@AuditTableName+'
SET '+@Audit_Status+' = ''Failed''
,'+@Audit_PkgEnd_dttm+' = GETDATE()
,'+@Audit_ErrorDescription+' = ''Task['+ @task +']:'+LEFT(@errordescription ,100)+'''
WHERE ' +@Audit_ID+ ' = ' + CAST(@LogID AS NVARCHAR)
Here, it is inserting till 119 chars, if i give more than 119 chars pkg is failing with above error.
I want to get insert Complete error info into the column.
Can anybody suggest on this??
Thanks in advance !!!

Thanks Arthur for the response, i have tried with the Sql_Variant data type also, here procedure itself not creating and throwing below error.
"The data types nvarchar(max) and sql_variant are incompatible in the add operator."
This is the procedure i am using to fetch error info into Audit table.
ALTER PROC [dbo].[usp_AuditErrorHandler]
@AuditTableName nvarchar(MAX)
,@Audit_Status nvarchar(100)
,@Audit_PkgEnd_dttm nvarchar(100)
,@Audit_Task_ErrorCode nvarchar(100)
,@Audit_ErrorDescription SQL_VARIANT
,@errorcode nvarchar(max)
,@task SQL_VARIANT
,@errordescription SQL_VARIANT
,@Audit_ID nvarchar(10)
,@LogID INT
AS
BEGIN
SET NOCOUNT ON;
DECLARE @STRQuery SQL_VARIANT
BEGIN TRY
SET @STRQuery = '
UPDATE '+@AuditTableName+'
SET '+@Audit_Status+' = ''Failed''
,'+@Audit_PkgEnd_dttm+' = GETDATE()
,'+@Audit_Task_ErrorCode+' = '''+@errorcode+'''
,'+@Audit_ErrorDescription+' = ''Task['+ @task +']:'+ @errordescription +'''
(Error is giving in this line)
WHERE ' +@Audit_ID+ ' = ' + CAST(@LogID AS NVARCHAR)
EXEC (@STRQuery)
END TRY
Below is the Audit Table Schema

SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

Hi,
This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
So far I have installed
http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
2012 release.
Here is the detail of error message:
TITLE: Package Validation Error
Package Validation Error
ADDITIONAL INFORMATION:
Error at Data Flow Task [Excel Source [2]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection
Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
Error at Data Flow Task: There were errors during task validation.
Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR. 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".
(Microsoft.DataTransformationServices.VsIntegration)
Here are my environment details:
SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
Services Project2\Integration Services Project2\Package.dtsx.
Does this kind of Shared drives have any impact to give this issue?
Thanks in advance!
Ketan
P.S.: I had look at this forum question -->
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

Hi Arthur,
Thanks for your response.
Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
1) Some times excel source files cannot be parsed by excel source connection manager.
2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage while destination mapping.
3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file. <-- For
this we tried IMEX setting also
4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
Do you think it is advisable to convert Excel into CSV or Flat file.
Thanks,
Ketan

EXCEL TO SQL USING SSIS Error

I have an .XLSLX File. I have a DFD Task to export that xlsx file into SQL. I use SSIS 2008. However when I run the package, it fails with this error below.
[Connection manager "Excel Connection Manager"] Error: SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available.

Hi Desigal59,
The BIDS is a 32-bit software, therefore, only 32-bit providers are visible in the IS design GUI. So, you need the 32-bit Microsoft ACE OLE DB Provider to be installed on your local machine to create the package (using OLE DB Source instead of Excel Source
in the Data Flow Task). If 32-bit Office 2007 or higher is installed on your local machine, the 32-bit Microsoft ACE OLE DB drivers have been installed already, otherwise, you need to install the 32-bit Microsoft Access Database Engine 2010 Redistributable.
To run the package in 64-bit runtime mode, you need the 64-bit Microsoft ACE OLE DB Provider. However, the 32-bit and 64-bit Microsoft Access Database Engine Redistributable cannot be installed side by side on a single server. So, if you have 32-bit Office
installed on your local server, you can install the 64-bit Microsoft Access Database Engine 2010 Redistributable and run the package in 64-bit runtime mode in BIDS by setting the Run64BitRuntime property to True. If 32-bit Office is not installed, you have
to install only the 32-bit
Microsoft Access Database Engine 2010 Redistributable and cannot run the package in 64-bit runtime mode in BIDS.
After deploying the package to the SSIS server, if you want it to run in 64-bit runtime mode, you only need to make sure the 64-bit Microsoft ACE OLE DB drivers are installed and the 32-bit drivers are not necessary.
Another way to create the package is use the 64-bit SQL Server Import and Export Wizard in which the 64-bit Microsoft ACE OLE DB Provider is available. Then, you can save it as a package to the file system from the SQL Server Import and Export Wizard. In this
way, you don’t need the 32-bit Microsoft ACE OLE DB drivers to develop the package. When you open the package in BIDS, you may encounter errors or the OLE DB Connection Manager works offline, but you can ignore the error and run the package successfully only
if you have 64-bit ACE OLE DB drivers installed on your computer.
Regards,
Mike Yin
TechNet Community Support

[Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messa

Error
[Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There
may be error message
I am using BIDS Microsoft Visual Studio 2008 and running the package to load the data from excel .
My machine has 32 bit excel hence have set property to RUN64BITRUNTIME AS FALSE.
But the error still occurs .
I checked on Google and many have used Delay validation property at Data flow task level to true but even using it at both excel connection manager and DFT level it doesnt work
Mudassar

Thats my connection string
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\SrcData\Feeds\Utilization.xlsx;Extended Properties="Excel 12.0;HDR=NO";
Excel 2010 installed and its 32 bit edition
Are you referring to install this component -AccessDatabaseEngine_x64.exe?
http://www.microsoft.com/en-us/download/details.aspx?id=13255
Mudassar
You can try an OLEDB provider in that case
see
http://dataintegrity.wordpress.com/2009/10/16/xlsx/
you might need to download and install ms access redistributable
http://www.microsoft.com/en-in/download/details.aspx?id=13255
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Package Validation Error - SSIS Error Code DTS_E_OLEDBERROR - Error code: 0x80040E4D

I sometimes get the following error randomly -
Package Validation Error
ADDITIONAL INFORMATION:
Error at MY_PACKAGE_PLUS[Connection manager "MY_DATABASE"]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'USERNAMEZ'.".
Error at MY_PACKAGE_PLUS [Log provider "SSIS log provider for SQL Server"]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "MY_DATABASE" failed with error
code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
(Microsoft.DataTransformationServices.VsIntegration)
My package name in SSIS/BIDS is MY_PACKAGE, but in the error I see MY_PACKAGE_PLUS, which was the name of an older version of the package. This error goes away when I close SSIS and then restart it. I wonder why this happens and how do I fix it
? Is this some bug in SSIS ? The same package runs without errors in SQL server agent.
Thanks.

It seems the old package reference still exists in your project bin folder or inside stproj file. WHich is why it tries to validate the older package each time when you start the project.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER

Hi Experts,
I have a package to import data from Excel to SQL tables. I have created and depolyed the package on production server say "ProdServer".
Also I have created job on the same server and it runinng the package successfully. Even I run it manually it is running properly. But
problem here is when I am connecting to SQL installed on the production server from my local machine using windows authentication and trying
to run the package manually it gives below error.
Executed as user: SERVERNAME\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Microsoft Corporation 2010. All rights reserved. Started: 7:41:10 AM Error: 2014-07-15
07:41:17.24 Code: 0xC0202009 Source: ImportMasterData Connection manager "PracticeMapping" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error
code: 0x80004005. End Error Error: 2014-07-15 07:41:17.27 Code: 0xC020801C Source: Load Practice Get Practice [69] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection
manager "PracticeMapping" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-07-15
07:41:17.29 Code: 0xC004701A Source: Load Practice SSIS.Pipeline Description: component "Get Practice" (69) failed the pre-execute phase and returned error code 0xC020801C. End
Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 7:41:10 AM Finished: 7:41:17 AM Elapsed: 6.692 seconds. The package execution failed. The step failed.
So in short when I run the packgae direclty from production server it works fine but from local machine or any other machine by connecting
to the SSMS and running manually, it get failed. Please help me guys on this issue. Its very very urgent.
Thanks and Best Regards,
Mangesh

SERVERNAME\SYSTEM account has no proper rights.
Typically a proxy is needed to run SSIS jobs. See how to here
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Arthur My Blog

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005 Description: "Internal error: An une

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005
Description: "Internal error: An unexpected error occurred (file 'pcxmlacommon.cpp', line 43, function 'PCFault::RaiseError').
I'm getting above error in the pre- execute phase of a DFT when I'm trying to fetch data from a SSAS cube using mdx query.
I'm using OLE DB provider for connecting to cube.
I got one resolution for Error Code 0X8004005, which asked me to add 'Format= Tabular' in cube's connection string. It does not seem to work either. Can any one help me out on this???

You are probably missing an update.
I saw a MS Connect post https://connect.microsoft.com/SQLServer/feedback/details/250920/error-using-oledb-or-datareader-to-get-analysis-services-data where that suggestion was proposed as a fix, but is for an older SQL Server version.
So do there is a question if you pull data from SQL Server 2012 SSAS using SSIS 2012 (so no other build is involved).
Arthur My Blog

SSIS Error Text was truncated or one or more characters had no match in the target code page

I the same issue or something close.
Except I have one Field (27) that get a trunacation error
Error:
Data conversion failed. The data conversion for column "Column 27" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
The "output column "Column 27" (91)" failed because truncation occurred, and the truncation row disposition on "output column "Column 27" (91)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
Data looks like:Red Text is the field that is throwing the error!
00000412,
0000000011411001,
0273508793,
01,
"RUTH           ",
"EDWARDS             ",
19500415,20080401,
"N",
04488013,
"1",
"F",
365094,
20080401,
000472162716,
"1447203880    ",
43995202341210,
00120.000,
0010,
00008.26,
00004.96,
000.00,
00002.70,
00007.66,
0,
"PROMETH/COD SYP 6.25-10 ",
"Y",
"Promethazine w/ Codeine Syrup 6.25-10 MG/5ML               ",
0000,
"001C",
610020,"WELLP1537",
"O",
"N",
00,
"D",
"S",
"G",
"ID01V012008782",
"TOM AHL CHRYSLER              ",
"M",
"M",
"PBD $20/10+40%/20%            ",
00008.26,
"1184641367"

I have found four things that I always check when I run into this problem. I have yet to find a time when one of these didn't work (specifically helps when reading data from flat files but I suppose most of the four would apply to any source). Check out my blog post, content repeated below:
1. Make sure to properly configure the "Flat File Source". When setting the connection properties to the flat file, take time to click on the advanced tab and ensure that the" Name", "DataType", and "OutputColumnWidth" properties are set properly. I have found that if this is setup correctly when the initial connection is created, some if not all of the data type issues and errors can be alleviated. The "Flat File Connection Manager Editor" can be accessed while initially creating the connection or by double clicking on a flat file connection within the "Connection Managers" for connections that have previously been created.
2. Depending on the order and steps that were used to create the connection to the flat file, sometimes the data types need to be updated in an additional area. This can be found by right clicking on the "Flat File Source" and selecting "Show Advanced Editor...". Once in the advanced editor, click on the "Input and Output Properties" tab. Expand the "External Columns" folder. For each field being loaded from the flat file there are some configurable properties. Make sure that the "DataType" field is properly set for each field.
3. Something else that can be done if you are sure that the data type is set correctly in both of the two previously mentioned locations is to set the "Flat File Source" to essentially ignore those annoying truncation errors. On the same "Input and Output Properties" tab, expand the "Output Columns" folder. For those fields listed, there is a "TruncationRowDisposition" property. By default this is set to "RD_FailComponent". This can be switched to "RD_IgnoreFailure" in order to allow the data to successfully pass through the "Flat File Source" even if SSIS believes that truncation is going to occur. Along with making this change, you can also check the "DataType" in the "Output Columns" as well.
Caution: If you do set the "Flat File Source" to "RD_IgnoreFailure" as mentioned above, always take time to review the data loaded in the target table to ensure that the integrity of the data was not jeopardized.
Note: I have found that when the "DataType" for both the "External Columns" and "Output Columns" is manually updated that it does not remain the same when the advanced editor is reopened. For this reason, try Steps 1 and 2 before setting the "Output Columns" manually.
4. The last thing to try, and this applies specifically to loading data from Excel files as opposed to text or CSV is to set the package to run in 32-bit mode. Click on "Project" on the top menu and select "Data Imports Properties...". Click on "Debugging" under the "Configuration Properties" and set the "Run64BitRuntime" to "False".
Working with data from flat files can sometimes be difficult in SSIS. By using one or many of the approaches I have listed above you should be able to create a repeatable process that is frequently needed within most SSIS packages. Be very careful when setting data types within SSIS and make sure to do it upfront when necessary because it can be harder to debug later in the development process. If the proper changes are made it should not be a surprise to feel a big SSIS developer sense of relief when the screen shows all green.
Let me know if this works!
Check out my blog!

Fetch SSIS error through SQL Server Agent JOB

Hi,
I am trying to fetch eventmessages from catalog.eventmessages view in SSISDB inside a sql job which executes a package. This utility is supposed to send an email with the description of failure reason and step whenever the JOB fails. But I could not find
a way to reference a package in SSISDB with the corresponding JOB through SQL query.
sysjobsteps stores the step info, but how can I refer to the SSIS package using the info from this table or any other table. Please provide an expert view for this problem.
Regards
Mohit

sysjobsteps stores the step info, but how can I refer to the SSIS package using the info from this
table or any other table
Can you try like this?
SELECT e.package_name,e.message
FROM msdb.dbo.sysjobsteps js
inner join SSISDB.catalog.event_messages e
On js.command collate database_default like'%\' + e.package_name collate database_default + '%'
--WHERE e.event_name ='OnError'
Uncomment the WHERE clause if you want to specifically look for errors
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

The ForEach Loop Enumerator is Empty - SSIS Error when executing through CMD via VBA

I am currently working on a SSIS package that is to be triggered through CMD via VBA (Access). All that the package does is read a bunch of files from a folder and upload them into a table in SQL Server. The tricky part comes is that this folder location from
which the package is to read the files is dynamic.
I figured out a way to make it dynamic, by using variables
I have used the following variables:
"Directory" against DIRECTORY in COLLECTION>>EXPRESSIONS in the ForEachfile Enumerator,
"FilePath" (With Index 0) in the Variable Mappings
PROBLEM : As the final link in the chain, I have used following to be triggered from VBA
dtexec \f "C:\Desktop\SSISAppend.dtsx" /Set "\Package.Variables[User::Directory].Property[Value];C:\Desktop\AppendFiles"
When I try to execute the package using the above command, it gives out the error
Code : 0x8001C004
Description: The For Each File Enumerator is empty. The For Each File enumerator did not find any files that meatched the file pattern, or the specified directory was empty.
But, when I run the package from MS VisualStudio 2008, the package runs fine, takes the location of the file assigned to the variable "Directory".
All help is appreciated

Where are you executing the package from? You're giving an aboslute path so this will work only if package as well as the folder is in the same machine from which you execute the above code. Otherwise you need to use UNC path.
Another thing to check is what login is executing the command and you need to ensure it does have access to the directoty path as well as to the path where package resides.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS Error Code -1071607778

Hi, I have a lookup in my SSIS package that looks up the data from a database table and matches it with the data from another table. For example Field A in Table 1 with Field B in Table 2, Table 1 is the transactional data and Table 2 contains the value to refer to.
For some reason, I get error code -1071607778 in the output file when the lookup fails, but the values are in both Table 1 and Table 2.
Has anyone encountered this error before and what does error code -1071607778 mean ?
Regards
Ash

I'm surprised you did not get the error description as well. The error event includes a description by default, and the output window or progress window gives full details. The message is "Row yielded no match during lookup."
The point that a match is not found, when you think it should be, still means the data really is not the same. Some notes on how or why this might be - http://wiki.sqlis.com/default.aspx/SQLISWiki/LookUp.html
The lookup is clearly failing to find a match, so you can change the behaviour of this, to ignore or redirect rather than fail if that is better.

Ssis error: hresult e_fail has been returned from a call to a com component

I am using VS 2013 (BIDS) to develop SSIS packages. It is running on a windows 2012 server.
I have a dev server on which when i try to load an SSIS project using the solution file i get a bunch of errors, and then visual studio just closes. The error is:
hresult e_fail has been returned from a call to a com component
If i copy the project to another machine it works fine.
If i open VS first, and then open the project using the proj file, it seems to work.
Any ideas what might be causing this error? I can work for now, but am worried my project may be corrupted in some way so dont want to do too much work on it.

It might be a corruption so a re-install is desired. But
Use SSDT (VS2010 shell) that came with the SQL Server installation media to edit SSIS 2012 packages.
Arthur
MyBlog
Twitter

SSIS error authenticating proxy with SQL Agent

Hello,
I'm a BI Analyst (not DBA) and I've asked our IT department for access to SSIS and SQL Server Agent to deploy packages to import data from Oracle nightly and transform it into a dataset in SQL Server 2012 using SSIS.
I've written several packages, deployed these to a SQL Server. These run fine when ran locally through Object Explorer > Integration Services Catalog > SSIDB by right clicking/execute.
However our DBA has set up an SSIS Proxy that I can use in conjunction with SQL Server Agent to run these packages. However, when I try to use this proxy I get the error message:
'Unable to start execution of step 1 (reason: error authoenticating proxy ad\[name removed], system error. The username or password is incorrect. The step failed.'
I've tried packages with security for 'dontsavesensitive' and 'encryptsensitivewithuserkey' but neither work. I'd like to rule anything out that I'm not doing, however I think it is a permissions issue (happy to be proven wrong though).
Can anyone offer suggestions for next steps please?
Thanks,
ZP

Hi V,
Thanks again.
I went to the general tab and it is all greyed out and the credentials box is empty - though I can click on the button with three dots on. However, it just takes me to a credentials form but doesn't give me any options to select from. The box for SSIS is
ticked though.
It is all greyed out - I presumed this is because I haven't got permissions to set what the proxy can do?
I tried select * from sys.credentials - didn't return any information (zero rows).
I'm (mostly!) convinced the packages are fine - I've created several simple packages to demonstrate the same thing to our DBA and these simple packages all run fine when executed directly through SSMS but never work through SQL Agent with SSIS Proxy. His
thinking is that its because I need to run them with security as 'dontsavesensitive' but these dont work either.
Do you know if I should be asking for a specific permission/credential?
Thanks!

SSIS error working with Server 2012

Hi,
I have a class library that creates, delete, update ssis packages programatically.
What could be the reason for an error message that I get in front of the server 2012. Against a server 2008 It works good.
Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSExecutables100'. This operation failed because the QueryInterface call on the COM component
for the interface with IID '{0FAC005E-5ABD-4D1E-9B21-18F3DE622B24}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
thanks

It looks like your references need to be updated for 2012.
David
David http://blogs.msdn.com/b/dbrowne/

SSIS error

Similar Messages

Maybe you are looking for