"Insufficent memory for this operation"
"Insufficent memory for this operation"
I've got an app which has been tested on Server 2003, Vista and XP and working fine (no requirement for Win7) but I'm having an issue on Windows Server 2008 Enterprise Edition.
In each case it's a standalone single user, i.e. localhost database, devart driver, midas.dll and my exe.
I'm doing a selective load of data into an empty table and it fails with this popup message (the banner is "error occurred"). It occurs in exactly the same place in the data.
Each record is doing an myDataSet.ApplyUpdates(-1), after 11,110 records it suddenly decides I can't do "InsertRecord()". No exception is thrown so I can't handle the error.
Is this messge coming from the driver ?
I haven't seen anything about being restricted to certain versions of windows. I've no need to go prior to XP, but the customer wants to run on his servers....
It's quite happily loaded around 240,000 of these records on my humble desktop. They have around a dozen fields, nearly all short text strings (no blobs etc.)
Anyone seen this problem ?
In each case it's a standalone single user, i.e. localhost database, devart driver, midas.dll and my exe.
I'm doing a selective load of data into an empty table and it fails with this popup message (the banner is "error occurred"). It occurs in exactly the same place in the data.
Each record is doing an myDataSet.ApplyUpdates(-1), after 11,110 records it suddenly decides I can't do "InsertRecord()". No exception is thrown so I can't handle the error.
Is this messge coming from the driver ?
I haven't seen anything about being restricted to certain versions of windows. I've no need to go prior to XP, but the customer wants to run on his servers....
It's quite happily loaded around 240,000 of these records on my humble desktop. They have around a dozen fields, nearly all short text strings (no blobs etc.)
Anyone seen this problem ?
Sorry - I can't do that it's client confidential data. I'll try and make a stripped down version with some dummy data and see if I can get that to fail.
Incidentally the customer has 32bit not 64. I think the message is coming from Windows and not your driver, but was wondering if you'd seen it.
Mark
Incidentally the customer has 32bit not 64. I think the message is coming from Windows and not your driver, but was wondering if you'd seen it.
Mark
Hello,
I've got your test application, but I still cannot reproduce the problem.
Please try to learn the amount of memory available on your client's machine and also check the amount of memory used by your application when inserting records.
If it turns out that there is not enough memory, you can reduce the amount of the needed memory by using parametrized Insert query instead of opening DataSet – it will significantly reduce the size of the needed memory.
I've got your test application, but I still cannot reproduce the problem.
Please try to learn the amount of memory available on your client's machine and also check the amount of memory used by your application when inserting records.
If it turns out that there is not enough memory, you can reduce the amount of the needed memory by using parametrized Insert query instead of opening DataSet – it will significantly reduce the size of the needed memory.
Thanks.
I'll get back to you on the RAM, it's "adequate". The machine is working as a big server and has way more memory than any of the other machines it has worked on.
I think the issue is one of Windows resources, what you have confirmed for me is that it should work on the Win Server 2008 and that I haven't done anything obviously wrong.
Thanks
Mark
I'll get back to you on the RAM, it's "adequate". The machine is working as a big server and has way more memory than any of the other machines it has worked on.
I think the issue is one of Windows resources, what you have confirmed for me is that it should work on the Win Server 2008 and that I haven't done anything obviously wrong.
Thanks
Mark
8Gb. It's run quite happily on 2 and 4Gb machines. The entire file it's trying to load is only 45Mb at it falls over before it's reached 10%.
So the problem lies elsewhere. The customer is about to try it on another of his servers, so it may be a case of just ignoring that machine while we get the job done.
Thanks for your help.
Mark
So the problem lies elsewhere. The customer is about to try it on another of his servers, so it may be a case of just ignoring that machine while we get the job done.
Thanks for your help.
Mark