Error: "There is not enough memory to complete the current activity" When open a report 3 times:

(0) Share

Report

Posted on by Community Member

Hello,

I got error: "There is not enough memory to complete the current activity" when I tried to open (double click) the same report 3 times simultaneously despite the fact that I even not yet run the report - just double click on it.

Do you have any ideas why I got this error ?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Nareshwar Raju Vane... 5,596 on at

Like (1)

Report

Hi,

This message is from SQL Server Backend. Which report did you try to run?

There can be many instances why this kind of error messages can happen.

Low disk/ram space.

There can be simultaneous users connected to NAV.

Do heavy tasks like Posting / Cost Adjustments / Other customizations and integrations.

Like this, there can be many more. Please do check and try to replicate the error again.

Extra: It was hotfixed in NAV 2013 CU 16. Not sure about NA 2009 :)

Link: mbs2.microsoft.com/.../KBDisplay.aspx

Hope it helps.

Was this reply helpful? Yes No
Suggested answer

Suresh Kulla 50,245 Super User 2025 Season 2 on at

Like (0)

Report

Is it a custom report ? and does it happen with other reports or just with this report ? If so check if there is any code on the Request Form or Page of the Report

Was this reply helpful? Yes No
Suggested answer

Amol Salvi 18,698 on at

Like (0)

Report

Kindly check the report whether is it running without any filters . Kindly try to run the report with some filters as well as check the report layout whether any expression is not correct.

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

It might happen due to poor design of the report itself - it might consume all the resources and still not be processed, or the processing goes to infinite loop. Check if the report has been customized or not. Also, try running the report from different users. Also, try running report not from client computer but from server using RDP. Try running in a different time. Check what is in general the memory status for SQL; try rebooting the server - would it show the same result?

Was this reply helpful? Yes No