Signtool is able to sign all passed assemblies just fine, but when it tries to timestamp them it fails with error code 255.
This also results in an error in the event viewer:
Faulting application name: signtool.exe, version: 10.0.10586.212, time stamp: 0x56fa257d
Faulting module name: ntdll.dll, version: 6.3.9600.17415, time stamp: 0x54504b0d
Exception code: 0xc0000374
Fault offset: 0x000e5be4
Faulting process id: 0x768
Faulting application start time: 0x01d3061e0a3c7af5
Faulting application path: C:\Program Files (x86)\Microsoft SDKs\ClickOnce\SignTool\signtool.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
My msbuild task for timestamping looks like:
<Exec Command='"$(SDK40ToolsPath)..\..\..\..\ClickOnce\SignTool\SignTool.exe" timestamp /t http://timestamp.verisign.com/scripts/timstamp.dll "%(SignableFiles.FullPath)"' />
I was able to produce an error when running the signtool directly from command line, but running cmd as an Administrator resolved that issue. After adding permissions to the user (same user that is running TeamCity Build agent service), allowed me to execute the signtool timestamp successfully without elevation.
To get closer to reproducing, I tried mocking my msbuild file to just run the signtool, but this also succeeded.
TeamCity seems to use an MSBuildBootstrapper, but I was unable to figure out the correct syntax to call my custom build script from it. Has anyone else run into this issue?
Related
Im having an issue where our ASP Net Core Website crashes immediately with little information.
The output in visual studio shows:
The program '[10196] dotnet.exe' has exited with code -532462766 (0xe0434352).
After settings COREHOST_TRACE = 1, I get the following error:
Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'MyProject.dll, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. File is corrupt. (Exception from HRESULT: 0x8013110E) ---> System.BadImageFormatException: File is corrupt. (Exception from HRESULT: 0x8013110E)
--- End of inner exception stack trace ---
The Event viewer shows me the same error and says the source is .NET Runtime, and is then immediatly followed by another error with the source Applciation Error, with the following details:
Faulting application name: dotnet.exe, version: 5.0.721.25508, time stamp: 0x609308e9
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1023, time stamp: 0x924f9cdb
Exception code: 0xe0434352
Fault offset: 0x0000000000034b89
Faulting process id: 0x4a18
Faulting application start time: 0x01d76797eececb6d
Faulting application path: C:\Program Files\dotnet\dotnet.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: eed8cc7d-eeb1-45d0-b33c-532e3524f4ee
Faulting package full name:
Faulting package-relative application ID:
Genuinely, I have no idea why, but this is being caused when I add any new property to any class, if I remove it, clean the project, rebuild and run, it works as expected.
I can't find any helpful information anywhere, suggestions on how I can get the real error that is causing the crash would be much appreciated.
I have ETL packages that works fine in Visual Studio 2019
When we deploy and run it from SQL Server Agent, it gives the error below
Additional info: the package is set to "Encrypt sensitive with password" and we set the connection password in the SQL Job step settings
Faulting application name: ISServerExec.exe, version: 14.0.1000.169, time stamp: 0x599ccc42
Faulting module name: **OraOLEDB11.DLL, version: 11.2.0.1, time stamp: 0x4b9a19db
Exception code: 0xc0000005
Fault offset: 0x000000000002c000
Faulting process id: 0x3954
Faulting application start time: 0x01d642753af07699
Faulting application path: c:\Program Files\Microsoft SQL Server\140\DTS\Binn\ISServerExec.exe
Faulting module path: C:\oracle\oracleclient64\bin\OraOLEDB11.DLL
Report Id: 0db0c583-e4aa-4dec-89f5-509f3969595c
Faulting package full name:
Faulting package-relative application ID:
UPDATE
Tried executing package from Integration Services Catalog in SSMS but also failed, the detailed error is "cannot acquire connection from connection manager"
It looks something related to password in the oracle database connection
Thanks, we found the solution.
It works when we changed the runtime in SQL Server Job Step properties to 32-bit
In Windows 7, a process started with CreateProcessAsUser by a windows service with a local system account crashes, but the same process started manually runs fine. The CreateProcessAsUser functionality is in a separate COM component [64 bit C++ dll], and the windows service [dot net 4.6.1] has platform target [Any CPU]. The process does not write anything to the event log either, suggesting that no code is executed, and it crashes immediately. This code works perfectly in windows 10.
I tried to attach to the process but it ends too soon to do anything. I do get a message "Module not found" , suggesting that it doesnt find a library. But I cant figure out which one. I gave it all the libraries it needs, which can be seen by the fact that the program runs ok when started manually from the same folder. I also tried to specify the startup folder in the function CreateProcessAsUser, but there was no difference, but I think it starts in the correct folder by default [where it is located]
I found the following link on SO
Why is this process crashing as soon as it is launched?
But it did not help either. ProcMon does not show where a module was not found [It says PATH NOT FOUND if I remove a known module]
The process exit status is -1066598274
and the stack trace is
0 ntoskrnl.exe RtlNtStatusToDosError + 0x1086 0xfffff8000712f206 C:\Windows\system32\ntoskrnl.exe
1 ntoskrnl.exe RtlCopySidAndAttributesArray + 0x1789 0xfffff8000714b0d9 C:\Windows\system32\ntoskrnl.exe
2 ntoskrnl.exe RtlNtStatusToDosError + 0x1538 0xfffff8000712f6b8 C:\Windows\system32\ntoskrnl.exe
3 ntoskrnl.exe KeSynchronizeExecution + 0x3a23 0xfffff80006e75e53 C:\Windows\system32\ntoskrnl.exe
The event viewer shows the following information
Faulting application name: BizBrainAgentPluginHost.exe, version: 1.0.0.0, time stamp: 0x5b88084d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b8479b
Exception code: 0xc06d007e
Fault offset: 0x0000000000009e5d
Faulting process id: 0x484
Faulting application start time: 0x01d440746491e037
Faulting application path: C:\Program Files\Avinashi Ventures Pvt Ltd\myTallyApp Agent\BizBrainAgentPluginHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: a2f39c97-ac67-11e8-94f1-0023ae9747d0
Thanks
I am running diskspd.exe tool which you can download from:
Diskspd Utility: A Robust Storage Testing Tool (superseding SQLIO)
https://github.com/Microsoft/diskspd
Operating system: Windows 2016 standard
I first get this:
D:\Diskspd\amd64fre>diskspd.exe -d15 -o4 -t4 -b8k -r -L -w50 testdiskspd.dat
Error opening file: testdiskspd.dat [2]
Error opening file: testdiskspd.dat [2]
Error opening file: testdiskspd.dat [2]
Error opening file: testdiskspd.dat [2]
After 15 seconds I get this:
There has been an error during threads execution
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
At the same time I get following pop up window:
I have write permission in folder D:\Diskspd\amd64fre\. I tested this by creating a .txt file.
This is what I can see in my windows log.
Faulting application name: diskspd.exe, version: 0.0.0.0, time stamp: 0x54b9a313
Faulting module name: msvcrt.dll, version: 7.0.14393.0, time stamp: 0x57899b47
Exception code: 0x40000015
Fault offset: 0x000000000000c2c2
Faulting process id: 0x4b40
Faulting application start time: 0x01d3e2437778fe7f
Faulting application path: D:\Diskspd\amd64fre\diskspd.exe
Faulting module path: C:\Windows\System32\msvcrt.dll
Report Id: 2190f963-f533-4805-b23a-e3224c56e72d
Faulting package full name:
Faulting package-relative application ID:
Any suggestions?
I needed to provide the file size switch and a value. Then it ran fine. From the document it was not clear that it was a mandatory parameter.
D:\Diskspd\amd64fre>diskspd.exe -d15 -o4 -t4 -b8k -r -L -w50 -c1G testdiskspd
I have the following two error logs in the Windows Event Viewer of our IIS production server:
Source: Application Error
Category: (100)
Event ID: (1000)
Description: Faulting application w3wp.exe, version 6.0.3790.3959, faulting module mscorwks.dll, version 2.0.50727.3603, fault address 0x0001da8f.
Seconds later:
Source: .NET Runtime 2.0 Error Reporting
Category: None
Event ID: 1000
Description: Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module mscorwks.dll, version 2.0.50727.3603, stamp 4a7cd88e, debug? 0, fault address 0x0001da8f.
What can I do with these error messages? I see that I have a fault address and a dll name - are there any tools that will show me what is at this address in the dll? Would this be the correct approach to figuring out what caused the crash? I've so far not been able to replicate it.
Thanks.