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.
Related
I have created release in Azure Devops, which should be deplyoing my web application to IIS which is on a physical server (Windows Server 2008) but firstly I am getting a warning:
##[Warning 1]
The operating system the agent is running on is "Windows Server" (OS name: 2008, OS version: 7601), which will not be supported by the .NET 6 based v3 agent. Please upgrade the operating system of this host to ensure compatibility with the v3 agent. See https://aka.ms/azdo-pipeline-agent-version
Then I am getting a error:
I have created an Agent on my server, and until today I was not getting this error. How could I fix this?
Windows Server 2008 reached end of life years ago, so no modern tool is going to support it any more.
You might feel lucky that things were running, but that luck finally ran out. You have to upgrade your machine to a supported Windows version.
I have a ASP.NET 3.5 application that includes a 32-bit DLL. It works fine (and has for years) on Windows XP, 7 and 10. I am adding support for Windows 2012, 2012 R2 and 2016. It works on 2016, but does not work on 2012 R2.
At the first call to the DLL, the following error occurs:
BadImageFormatException: An attempt was made to load a program with an
incorrect format. (Exception from HRESULT: 0x8007000B)
The same build and install script is used for all OS's tested. Each OS is on a VM on the same machine, so the hardware for all OS's is identical. For each OS:
OS is fully updated.
vcredist 9.0 (x86) is installed as part of the installation.
IIS DefaulatAppPool has 32-bit applications enabled.
I've tried all the suggestions in the posts I've found on this problem, but nothing works. Any ideas?
Double check in Task Manager that your W3WP.exe process for the application is running 32-bit and that it is in fact Default App Pool that is trying to load the DLL. This error message almost certainly means 64-bit process trying to load 32-bit DLL.
My application starts fine on my Windows 8 laptop.
However I can not start it on Windows Server 2008 R2. Following error occured:
The exception unknown software exception (0xe0434352) occured in the application at location 0xfd5ecaed.
The following is printed in the command line:
Unhandled Exception: Cannot print exception string because Exception.ToString() failed.
My solution contains one c++-cli project which i'm trying to use, and if I do not use it then everything works fine, so commenting just this line helps:
// private static CliAdapterMain cliAdapter = new CliAdapterMain();
I've tried:
repair .NET Framework 4.5 on target machine
repair/reinstall VS 2012 Update 1 Redistributable (both x86 and x64, version 11.0.51106.1)
updated my VS2012 to Update 1 recompiled project
no Windows pending updates, tried to reboot system several times
Dependency Walker claims that following DLL's are missing: GPSVC.DLL IESHIMS.DLL MF.DLL MFPLAT.DLL MFREADWRITE.DLL WLANAPI.DLL However they exist on target computer, for example here
c:\Windows\winsxs\amd64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.1.7601.17514_none_8649674dfda23046\gpsvc.dll
Probably I can try manually reregister missing dll's, but i don't think this is really a problem. Looking at an exception it seems that something is broken, not something is missing.
upd: From Windows logs:
Va.MBClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException
Stack:
at Va.MBClient.Program.Main(System.String[])
So I guess that private static CliAdapterMain cliAdapter = new CliAdapterMain(); is failed but i don't know why.
upd played with my application a little. Finally i've found just one line of code that causes a failure. This is #include <boost/thread.hpp>. Why this doesn't work? I'm using latest version of boost (1.52), but i did built it on my Windows 8 machine. Should I rebuilt everything for Windows Server 2008 R2? Should I built entire project on Windows Server 2008 R2?
It is due to in the Windows Sever, some features is not enabled by default, you need to add the Windows Media Services and Wireless LAN Service by yourself to get the Dll back.
You can reference to MSDN
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
I have written an app to run on 64bit Windows Server 2008, it needs to go in the schedular as it needs to run every 15 minutes. For some reason the program crashes after being open for a few minutes (this is without it being in the schedular). The program runs fine on both my 32bit laptop and a colleagues 64 bit laptop, but fails on this server. Error details:
EventType = APPCRASH
Fault Module Name = KERNELBASE.dll
Fault module Version = 6.1.7600.16385
Exception Code = e053534f
Any help on this would be most appreciated, ive already tried changing the target platform to x64, setting DetectNewerInstalledVersions to false, running as administrator and changing the compatability settings to what the compatability checker recommends (Windows XP Service Pack 2) and still no avail....
That's very little to go by. However, the exception code is EXCEPTION_SOFTSO, a "soft stack overflow" exception. It is raised when the CLR is about to run managed code but detects that there isn't enough stack space left to safely execute the code.
You'll need a debugger to get to the bottom of it. Use the Debug + Exceptions dialog to make the debugger stop at the exact point where the exception is raised.