Error while running diskspd - testing

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

Related

ISServerExec.exe crash when executing from SQL schedule job

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

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

Crystal reports viewer print dialog crash

I have created a vs2010 win app that uses Crystal-reports 13.0 sp22
The app is deployed on a work-group of 5 computers
There is a printer connected to the network visible from all PCs
All PCs can print to the printer except one
This one can print from all programs eg notepad, PDF but not from my app
The user clicks on the viewers button to print, the print dialog shows up
but when print is clicked or layout tab is clicked the app crashes
Checking the event viewer I get two application errors:
Number 1:
Application: InsuranceAgent.exe Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException at
System.Globalization.RegionInfo..ctor(Int32) at
CrystalDecisions.Windows.Forms.CrystalReportPrintDialogCustomPanel.GetPaperSizeString(Double,
Double) at
CrystalDecisions.Windows.Forms.CrystalReportPrintDialogCustomPanel.UpdateChoices()
at
CrystalDecisions.Windows.Forms.CrystalReportPrintDialog.UpdateSelectedPrinterOnPanel()
at
CrystalDecisions.Windows.Forms.CrystalReportPrintDialog.CrystalReportPrintPropertySheetDlgProc(IntPtr,
CrystalDecisions.Windows.Forms.Internal.WindowsMessages, IntPtr,
IntPtr)
Number 2:
Faulting application name: InsuranceAgent.exe, version: 2.0.6622.2791,
time stamp: 0x5a876a70 Faulting module name: KERNELBASE.dll, version:
10.0.16299.248, time stamp: 0x4414ec23 Exception code: 0xe0434352 Fault offset: 0x0000000000014008 Faulting process ID: 0x27fc Faulting
application start time: 0x01d3a782bfac72fc Faulting application path:
C:\Program Files (x86)\PNSoftware\Insurance Agent\InsuranceAgent.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report ID:
70ffc331-1923-4f03-b06e-e07935328527 Faulting package full name:
Faulting package-relative application ID:
This Happens only in this PC all others are ok and all the same win10 OS
Any help will be deeply appreciated
Thank you all in advance
​After all the problem was solved
​I cannot explain why but only how !!!!!
I changed the regional settings ( the format tab )​ to English United States
​Any other setting does not work eg. English United Kingdom
​The funny thing is that on the network all other computers they have regional settings Greek and the application is working fine
​
​Would be great to have an explanation but at least at last it is working ...
All the best
Nikos

Teamcity Signtool via Msbuild Runner throws error on timestamp

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?

mysqld.exe keeps crashing

I appear to be in a bit of a bind. I have been working on some simple design changes to our website and having finished went to release them live. No sooner than I uploaded the affected pages, the MySQL Daemon service crahsed. I did a restart and then restarted the service as it didn't restart automatically and managed to navigate to the website. It crashed again and has been doing so nearly every ten minutes like clockwork.
The windows event log is listed here:
Log Name: Application
Source: Application Error
Date: 14/06/2013 10:03:47
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DEDICAT-3JPUQIF
Description:
Faulting application name: mysqld.exe, version: 5.5.28.0, time stamp: 0x503ddca5
Faulting module name: mysqld.exe, version: 5.5.28.0, time stamp: 0x503ddca5
Exception code: 0xc0000005
Fault offset: 0x00000000000fd869
Faulting process id: 0x428
Faulting application start time: 0x01ce68dc51cff4c0
Faulting application path: C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
Faulting module path: C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
Report Id: 525bda97-d4d1-11e2-95f3-525400bb8b87
Event Xml:
1000
2
100
0x80000000000000
6821
Application
DEDICAT-3JPUQIF
mysqld.exe
5.5.28.0
503ddca5
mysqld.exe
5.5.28.0
503ddca5
c0000005
00000000000fd869
428
01ce68dc51cff4c0
C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
525bda97-d4d1-11e2-95f3-525400bb8b87
Does anybody have any clues what might be causing this?
As always thanks in advance.
Graham
This turned out to be an erroneous space character at the end of several lines of a stored procedure generated by SqlYog. Removing the characters fixed the problem.
Cheers
Graham
When I researched, this error means your database is probably corrupt and needs rebuilding.
Have a look at MySQL suddenly not working on Windows Server 2003 server fault question.
Hope this helps.