Currently, I'm expressing an error when I'm trying to work in Excel as OLE Db data source. The error from the event viewer is as follows:
Faulting application name: devenv.exe, version: 14.0.25420.1, time stamp: 0x57685d85
Faulting module name: mso40uiwin32client.dll, version: 16.0.4510.1001, time stamp: 0x58aea30f
Exception code: 0xc0000005
Fault offset: 0x001665c1
Faulting process id: 0x1634
Faulting application start time: 0x01d2a4d1d4ef28d1
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso40uiwin32client.dll
Report Id: c15c623e-10c5-11e7-81d4-782bcbacd899
What I'm trying to do: loading data from the excel file and put in sql database. When I create my package at the first time everything work ok, but when I closed and reopen my project I have VS crashing due to the error I reported from the event viewer.
From the error of the event viewer, I had the idea to uninstall office, install only ACE and try again to reopen and work in my project. The project worked again.
My understanding now, is that we cannot have office installed when we want to work with excel as OLE DB Source. Is this true?
Can any one help me to overcome this error? I want to have Excel and be able to work in my SSIS project in the same machine
Thank you
You have to ensure:
The version of the driver (Microsoft Jet /ACE) support the version of the excel you are trying to load.
You can load and preview the Excel in the dataflow in a excel component, and see the info you are looking for.
Sometimes the problem is that your driver is for 32bits and ssis runs on 64bits, you can change this from project to 32bits. I think this is the most important check and your fail could be this.
Check the security of the file, ensure that you can access it and the user you are running ssis have permission.
put here the result of the execution of the package, to read more about the error.
After a lot of install/uninstall SSDT2012.
We found that we are able to overcome the conflict issue when installing the SSDT2012 from this location:
https://msdn.microsoft.com/en-us/jj650015
I cannot explain why this version can resolve the issue, but what I understand that with this newer version of SSDT2012 we have several enhancement like creating database project in 2012, using sql server 2014 without any trouble, ...
Related
How could I read an Excel file with SSDT-Visual Studio 2019 under Windows Server 2016 64-bit ?
I see there are a lot of blogs describing similar issue but I'm still not able to solve my problem.
I would like to read an Excel file within my Visual Studio 2019 (SSDT Toolbox) under our Windows Server 2016 64-bit.
At first attempt (during the development) I got this error message "The requested OLE DB provider Microsoft.ACE.OLEDB.16.0 is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode."
Ok, I understand VS 2019 is a 32-bit app so it, by default, tries to use 32-bit driver.
Through multiple tests I tried the actions below but none of them have solved the issue :
set the Run64BitRunTime as True
set the "Processor Architecture for AnyCPU Projects" as x64
It seems modifying those settings would apply only at RunTime level i.e at the compiled version of the package, not during the development.
When I use SQL Server Import and Export Data Wizard 64-bit (and save the SSIS Package) it do works BUT it does not help reaching 100% of my goal. The reason I use SSIS is to do complex ETL , not only reading an Excel file. Reading such file is only a small part of the process (otherwise SSIS would be quite underutilized)
The biggest constraints I currently have are:
As per company restrictions, we could not install 32-bit driver on that machine
I know Visual Studio 2022 would be 64-bit but unfortunately, at this time (October 2022), it does not have SSIS module yet
Could anyone help me to solve this?
Any helps or tips would be appreciated.
My environment:
Windows Server 2016 64-bit
SQL Server 2019 with SSIS module installed
Visual Studio 2019 with SSDT module installed
We are running Microsoft Azure Backup Server (MABS) v3 on Windows Server 2019. Since Monday evening the cloud and bare-metal backups started failing, but other on-premises backups are running fine.
Looking through Event Viewer we found an application error which might assist in resolving the issue, but I haven't been able to find much info online:
Faulting application name: cbengine.exe, version: 2.0.9177.0, time stamp: 0x5e677965
Faulting module name: LKRhDPM.DLL, version: 2.0.9177.0, time stamp: 0x5e6778b2
Exception code: 0xc0000005
Fault offset: 0x0000000000005e3f
Faulting process id: 0x1984
Faulting application start time: 0x01d62470ae5f7af9
Faulting application path: C:\Program Files\Microsoft Azure Backup Server\DPM\MARS\Microsoft Azure Recovery Services Agent\Microsoft Azure Recovery Services Agent\bin\cbengine.exe
Faulting module path: C:\Program Files\Microsoft Azure Backup Server\DPM\MARS\Microsoft Azure Recovery Services Agent\Microsoft Azure Recovery Services Agent\bin\LKRhDPM.DLL
Report Id: b57ddf2b-4948-4f68-b572-e58f9031db9b
Faulting package full name:
Faulting package-relative application ID:
The application is on the most recent version and I also updated and repaired all the Visuall C++ components as well as .NET frameworks.
The OS also has the March updates installed.
Please let me know if you need more details.
I'm not exactly sure why, but the cause of the issues was the latest version of Sysinternals' Sysmon, version 11.0.
This also caused another issue where Office documents would take long to open or save from and to network locations, even when the client had a gigabit connection to the server.
Rolling back to Sysmon version 10.42 resolved all of the issues.
You can also try upgrading to the latest version of Sysmon (12.02). They corrected this issue there.
We have a legacy windows desktop client application that calls a Load Balancer (running in Windows Server 2003) that delegates the request to an Application Server (Windows Server 2003) that connects to an SQL Server (Windows 2008 R2 Database server). This desktop application has been running well since Windows XP to Windows 8.1; however, on Windows 10, it unpredictably crashes with the following error message displayed on the end user's Windows 10 machine:
Client Decompression System ERROR! ...Header sum error
in Function Name... GetServerDataToBuffer
Calling Process... LSD_Decompress (or Base64Encode)
Add'l Data: C:\Users\<username>\AppData\Local\Temp\<filename>.tmp
And this is what gets logged on the Event Viewer on the client machine:
Faulting application name: <programname>.exe, version: 0.0.0.0, time stamp: 0x5011b17b
Faulting module name: ntdll.dll, version: 10.0.10240.16603, time stamp: 0x565531ee
Exception code: 0xc0000005
Fault offset: 0x0003dd2a
Faulting process id: 0x88c
Faulting application start time: 0x01d13c3c46d18779
Faulting application path: C:\xxxxx\<program-name>.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: fdeb33bd-e546-4711-8c4e-e1d615bc3c14
This desktop windows application continues to be maintained on a Windows XP machine as its IDE won't work on earlier versions of Windows. It uses Clarion Enterprise Edition version 5.5H (by Softvelocity) and uses the following Clarion extensions: ClarioNet Application Performance Writer V1.4, ClarioNET for Clarion 5.5 version 1.4 (from Jan-11-2004), xmlFUSE, wPDFControl and vuMail 3.20.
Based on the error message, we believe this issue may be related to how the two files (from ClarioNET) compiled in this system: lscomp.dll and lsdecomp.lib, react on Windows 10, where we unfortunately cannot ask for support as this Clarion version reached its End Of Life many years ago.
When setup in a Windows 10 PC, it is configured to run with administrator rights to all users (Run this program as an administrator), under Compatibility mode for "Windows 7", "Windows Vista" and even "Windows XP" and added as an exception on the Data Execution Prevention (DEP) list. The "AppData\Local\Temp\" folder is given "Full control" rights to "Everyone" user. Windows is up-to-date on Windows Updates and the Antivirus and Firewall have been disabled. We have ran the application performing a clean boot in windows starting the machine with minimal set of drivers and startup programs. Still this issue persists. :(
As we move to a completely different cloud based system, we will still need to hang on to this old legacy program for at least the next 16 months. Setting a virtual box with Windows 7 has been proposed but has been rejected.
Questions: 1) What other configurations can I set on Windows 10 to have this program run well? 2) Are there any 3rd party applications to help this application run smoothly on Windows 10? 3) Any other hints/tips? :'(
Although Clarion-nonspecific, I've had that error thrown before after a bad install of a windows update (a quick google shows it might have been KB2882822). This could be a more general OS error instead of something Clarion-specific.
If this involves the Linder compression dll, be aware that it is not thread-safe. If that's the underlying compression technology you're using, surround calls to it with a critical section and see if that helps.
I have a legacy business application written in VBA in Excel. It uses the VBA DAO library (installed at c:\program files (x86)\Common Files\Microsoft Shared\DAO\dao360.dll) and the classes Workspace, Database, DBEngine, Connection) to connect to a SQL database via ODBC.
It works properly up to Windows 7, but on Windows 8 /Server 2012, it doesn't work, on the very first call to DAO:
Set ws = DBEngine.CreateWorkspace(wsName, "", "", dbUseODBC)
raises a runtime error number 3633 description "Cannot load DLL: 'msrdo20.dll'". This occurs both in the class library's DBEngine.Errors and the regular VBA Err object.
This error occurs whether or not the file msrdo20.dll exists.
I found
https://support.microsoft.com/en-us/kb/260369
which says to include ODBCDirect, but that doesn't seem to be relevant.
I found
http://www.xtremevbtalk.com/archive/index.php/t-172385.html
which suggests removing Microsoft DAO 3.6 from the references and switching to DAO 3.5 -- but doing that breaks things even worse, I get run-time error 429, "ActiveX component can't create object".
This is Windows Server 2012, Excel 2013.
This blog solved that problem for me:
http://pwaldman.com/unable-to-load-msrdo20-dll-or-rdocurs-dll/
Extract:
Resolution
Download Service Pack 6 for Visual Basic 6.0 (Vs6sp6.exe)
http://www.microsoft.com/en-us/download/details.aspx?id=9183
Run Vs6sp6.exe and extract the files
Open msrdo20.cab, it contains the following files: MSRDO20.DLL, MSRDO20.INF, and RDOCURS.DLL. Extract all three files and copy them to the C:\Windows\SysWOW64\ directory.
Open an elevated(admin) command prompt, navigate to C:\Windows\SysWOW64, and register MSRDO20.DLL. The RDOCURS.DLL does not need to be registered.
C:\Windows\System32> cd C:\Windows\SysWOW64
C:\Windows\SysWOW64> regsvr32 MSRDO20.DLL
I had forgotten to run my command prompt as administrator when I used regsvr32. That's why VBA wasn't able to find the DLL.
I am having a problem "IIS Express worker process has stopped working".
I'm developing a project using ASP.NET MVC.
This is visual studio on may be a sample project.
Windows 7 Using.
My Steps 1 open project on Visual Studio 2012
My Steps 2 Build my Project
My Steps 3 Run my project
Error Details
Faulting application name: iisexpress.exe, version: 8.0.8418.0, time stamp: 0x4fbaa9e8
Faulting module name: ApiRd.dll, version: 0.0.0.0, time stamp: 0x52f26a34
Exception code: 0xc000041d
Fault offset: 0x0000239c
Faulting process id: 0x12ec
Faulting application start time: 0x01cf2d83a6972b10
Faulting application path: C:\Program Files (x86)\IIS Express\iisexpress.exe
Faulting module path: C:\Users\Administrator\AppData\Local\Obqcics\ApiRd.dll
Report Id: e4f689ae-9976-11e3-9426-e840f2ac7e6e
Faulting package full name:
Faulting package-relative application ID:
Close out Visual Studio completely, then check your system tray and stop any instances of IIS Express that might be running. Re-start Visual Studio, create a new MVC project based on one of the standard templates. Check the properties to ensure it's set to use IIS Express, and then run it. If you don't get the same error, check any custom code your might have in the troubled project's Global.asax.cs (or .vb) file. Put debug points on the first line of every method you have code in (Application_Start, etc.). Step over each line and see where it breaks.
If you don't have any custom code in there, close out VS and clean the ASP.NET temp directories. Do a restart, and see if the problem persists.
The problem seems to have been caused by AVG antivirus.
I was able to solve by uninstalling AVG antivirus.
Right click on your ASP.NET MVC project.
Select 'Properties' option.
Go to 'Web' settings and choose option 'Use Visual Studio Development Server' in 'Servers' category.
Now try to run the application, it will execute.
Run your visual studio and your browser as Administrator
I had default chrome as a default browser and was getting the same issue while debugging. I changed the default browser in visual studio to Internet Explorer and then tried again. I was able to run my project successfully. Hope this may help.