This project is read-only.

2014 executable has WER fault


When I download and run the 2014 executable, it produces a WER fault -- I can see it appear in the task list (using Process Explorer) but it immediately shows a WERFault icon and then disappears.


IronRod wrote Nov 3, 2015 at 11:57 PM

I downloaded the source in an attempt to figure out what is going on. Here's what I did:

(I have VS 2013 and SQL Server 2014 installed, along with the SSDTBI for VS2013.)

I'm running VS2013, so it required the conversion from the 2012 solution. No functional changes.
The three references were all icon'd with warnings. I located them in the respective locations and added the references.
Had to change the target .NET of the project to 4.0 since that is the level of the three libraries.

Still getting a warning about DTSRuntimeWrap being a different architecture that the project architecture (full message at bottom). Looking into this...

Warning 1 There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWrap, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. RAW File Viewer

strigona wrote Dec 5, 2015 at 7:44 AM

Hi, sorry for the delays.. I don't check this email account very often. I recently switched jobs and am no longer working with SSIS or RAW files. I have VS 2015 & SQL Server 2014 at work and will try building at some point in the near future.

Were you looking at the 2014 branch or master? My initial thought is that the reference to DTSRuntimeWrap should be updated to a newer version.. likely 12.

There are some details about errors between 2008 & 2012 here that may be applicable when tracking down the issue:

IronRod wrote Mar 16, 2016 at 6:18 PM

I have found that the issue is that the attempt to execute the temporary package fails. I can see the temp dtsx is created in my temp folder. But when it reaches the line use DtsCommand.ExecuteReader() it returns an exception "Package failed to execute".

I assume this is some kind of strange permission issue. Attempts to open the temp package in the "Execute Package Utility" aren't helpful. When I click [Execute], it runs but then fails with errors:

Error: To run a SSIS package outside of SQL Server Data Tools you must install DataReaderDest of Integration Services or higher.
Error: To run a SSIS Package outside of SQL Server Data Tools you must install Raw File Source of Integration services or higher.

Of course, "DataReaderDest" and "Raw File Source" are the names of the two components in the package. I assume the install "Integration Services or higher" means that, because I'm attempting to run the Execute Package Utility on my local system, which does not have Integration Services installed (only Data Tools), that the utility cannot execute the package. Thus, I think these errors aren't meaningful for the main problem of why code is unable to execute the temporary package.

strigona wrote Mar 16, 2016 at 7:30 PM

Hmm.. not too sure what to say. I'm in a different line of work these days and don't work with SSIS anymore so I don't have an environment setup at the moment to build and test.