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.
Related
I have a .NET Core web API that works fine when hosted in IIS on my local Windows 10 desktop OS. However, when I deploy the same code to a Windows Server 2016 machine, the app pool in IIS fails 5 times and then stops the app pool. The error in the event viewer indicates the following:
A process serving application pool 'My API' reported a failure during application preloading or service loading. The process id was '416'. Please ensure that all application preload or service settings in the application pool are configured properly. The data field contains the error number.
I've tried configuring the API to write out to the stdout, but it doesn't ever generate a log file.
This API was originally written in .NET Core 2.2, so I tried upgrading it to .NET Core 6 and have the same issue - it works in Windows 10 with IIS, but not on Windows Server 2016. The hosting bundle for the appropriate version is installed on the server. I found that if I change the app pool that is hosting my API to have a .NET CLR Version of .NET 4 instead of 'No Managed Code', it then works. All documentation indicates 'No Managed Code' is recommended.
I did actually get it to work at one point with the app pool set to 'No Managed Code'. I ran procmon to see if there were any failures accessing registry keys, system files or folders, etc. and did find that if I copied a few files like webengine.dll, webengine4.dll, and aspnet_rc.dll from the folders they were actually in to folders where procmon indicated it was looking for them in, it then worked. Obviously though I don't want to be copying system files to various locations.
My guess is that something isn't installed on the server or I've misconfigured something as I got the same result when creating a test Web API project in Visual Studio and used the sample endpoints included in the default project. Unfortunately I can't figure out what is missing or misconfigured.
I ran the JexusManager ASP.NET Core Diagnostics tool and this is the report:
System Time: 7/20/2022 8:01:35 AM
Processor Architecture: AMD64
OS: Microsoft Windows NT 10.0.14393.0
Server Type: IIS
Scan 35 installed module(s).
ASP.NET Core module version 2 is installed for .NET Core 3.1 and above: C:\Program Files\IIS\Asp.Net Core Module\V2\aspnetcorev2.dll (16.0.22173.7).
Scan 91 registered handler(s).
* Found a valid ASP.NET Core handler as { Name: aspNetCore, Path: *, State: Enabled, Module: AspNetCoreModuleV2, Entry Type: Local }.
Visual C++ runtime is detected (expected: 14.0, detected: 14.12.25810.0 built by: VCTOOLSREL): C:\Windows\system32\msvcp140.dll.
The application pool 'Test API' is used.
Pool identity is NetworkService
Please ensure pool identity has read access to the content folder D:\Program Files (x86)\My Company\Test API.
Pool bitness is 64 bit
Scan aspNetCore section.
"processPath": dotnet.
"arguments": .\TestApi.dll.
"hostingModel": inprocess.
In-process hosting model is detected. To avoid 500.xx errors, make sure that the bitness of published artifacts matches the application pool bitness
Framework dependent deployment is detected. Skip bitness check.
Found runtime config file D:\Program Files (x86)\My Company\Test API\TestApi.runtimeconfig.json.
Runtime is 6.0.0.
I did verify the bitness and the folder permissions. Both were set properly.
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, ...
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 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.
I recently resinstalled Windows 7 on my machine and went back to downloading and installing the tools to help me continue developing node.js windows azure web applications. I followed the instructions given on the node.js azure site:
http://www.windowsazure.com/en-us/develop/nodejs/
and using web installer 4.0 it says I have successfully installed these tools:
Windows Azure Powershell
Windows Azure SDK for Node.js - June 2012
Windows Azure SDK for .Net (VS 2012 RC) - June 2012
IIS Recommend Configuration
The problem I am experiencing is that when I run the site using powershell e.g:
start-azureemulator -launch
it goes ahead and runs IIS Express, and after several minutes IIS Express crashes with the following information:
Problem signature:
Problem Event Name: APPCRASH
Application Name: iisexpress.exe
Application Version: 8.0.8298.0
Application Timestamp: 4f620349
Fault Module Name: iiscore.dll
Fault Module Version: 8.0.8298.0
Fault Module Timestamp: 4f63b65c
Exception Code: c0000005
Exception Offset: 00021767
OS Version: 6.1.7601.2.1.0.256.28
Locale ID: 1033
Additional Information 1: f66d
Additional Information 2: f66d807b515d6b2dc6f28f66db769a01
Additional Information 3: 7b2f
Additional Information 4: 7b2f6797d07ebc2c23f2b227e779722e
I am running 2 instances each time, and both of them crash one after the other. Is anyone experiencing something similar and fix this issue ? Is their an upgrade I need to do ? I've run windows update but it says I've got all the latest updates etc.
Can I tell the powershell cmdlet to use IIS 7 instead of IIS Express? I'm guessing its something to do with IIS Express on my machine.
I did some hunting around and found this person here who experienced a similar problem:
https://github.com/tjanczuk/iisnode/issues/149
I've got a cron job running every 1 second, to check if any website totals need to be updated. Could this be causing IIS Express to crash?
Cheers
I believe your problem will be resolved if you install and use iisnode for IIS7 64bit (instead of iisnode for iisexpress) from the link below as I could fix a similar issue in past:
http://go.microsoft.com/?linkid=9784331