I have created a new Integration Services Project in Visual Studio 2015. I have added a package with a Data Flow Task. In this task I have added the ADO.NET Source component with a simple SQL query as the command. In the Expressions editor of the Data Flow Task I have added an expression for the [ADO NET Source].[SqlCommand] property with (currently) the same SQL query. This SSIS package runs successfully.
Now, when I rename the ADO.NET Source component in the Data Flow Task and want to save the package, Visual Studio crashes. The following information is logged in the Event Log:
1st Event
Source: .Net Runtime
Message:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPackagePersist100.SavePackageToXML(System.Object ByRef, Boolean, Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSEvents100)
at Microsoft.SqlServer.Dts.Runtime.Package.SaveToXML(System.String ByRef, Microsoft.SqlServer.Dts.Runtime.IDTSEvents)
at Microsoft.DataTransformationServices.Design.Serialization.DtrDesignerSerializer.SerializePackage(System.ComponentModel.Design.Serialization.IDesignerSerializationManager, Microsoft.SqlServer.Dts.Runtime.Package, System.IO.TextWriter)
at Microsoft.DataTransformationServices.Design.Serialization.DtrDesignerSerializer.SerializeComponent(System.ComponentModel.Design.Serialization.IDesignerSerializationManager, System.ComponentModel.IComponent, System.Object)
at Microsoft.DataWarehouse.Serialization.DesignerComponentSerializer.Serialize(System.ComponentModel.Design.Serialization.IDesignerSerializationManager, System.Object)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseDesignerLoader.Serialize()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush(Boolean)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseContainerManager.OnBeforeSave(UInt32)
2nd Event
Source: Application Error
Message:
Faulting application name: devenv.exe, version: 14.0.25420.1, time stamp: 0x57685d85
Faulting module name: DTS.dll, version: 2017.140.800.90, time stamp: 0x5964da54
Exception code: 0xc0000005
Fault offset: 0x00070c07
Faulting process id: 0x1660
Faulting application start time: 0x01d3c4ee248a88f4
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\DTS.dll
Report Id: 9b9d1a33-4974-480f-a6b0-91bf7658045f
Faulting package full name:
Faulting package-relative application ID:
Check this video on YouTube
Does anybody have an idea on solving this problem?
Thanks,
Danny
Related
I have created a desktop application in visual studio and sqlserver and when I created a setup, it is working on the development machine but when the setup is installed in the client machine together with crystal reports runtime engine, the application is not starting. I have implemented event logging and managed to get the following error for crystal reports.
Application: Crystals.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.BadImageFormatException
at CrystalDecisions.Shared.SharedUtils..cctor()
Exception Info: System.TypeInitializationException
at CrystalDecisions.Shared.SharedUtils.get_CurrentControl()
at CrystalDecisions.Shared.SharedUtils.GetEffectiveCulture()
at CrystalDecisions.Shared.LocaleManager..ctor()
at CrystalDecisions.Windows.Forms.CrystalReportViewer.InitReportViewer()
at CrystalDecisions.Windows.Forms.CrystalReportViewer..ctor()
at Crystals.Form1.InitializeComponent()
at Crystals.Form1..ctor()
Exception Info: System.InvalidOperationException
at Crystals.My.MyProject+MyForms.Create__Instance__[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon)
at Crystals.My.MyProject+MyForms.get_Form1()
at Crystals.My.MyApplication.OnCreateMainForm()
at Microsoft.VisualBasic.ApplicationServices
I have also tried Microsoft Report Viewer RDLC and it is returning the following error
Faulting Application name:ReportViewerSample.exe,version:1.0.0.0, time stamp:0x6130af2a
Faulting module name:KERNELBASE.dll,version:10.0.10240.16384, time stamp:0x559f3b2a
Exception code:0xe0434352
Fault offset:0x000b3e28
Faulting process id:0x17b4
Faulting application start time:0x01d7a059329df75d
Faulting application path: C:\Program Files(x86)\Beymo\RDLCViewer\ReportViewerSample.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report id: 57ed1ef9-6ed3-418f-952a-aea23f09618b
Faulting package full name:
Faulting package-relative application ID:
Log Name: Application
Source: Application error
Event ID: 100
When I create a project without a report, it is working fine in both development environment and client machine. How can I resolve the issue?
Earlier today I was attempting to import data in a local SQL Server instance using the built-in SQL Server Import and Export Wizard [DTSWizard.exe] which I've recently done many times. Today was not one of them. Immediately after clicking the initial 'Next' where the Source Data Sources are enumerated, DTSWizard.exe crashes immediately. Luckily, it does generate Application Events in Event Viewer.
Application: DTSWizard.exe Framework Version: v4.0.30319 Description:
The process was terminated due to an internal error in the .NET
Runtime at IP 745B1AB3 (74590000) with exit code 80131506.
Faulting application name: DTSWizard.exe, version: 15.0.2000.168, time
stamp: 0x60d2af25 Faulting module name: clr.dll, version: 4.8.4400.0,
time stamp: 0x60b90414 Exception code: 0xc0000005 Fault offset:
0x00021ab3 Faulting process id: 0x2644 Faulting application start
time: 0x01d798859bcd5141 Faulting application path: C:\Program Files
(x86)\Microsoft SQL Server Management Studio
18\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn\DTSWizard.exe
Faulting module path:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id:
f299f3ae-8e51-4bf8-a4b0-33bee2d36804 Faulting package full name:
Faulting package-relative application ID:
Fault bucket 1468275927648085676, type 1 Event Name: APPCRASH
Response: Not available Cab Id: 0
Problem signature: P1: DTSWizard.exe P2: 15.0.2000.168 P3: 60d2af25
P4: clr.dll P5: 4.8.4400.0 P6: 60b90414 P7: c0000005 P8: 00021ab3 P9:
P10:
Attached files:
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF2CF.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF438.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF448.tmp.xml
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF446.tmp.csv
C:\ProgramData\Microsoft\Windows\WER\Temp\WERF467.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DTSWizard.exe_9a495bf0850f18fc52df16157df1d27143632_d6e9ae04_912b0408-c4d8-4634-820f-fde40457c5a6
Analysis symbol: Rechecking for solution: 0 Report Id:
f299f3ae-8e51-4bf8-a4b0-33bee2d36804 Report Status: 268435456 Hashed
bucket: 99ad5a02b5c660c124605d2d4bb8a6ac CabGuid: 0
I'm using the latest version of SQL Server Management Studio, build 15.0.18386.0, which I did reinstall but with no change. Other things which I have tried is apply all cumulative updates for .NET Framework 4.8, which brought clr.dll to file version 4.8.4400.0, timestamped 6/3/2021 1:25PM. I have also tried the .NET Framework Repair Tool which didn't seem to make a difference. Based on Windows Update, there seem to have been no recently applied hotfixes, patches, etc. between now and last week which is the time of the last successful import.
In my expierence, this could be related to anti-virus/anti-malware software. You might need to whitelist the software.
I am using:
And everything works fine, I can even see reports performance:
But when I hit 'new query', I get this, and SSMS restarts automatically:
Most of what I have to do is on the query window, so this is quite irritating
error:
Faulting application name: Ssms.exe, version: 2017.140.17230.0, time stamp: 0x5aa77b02
Faulting module name: WindowsBase.ni.dll, version: 4.7.2558.0, time stamp: 0x59d41ae3
Exception code: 0x80131623
Fault offset: 0x002809a3
Faulting process id: 0x3ddc
Faulting application start time: 0x01d3d894161c96fd
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\WindowsBase\d9eac8ec5a604324b2ad7792cf8d8ed4\WindowsBase.ni.dll
Report Id: 9889b185-67cd-4cb4-928f-d89b5801d2f3
Faulting package full name:
Faulting package-relative application ID:
Application: Ssms.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.
Message: Unrecoverable system error.
Stack at System.Environment.FailFast
at MS.Internal.Invarian
Right click on the database giving you the problem in the object explorer.
Click ‘Properties’
Click ‘Options’
Set ‘Auto Close’ to False
I have a build script which starts Visual Studio from a command line as follows:
devenv.exe <project file> /Rebuild "Release" /Project <project name> /UseEnv /Out <log file>
On completion the script checks the exit code from Visual Studio.
We have updated from Visual Studio 2010 to 2015. Most of the projects compile without problems, but some exit with the code 0xE0434352, which I believe is System.InvalidOperationException.
The windows event log shows two entries:
Faulting application name: devenv.exe, version: 14.0.24720.0, time stamp: 0x564ea97e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.19045, time stamp: 0x56258f05
Exception code: 0xe0434352
Fault offset: 0x0000c42d
Faulting process id: 0xb64
Faulting application start time: 0x01d131c68bdc0db0
Faulting application path: c:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: cb600c61-9db9-11e5-abfc-005056c00008
and
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Windows.Forms.Control.MarshaledInvoke(System.Windows.Forms.Control, System.Delegate, System.Object[], Boolean)
at System.Windows.Forms.Control.BeginInvoke(System.Delegate, System.Object[])
at System.Windows.Forms.WindowsFormsSynchronizationContext.Post(System.Threading.SendOrPostCallback, System.Object)
at System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation.PostAction(System.Object)
at System.Threading.Tasks.AwaitTaskContinuation.RunCallback(System.Threading.ContextCallback, System.Object, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.AwaitTaskContinuation+<>c.<ThrowAsyncIfNecessary>b__18_0(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
The projects are VB and C# Windows Forms projects. It is not happening with C++ projects.
So far as I can tell, the components are always built correctly and the exception occurs on closing visual studio. I have modified our script to ignore this specific error, but that doesn't seem like a great solution.
Can anybody suggest how to fix this problem?
If that are all normal projects you build you don't need devenv to do that work for you.
Simply use msbuild.
I think this commandline should get you started:
msbuild /t:Build /p:Configuration=Release [your .sln or .csproj or .vbproj]
Which instructs msbuild to process the Build target and set the Property named Configuration to Release
Notice how you can either msbuild the complete solution or single projects this way. The only exception is for projecttypes that are only known to Visual Studio and not to msbuild. For earlier versions of VS that was true for the Setup projecttype. You couldn't build that one without running devenv.
My app was built on .NET 4.0 with WPF, Prism, Entity Framework
There are 1 exe (the app), 1 exe (the app config - simple app to restore db, no referenced dll no prism and no EF), and several referenced DLLs like the prism-way, SQL Server 2008 Express. All assemblies and Exe are built with target platform AnyCpu.
I tested in my development environment(Win764bits, VS2010, .NET4...), no problem. Then I tested in Windows 7 32 bits and the app config works well. But the app runs perfectly only if the Visual Studio is installed. Without VS 2010, I got the 2 errors in event log:
Application Error:
Faulting application name: App.exe, version: 1.0.0.0, time stamp: 0x4df473d0
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdaae
Exception code: 0xe0434352
Fault offset: 0x00009617
Faulting process id: 0xa28
Faulting application start time: 0x01cc2aa91326a10e
Faulting application path: C:......\Release\App.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 52f2c510-969c-11e0-98bf-000c299e51f4
.NET Runtime:
Application: App.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Practices.Prism.Modularity.ModuleInitializeException
Stack:
at Microsoft.Practices.Prism.Modularity.ModuleInitializer.HandleModuleInitializationError(Microsoft.Practices.Prism.Modularity.ModuleInfo, System.String, System.Exception)
at Microsoft.Practices.Prism.Modularity.ModuleInitializer.Initialize(Microsoft.Practices.Prism.Modularity.ModuleInfo)
at Microsoft.Practices.Prism.Modularity.ModuleManager.LoadModulesThatAreReadyForLoad()
at Microsoft.Practices.Prism.Modularity.ModuleManager.LoadModuleTypes(System.Collections.Generic.IEnumerable`1)
at Microsoft.Practices.Prism.Modularity.ModuleManager.LoadModulesWhenAvailable()
at Microsoft.Practices.Prism.Modularity.ModuleManager.Run()
at ...
I've searched and tried to fix, but It's the same.
Please help me
Many thanks and regards!
I've found that one of my DLL using ReportViewer. Just installed this one and the problem was resolved
http://www.microsoft.com/download/en/confirmation.aspx?id=6442