an unexpected error happened during this operation. (MS Design Tools) - Not enough storage is available to complete this operation
-
i have a problem with sql server enterprise manager: whenever i try to return all the rows of a table, by means of the option menu, it returns the following error message: an unexpected error happened during this operation. (MS Design Tools) - Not enough storage is available to complete this operation.
I have sql server enterprise edition with sp3 installed.
When I run the same query (that returns me all the rows belonging to a table) by sql Query Analyzer everything is ok.
Can anyone help me finding the problem with my Sql Enterprise Manager?
Thank you Marianna
-
You may not have enough memory on your PC to do this.
What happens when you try and do this via QA ?
Good Hunting!AJ Ahrens
webmaster@kritter.net -
When i do it via QA it works fine, it returns me all the rows belonging to the table without any error message.
I tryed to access the server via remote desktop and also in this case I had no problem both via option menu and via QA. The server has 2GB of RAM.
In the end i would like to add that no error is registered in the event viewer neither in SQL Server error file.
Thank you Marianna
-
I don't think the problem is with your server rather your PC itself. I think you are overrunning your own memory buffer..
Good Hunting!AJ Ahrens
webmaster@kritter.net -
I have exactly the same symtoms.
I have rebuilt the server twice using Windows 2K SP4 and SCL 2000 SP3, but as soon as I use Enterprise Manager to view a table the "Not enought Storage..." message appears. Have you managed to find the problem yet? It looks like I may have to return the server (under warrenty) unless someone can advise on a fix.
Kevin Tall
-
I think AJ is right, EM is not a good place a view all rows of a table especially a large one. It consumes alot of mem.
That is why there is QA
-
I have one server running SQL Server SP 2 and one running SP 3. The SP 3 box has the error and the SP 2 box does not. I don't know if this is causal or coincidental yet. But I know that the databases are exactly the same and the SP 3 box is much, much more powerful.
More specifically, when the SP 3 box connects to the SP 2 box, though Enterprise Manager, it generates the error. When the SP 2 box connects to the SP 3 box, it does not.
So it seems to be a problem with the Enterprise Manager GUI and not the underlying DBMS.
Brian
-
We too have pretty much the same issue. We have clustered Dell PowerEdge 2850 servers w/ 4GB Ram, connecting to a CX300 SAN. We get the message on all 4 servers whether or not they connect to a database on the SAN or on another stand alone server. We can run EM from some other non-clustered server and it works fine. We've tried reinstalling SQL, and even rebuild one of the 2-node clusters from the ground up using different media. This did not work. We have escalated this problem to Dell and Microsoft. Any update to this would be appreciated. I will update this link if I get an answer.
-
I also have the same problems described. New Dell PE2800 with 4GB of RAM running Windows 2000 w/ SP4 and SQL 2000 W/ SP3a. Try to return rows from EM on the test Northwinds db and get the same error. It doesn't matter the database.
-
I have created a case w/ Microsoft thru Dell about this issue. They want me to boot one of my clustered servers into VGA mode and try the same process on a non-clustered database. Unfortunately, my units are in production and to bring one of them down to "test a theory" is not feasable anytime soon. Can one of you who are having this issue, that may not be in production yet, try booting in VGA mode and seeing what happens. Microsoft seems to believe that it may be a corrupted VIDEO driver causing the issue. Our servers were built from the Dell Factory and all we did was load SQL on them and cluster them. So if it's a driver corruption, it's happening during the SQL install, or SP update or a bad driver from Dell.
Please post if anyone can do this.
-
System Details:
- MS Windows 2000 w/ SP4
- MS SQL 2000 w/ SP3a or SP4 (tested with both)
- Dell PE2800
- Built with Dell PowerEdge Installation and Server Management CD Version 4.4 May 2005
Issue:
When in MS SQL Server Enterprise Manager from the console of the server and trying to return all rows from a table (this was for any table in any database including the sample databases) the following error is displayed.
======================
Title: SQL Server Enterprise Manager
Body: An unexepected error happened during this operation.
[MS Design Tools] - Not enough storage is available to complete this operation.
======================
If this same process is ran through MS remote desktop to the server all rows are returned correctly.
Troubleshooting Steps:
- Call was established to MS Support
- Information was exchanged with MS support
- Service pack 4 was applied to resolve issue
- No change
- A reinstall of the SQL client tools was done
- No change
- Server was booted in VGA only mode
- Launched MS SQL Enterprise Manager and return rows from a table correctly.
- Server was rebooted normally
- Call was placed to Dell support
- Wrote driver version number down from Device Manager (6.14.10.6497).
- Downloaded and installed latest driver from Dell support download site (R93282.EXE).
- Rebooted server
- Double checked driver version number from Device Manager again (6.14.10.6497).
- Tested opening a table as described before
- No change
- Dell support sent link to ATI's website to download the latest driver (https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=295). The following is the exact link to the drivers only install that I found off of the link sent by support. (http://www2.ati.com/drivers/5-8_xp-2k_dd_25203.exe).
- Installed DirectX 9.0C
- Rebooted server
- Installed ATI Driver 5-8_xp-2k_dd_25203.exe
- Rebooted server
- Tested opening a table as described before
- All worked correctly.
Issue resolved
-
Are we to take it that it's a driver error on the server and NOT the client that is the cause of this particular issue?
-
Hi, i resolved the problem thanks to Microsoft support. The problem was due to the video driver. The graphical card was an ATI Radeon 7000 and I had the latest driver, that is 6.14.10.6497. I operated a downgrade of the driver to the 6.14.10.6430 version. With this driver the problem was resolved. Thanks you all
-
Okay, so, did you downgrade the driver on your client to resolve the problem?
-
No, I downgraded the driver on the SqlServer Server.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply