Microsoft Knowledge Base Email Alertz

(254759) - When you execute the ListAvailableServers method of the SQLDMO.Application object from an ASP page, the following error message may occur: Microsoft SQL-DMO (0x800A000E) [SQL-DMO]Not enough storage is available to complete this operation. /SQLDMO.asp,...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 254759 - Last Review: November 17, 2003 - Revision: 3.1

BUG: ListAvailableServers Method of the SQLDMO.Application Object Causes Error 0x800A000E

This article was previously published under Q254759

SYMPTOMS

When you execute the ListAvailableServers method of the SQLDMO.Application object from an ASP page, the following error message may occur:
Microsoft SQL-DMO (0x800A000E)
[SQL-DMO]Not enough storage is available to complete this operation.
/SQLDMO.asp, line 10

WORKAROUND

This error only occurs when the method is called in server-side scripts. Executing the code using client-side scripts does not cause this error message. For example:
<SCRIPT LANGUAGE="VBScript" FOR=window EVENT=onload>
Dim oDMO, oServers
Set oDMO = CreateObject("SQLDMO.Application")
Set oServers = oDMO.ListAvailableSQLServers()
Msgbox "Total Number of Servers = " & oServers.Count
</SCRIPT>
				

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0.

APPLIES TO
  • Microsoft SQL Server 6.5 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft Active Server Pages 4.0
Keywords: 
kbbug kbpending KB254759
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Anonymous User Report As Irrelevant  
Written: 8/26/2004 9:35 PM
I found that often this message has nothing to do with space available or running scripts on the server or client side. More than ten times I had this problem on workstations with corrupted ODBC installation. Chances are that reinstalling ODBC drivers will help it. Brian Hunter