Not enough quota is available to process this command.

[dawnw]

Has anyone seen these errors and know what it could cause it?  I don't have the application on had to test but it is necessarilly repeatable.  Occurred after the application was running for a number of hours.

A dialog window with the following information:

Unspecified error occurred.

VI “RecipeStep.vi” was stopped at node 0x0 of subvi “DAQmx Clear Task.vi:1”

This was procedded with another error that would not allow any operation to occur to the machine.  

Not enough quota is available to process this command,

[pincpanter]

"Not enough quota is available to process this command" is a rather obscure Windows error message. Your program ran out of resources. I don't know exactly which resources, but they should be related to virtual memory and paging file. The concise description given by Microsoft suggests to increase the paging file size, however this may only delay the occurrence of the error if the lack of resources is due to some critical part of the program (open too many files and not close them? allocate too much memory? ...?) Can you give more details on what the program does?

[dawnw]

It is a cycle test fixture that moves a couple Linmots using serial commands, tests communication with the fixtures Aux and IP ports (pings and writes serial command for response), and turns some IO on and off using NI IO card.

No external routines have been introduced to program.  Using Labview 8 Advanced Serial VI and Ping VI.

Thanks!

[pincpanter]

Are you opening resources (files, connections) that are not closed at the end of each cycle? Certainly, a look at the code could be useful.
One suggestion is to use the built in Windows performance monitor (Control Panel ->Administration Tools -> Performance) to verify if a system resource usage is continuously growing. Another useful tool is the Process Monitor ( http://www.microsoft.com/technet/sysinternals/SystemInformation/processmonitor.mspx ) that lets you monitor only your process, although the monitored items are limited. Pay attention especially to paging file and the process working set.

Message Edited by pincpanter on 07-12-2007 04:58 PM

Message Edited by pincpanter on 07-12-2007 05:01 PM

[dawnw]

I looked at all the Labview sample communication vi's I am using and they all close and do cleanup.  I write to a text files and the text files are closed.

The task mentioned above (DAQmx Stop) is in the IO read/write Vi's.  I will attach.  Although, I also realize problem could be caused somewhere else and this may just be where it stopped.

[mikeporter]

While your application is running watch the amount of memory LV is using in the Task Manager. If this value is creeping up over time you have a memory leak in your code. Two common places are references (of any kind) that don't get closed, and arrays that aren't reinitialized appropriately.

Mike...

PS: If you stop your applications for a few hours, but before it errors out, how long does it take to stop the application and shutdown LV?

[dawnw]

Everything shuts down right away.

[mikeporter]

Then I think I would be looking for an over-grown array. If the memory leak is due to references being left open LV closes all of them before it shutsdown, and in the past I have seen this process take anywhere from a few minutes to more than an hour.

Mike...

[pincpanter]

Yes, the offending code may be elsewhere, not necessarily into the DAQmx vi's.
However I have a suggestion about the uploaded code: you may try to only Stop the task instead of clearing it, and delay clearing until the final program cleanup.
In principle this should not make a big difference, only a slight optimization, but who knows...?

[dawnw]

I'll look into both.

Thanks!