Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash: "Multiple-step operation generated errors" when accessing Data tab of view #423

Open
axbender opened this issue Dec 4, 2018 · 10 comments

Comments

@axbender
Copy link

commented Dec 4, 2018

  1. Open HeidiSQL
  2. Select the view area of a MSSQL database.
  3. Select a specific view (works OK with some other views).
  4. Press the "Data" tab.
    Crash

Current behavior

The application crashes with the attached bug report.

Expected behavior

Do not crash ;-)

Possible solution

Hm, that's your part...

Environment

Database's OS: Windows Server 2012, 64-bit
Database: MSSQL Server 2012, 64-bit
Client's OS: Windows 10, 64-bit using 32-bit executable (9.5.0.5362).

The problem might be correlated to the complexity of the used view. While I might provide the view, I cannot provide the underlying data.

BUGREPORT (provided as is, as I was not able to attach it)


date/time          : 2018-12-04, 09:46:34, 432ms
computer name      : IFM10N12495
user name          : debendax <admin>
operating system   : Windows 10 x64 build 17134
system language    : English
system up time     : 1 day
program up time    : 1 minute 7 seconds
processors         : 4x Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
physical memory    : 4379/8047 MB (free/total)
free disk space    : (C:) 126,58 GB (K:) 3,43 GB
display mode       : 1920x1080, 32 bit
process id         : $145c
allocated memory   : 94,13 MB
largest free block : 634,30 MB
executable         : heidisql.exe
exec. date/time    : 2018-12-03 08:48
version            : 9.5.0.5362
compiled with      : Delphi 10.2 Tokyo
madExcept version  : 4.0.20
callstack crc      : $fae19fd7, $c9b0e229, $c9b0e229
exception number   : 1
exception class    : EOleException
exception message  : Multiple-step operation generated errors. Check each status value.

main thread ($3390):
0086cbb9 heidisql.exe   Data.Win.ADODB            TCustomADODataSet.GetFieldData
0083782a heidisql.exe   Data.DB                   TField.GetData
00837b1d heidisql.exe   Data.DB                   TField.GetIsNull
008ac326 heidisql.exe   dbconnection    6422   +7 TAdoDBQuery.IsNull
00a84d25 heidisql.exe   Main            8603  +10 TMainForm.AnyGridGetText
0076228d heidisql.exe   VirtualTrees   33561   +8 TCustomVirtualStringTree.DoGetText
00761282 heidisql.exe   VirtualTrees   33023   +4 TCustomVirtualStringTree.GetText
007621ef heidisql.exe   VirtualTrees   33545  +26 TCustomVirtualStringTree.DoGetNodeWidth
00756f49 heidisql.exe   VirtualTrees   26697 +112 TBaseVirtualTree.GetDisplayRect
00a86b27 heidisql.exe   Main            9175  +28 TMainForm.AutoCalcColWidth
00a774c0 heidisql.exe   Main            5054 +175 TMainForm.DataGridBeforePaint
00749b5b heidisql.exe   VirtualTrees   19214   +2 TBaseVirtualTree.DoBeforePaint
0075bbe0 heidisql.exe   VirtualTrees   30013   +5 TBaseVirtualTree.PaintTree
74d61d72 KERNELBASE.dll                           QISearch
00751269 heidisql.exe   VirtualTrees   23549  +23 TBaseVirtualTree.Paint
005bf3fb heidisql.exe   Vcl.Controls              TCustomControl.PaintWindow
005b92b1 heidisql.exe   Vcl.Controls              TWinControl.PaintHandler
005b9aa0 heidisql.exe   Vcl.Controls              TWinControl.WMPaint
005bf395 heidisql.exe   Vcl.Controls              TCustomControl.WMPaint
00746f15 heidisql.exe   VirtualTrees   17412   +8 TBaseVirtualTree.WMPaint
005b4502 heidisql.exe   Vcl.Controls              TControl.WndProc
005b90e7 heidisql.exe   Vcl.Controls              TWinControl.WndProc
0075444d heidisql.exe   VirtualTrees   25273  +32 TBaseVirtualTree.WndProc
005b86b4 heidisql.exe   Vcl.Controls              TWinControl.MainWndProc
0053c560 heidisql.exe   System.Classes            StdWndProc
77d7c6cb ntdll.dll                                KiUserCallbackDispatcher
74858482 KERNEL32.DLL                             BaseThreadInitThunk

@swiffer

This comment has been minimized.

Copy link

commented Dec 12, 2018

@axbender can you check if the view contains DECIMAL columns?

perhaps related to #151

@axbender

This comment has been minimized.

Copy link
Author

commented Dec 17, 2018

Sorry for the late answer...
No but it contains a lot of colums with the MS datatype "GUID". Attached is another bugreport that was produced (reproducible) when executing the specified query.

@axbender

This comment has been minimized.

Copy link
Author

commented Dec 17, 2018

Hm, seems, I'm no longer able to attach files via FF ESR. Will come back...

@axbender

This comment has been minimized.

Copy link
Author

commented Dec 17, 2018

Here we go...
bugreport.txt
query.txt

@ansgarbecker ansgarbecker changed the title Crash when accessing the "Data" tab of a specific view in MSSQL Crash: "Multiple-step operation generated errors" when accessing Data tab of view Mar 20, 2019
@robbyappel

This comment has been minimized.

Copy link

commented Jun 26, 2019

Hi,

In reaction on the answer on the Heidi Forum,

It looks that i have the same error as mentioned above,
I use the Heidi 64 bit (windows 7 64 bit)version to browse trough MSSql (2008, 2012) database with or without SSL active.
The moment i hit de Data tab Heidi chrashes.
When i use Heidi 8.0 i dont experience the problem, but i cant connect to SSL activated SQL servers.

I hope you can fix the problem because i like Heidi very much
bugreport2.txt

@robbyappel

This comment has been minimized.

Copy link

commented Jun 26, 2019

I have tried to analyse the problem,

It looks indeed that Heide crashes only on tables with data columns of the datatype DATE (Default('0001-01-01')) available.

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Aug 31, 2019

I just wanted to try out if thet multiple-step error really only occurs with the MSOLEDBSQL library, but for some reason I cannot even get the connection to work. Using SQLOLEDB in named pipe mode with ".\SQLExpress" host, I get a connection but the same with MSOLEDBSQL runs into a timeout. Can somebody tell me what that new driver expects differently eg in the host name?

ansgarbecker added a commit that referenced this issue Sep 22, 2019
…lly healing these "multiple step" errors on MS SQL
@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Sep 22, 2019

I just added the value DataTypeCompatibility=80 to the ADO connection string, in order to tell the new driver to be more ADO compatible. See the documentation from Microsoft. I can still establish connections through the old SQLOLEDB driver, but I have problems with the new one. So anyone here who could check if that "multiple step" error is gone with the new HeidiSQL build 5695?

@FlavioSuarez

This comment has been minimized.

Copy link

commented Sep 23, 2019

I can confirm!!! The crash is gone for me!!
Tested on a table and on a view that always crashed Heidi with the MSOLEDBSQL driver. With the SQLOLEDB driver the crash didn't happen.
Thank you very much!! I love Heidi!!! :-)

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Oct 6, 2019

There is still this crash with SQLOLEDB on large decimal values with more than 15 digits: https://www.heidisql.com/forum.php?t=25333#p34736

I also still get "Error Locating Server/Instance Specified [xFFFFFFFF]" using the newer MSOLEDBSQL driver, although I installed it properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.