Greeting; I have a development virtual machine I use daily for my job. Today I had a Windows Updates KB3212646, KB3197868, KB3185330 install and request reboot. After rebooting, I started getting errors in applications that ran SQL Statements. I opened SSMS 2014 to test and was getting different errors on simple selects. Example, I got all three of these errors from running the simple select a few times in a row.
select * from MVXJDTA.MITMAS
--An error occurred while executing batch. Error message is: Internal connection fatal error. Error state: 18
--An error occurred while executing batch. Error message is: Index was outside the bounds of the array.
--An error occurred while executing batch. Error message is: Object reference not set to an instance of an object.
I'm running Windows 7 x64 SP1.
I have Visual Studio 2010, 2012, and 2013 installed.
I have SQL Server 2008 R2, 2012, 2014, and 2016 installed.
I have removed the updates after the failure and I still have the errors. The errors don't occur on SMALL select statements, only larger ones. (MITMAS has 171,252 rows, 224 columns) Not a massive table by any means, but not a simple one either. If I do select top 100 MMCONO, MMITNO from MVXJDTA.MITMAS I do not seem to get the error. I have tested in SSMS for 2012, 2014, 2016, and in Visual Studio 2013.
I have not had the problem to till today, I know several Windows Updates installed Tuesday, but I didn't have issues yesterday after that reboot. I have not installed or uninstalled any other software.
Any assistance is appreciated.
In response to the comment that is can't be happening with the query listed:
Sadly, I was unable to resolve this issue. I installed all available service packs for all products, and even reinstalled the three updates listed in the question. After 10 hours of trouble shooting, and knowing I had to work again today, I started the restore process from backup. I believe something was corrupted in the .Net framework or Native client, as no software using the SQL Native client could run any statement that returned more than a few rows.
I will snapshot the machine before any more Windows Updates are installed, and advise here if those updates cause the problem to reoccur.
Sorry I couldn't report a better solution.
Billy
Related
Users in my office who have been upgraded to Windows 10 (build 1909) are suddenly getting the message "[Microsoft][ODBC Drive Manager] Invalid cursor state (#0)" whenever they run a pass through query in Microsoft Access. It doesn't matter how complicated the Pass Through query is, they all crash. We use SQL Server on our back-end. I have tried updating the ODBC drivers on our users' machines to the most recent version, but this doesn't solve the problem.
It is very frustrating because I can open tables linked to our SQL Server with no problem. I can write an equivalent query in Access and it will run. I even installed SQL Management Studio on one user's machine, and I could run the query fine there, I just cannot get the Pass Through to run. We are using 32 bit Access from Office 365 with the most recent updates.
Any help would be appreciated.
I'm running an SSIS package on a recent install of SQL Server 2016. Recently the All Axecutions report of the Integrations Services Catalogs SSISDB started looking like the screenshot below. The package that is executed on a 5 minute basis runs fine. No errors. I can see the data being transferred as expected. Something is wrong with this report. I did some searching around and can't seem to find anything.
Anybody have any ideas as to what is wrong? Why is it showing #Error everywhere?
Solution: Restart SSMS.
I can reproduce this error with on SSMS 13.0.16106.4 / SQL Server 13.0.4206.0 (Although the reports was working for a period, the the issue came back).
With the SQL same user, but running SSMS 12.0.5000.0 (from a remote desktop) the reports were fine.
Another user with SSMS 14.0.17177.0 has never had the issue.
Restarting the server had no effect.
I restarted SSMS 13.0.16106.4, which solved the issue. This could be a SSMS memory issue.
Also posted on: https://connect.microsoft.com/SQLServer/feedback/details/3103853/ssis-built-in-execution-reports-are-broken-in-ssms-2016-v13-0-15800-18
Using SSMS Microsoft SQL Server Management Studio 14.0.17285.0. Solved this by closing SSMS and restarting it.
I had this exact same problem and initially thought it was due to using the latest SSMS package - 17.1 on Windows 10 - but others with the same setup were not getting the errors.
I then ran the configuration for SSRS (which had been installed but not configured). This created the reporting server databases but made no difference. I don't think SSIS reporting uses SSRS anyway but not sure.
I then ran Windows update and it installed latest .NET 4.7 packages.
After a re-boot SSIS reporting was back to normal!
So one or combination of what I did above together with a re-boot made the difference but equally it may just have been a re-boot that was required.
This was on my development machine and I have been backing up and restoring the SSISDB from production to my development environment - this may have a bearing on attempting to re-producing this problem but I have not experienced it since and after fully deleting and restoring the SSISDB.
Hope that helps?
I had this issue. Turns out I had dropped some windows groups from the database I was loading data into (which was on a completely different server). When I added them back, the reports worked and didn't show #error
This makes absolutely no sense of course, but I thought I'd document it in case it helps or jogs someones memory
RE: "I restarted SSMS 13.0.16106.4, which solved the issue. This could be a SSMS memory issue." from #James Bourne
RE: "Using SSMS Microsoft SQL Server Management Studio 14.0.17285.0. Solved this by closing SSMS and restarting it." from #Ade
I had some very large nHibernate queries (captured from Extended Events) open in a couple of SSMS tabs. I closed each tab and restarted SSMS version 18.8.
Problem solved!
I have searched all over this issue and have found no solutions.
This is the error I am getting:
An error occurred while executing batch. Error message is: Method not found: 'System.String Microsoft.SqlServer.Management.Smo.Util.BytesToHexString(Byte[], Int32)'.
I had no issues with this prior to installing the Windows update for Service Pack 2 and I need this working for my class. My instructor also has no idea how to fix this other than a reinstall which is my LAST resort.
I know it is not my queries, as they ran perfect prior to this update.
Please help
I just had exactly the same problem, on a clean install of SQL Server 2014 (Express edition) and found that restarting the server itself cured the problem. (In Management Studio, right click on the server at the top of the tree in the object explorer and choose "Restart", or just restart the service...)
I have been using SQL Server Management Studio for years. Yesterday, when I started hitting "new Query", I would get the following error in pop up form:
"is not a valid win32 application".
I did a lot of googling, and I found this:
http://blog.sqlauthority.com/2009/04/30/sql-server-fix-error-is-not-a-valid-win32-application-exception-from-hresult-0x800700c1/
Which is not at all applicable (but I did set all of my application pools in my IIS to allow 32 bit applications on both the server and my client. I'm not sure how that would make any difference and it didn't). I thought maybe it was a problem with VSSHell, but I have been unable to find any valid information to fix it if it is.
I am using Windows 7 64 bit Ultimate.
My colleagues, who connect to the same SQL Server instance, do not have this issue (so it is a problem with my env).
I tried uninstalling and reinstalling.
I tried installing SQL Server 2008 R2 Management Studio (and express version).
I tried installing SQL Server 2005 Management Studio Express.
I even tried the SQL Server 2012 R0 Management Studio. In all, of these, when I click, New Query, I get a pop up that says "is not a valid win32 application".
Please help!
Had the same issue - it turns out one of the MS C Runtime libraries got corrupted somehow. I got the name from the exception details. In my case it was MSVCM80.dll in C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a, that was 0kB.
Once I replaced it with the actual file, all started working again.
My advice is - try to locate the faulty file that SQL Studio is trying to open (in my case the same error happened when I tried to start SQL Profiler, and I could trace the exception details there).
Good luck
In the past, I installed Visual Studio 2010. With that comes SQL Server.
Now I installed this:Microsoft SQL Server Management Studio Express
Now, upon starting, I get this screen:
And it doesn't matter what Server name I enter, nothing works.
I've tried installing SQL Server 2008 Enterprise(I can get that via MSDNAA), but that fails totally, giving me this error:
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:
Unable to open Windows Installer file
'G:\x86\setup\sql_engine_core_inst_loc_msi\1033\sql_engine_core_inst_loc.msi'.
Windows Installer error message: The
system cannot open the device or file
specified. .
Click 'Retry' to retry the failed
action, or click 'Cancel' to cancel
this action and continue setup.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.2531.0&EvtType=0xC24842DB
------------------------------ BUTTONS:
&Retry Cancel
There is no help, I can click retry as much as I want, nothing changes. I went to the file itself, and Windows says I should check if it is a valid installer file.
And that's my story. I need to get this up and running, and it's all going against me. Can anyone help?
Oops, I have the same problem [1]!
Though I did not investigate the issue
(since I do not need now VS2010 or SQL Server Express)
You can find helpful the answer to my [2] which was reported helpful to resolve the problem by others.
I am afraid it should be reported as bug to MS Connect, though I do not have time and desire to invest time in investigation. Anyway, when MS teams cannot resolve something they close bugs "by design" or "not reproduced"
Since there is no channel to report bugs on SQL Server 2005 xxx (or VS2008), for which the reports are closed, it should be reported in VS2010 board.
Give link if you report, I shall upvote the bug and mark it as reproduced by one more.
My related questions (having some solutions):
in asp.net "Visual Studio and Visual Web Developer Express " forum, frequently answered by MS teams
[1]
S2010RC setup installs unusable MSSQL2008 Express?
(the same problem as yours, unanswered)
http://forums.asp.net/t/1571173.aspx
[2]
MSSQL2008R2 (BIDS, i.e. VS2008) after VS2010?
(answered and solution is reported to be helpful to others)
http://forums.asp.net/t/1568816.aspx
[3]
to submit bug reports on BIDS 2008 R2 as VS2010 bugs?
http://forums.asp.net/t/1568807.aspx