Comments
9 comments
-
I think you can ignore this for now. I have been working with Microsoft on this and they think the problem is on there side. It just shows up because of SQL Prompt adding to the total memory usage.
-
Hi,
Thank you for your information @erenken. Can you give as an info when it will be repaired?
Best regards
Krzysztof -
I haven't heard anything about a timeline for a fix from Microsoft. When I hear something I will let everyone know.
-
I have the same issue. And it always happens when I have a large resultset in the result tab.
After closing the query tab everything works again.
No more out of memory error. (Im using SSMS v17.2 - 14.0.17177.0) -
Same issue here using SSMS v17.2.
Any updates on the fix? -
Nothing official, but follow these steps for the SSMS.exe fix it for me:
http://gisgeek.blogspot.com/2012/01/set-32bit-executable-largeaddressaware.html
Make sure to make a backup of SSMS.exe before you do this. -
Same issue here using SSMS v17.2 (also had it with 17.0 and 17.1)
Followed erenken's instructions
Here are the commands I used (your path may vary)
Make a copy of "C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe"
Open Admin Command prompt
Change Directory to C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\ADL Tools\2.2.5000.0\CppSDK\VC\bin
(This is where my Visual Studio editbin and dumpbin programs were located)
editbin /LARGEADDRESSAWARE "C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe"
dumpbin /headers "C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe" | more
You should see "...Application can handle large (>2GB) addresses..."
We shall see if this helps. -
I believe this has been addressed in SSMS 17.3.
-
I still get OOM errors in 17.3, even with no Redgate tools installed
Add comment
Please sign in to leave a comment.
An error occurred while executing batch. Error message is: Exception of type 'System.OutOfMemoryException' was thrown.
If I uninstall SQL Prompt 8 I no longer get this error message. I have a SQL Dump that was triggered by the exception if you are interested. The only way to fix this error is to shut down SSMS and restart it.