asked on

msxml3.dll: Not enough storage is available to complete this operation

I have written one schedule agent which runs on domino server. The same code worked fine in the development and staging environment.

When the I same code ran on production server, I am getting the following error

msxml3.dll: Not enough storage is available to complete this operation

Set xmlhttp = CreateObject("Msxml2.ServerXMLHTTP")						xmlhttp.setOption 2, 13056
Call xmlhttp.open("GET", docConfig.US_XML_Address(0), False)	
Call xmlhttp.send()		
While (xmlhttp.readyState<>4)
xmlhttp.waitForResponse(1000)      
Wend				
srcStatus = xmlhttp.status
If srcStatus = "200" Then
srcHTML = xmlhttp.responseText

Set xmlDoc = CreateObject("Msxml2.DOMDocument")
	xmlDoc.async = False
	bFlag=xmlDoc.loadXML (srcHTML)

Open in new window

Ted Bouskill

Is the XML on the development and staging environment the same size?

What about the memory capacity of the development and staging capacity compared to production?

XML is verbose and you are loading the entire blob into memory.

gattuba

ASKER

Hi,

Yes, XML is all most same size. As I know that production servers are having good amount of memory capacity than development and staging environment.

XML size is 3,922,566 bytes and I am loading this into memory.

Thank You,
Bala

Ted Bouskill

3 MB isn't that bad for a document. I suspect the error isn't about memory and is one of the cases where a different problem is being caught by the wrong exception handler.

Is there any other logs you've inspected?

gattuba

ASKER

Hi Tedbilly,

I have maintained the log and I have got following error.

Error in Initialize() - Error Number: 213 -- Error Text: msxml3.dll: Not enough storage is available to complete this operation. -- Line Number: 330

Line Number: 330 is srcHTML = xmlhttp.responseText

Note:
(set xmlhttp = CreateObject("Msxml2.ServerXMLHTTP"))

Thank You,
Bala

Ted Bouskill

Have you tried with smaller files to see if there are any other issues?

gattuba

ASKER

I have tried with smaller files and this error is not coming.

Ted Bouskill

It might not be the file size either. It could be one badly formatted record that is the problem. Did you use the exact same XML in staging and development?

To find the threshold for failure I'd recommend a divide and conquer strategy.

If your successful file was 1KB and the failed file is 4 MB do this.

Try 2 MB, if success try 3 MB else failed using 1 MB.

Keep repeating by using 1/2 the distance until you fail. Once we have a file limit we might be able to track if there is a setting or specific condition that is the problem.

gattuba

ASKER

When we were doing the staging / UAT testing we have a business request to upload all the production data in these environment, it was fine and the same xml we are using in production

I do not think it is because of that since I have provided the check whether xml load is success or not, if not it creates the log with line which is causing problem.

Ted Bouskill

We still need to determine the practical limit that is causing the problem.

gattuba

ASKER

Schedule agent ran successfully on the server and I did not get that error this time. I am not able to understand why some times I am getting that error message and sometimes not.

ASKER CERTIFIED SOLUTION

Ted Bouskill

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial