Error [IM003] System error 8 - when trying to print a report

Dear All,

I just wanted to share a solution that took me almost a month to solve, if you have come across this error, I would be very interested to hear how you have solved it.

SAGE Support was unable to help, and had no knowledgebase notes on the subject. So having spent almost £ 2000 of IT support and several weeks searching for a solution, I feel I should share my efforts.

We are using CITRIX on a remote server environment, and Office 365 online using SAGE Line 50, Version 22

The error appears to be on ODBC error, but it is more likely to be a "share" network error.

The solution is to set the registry value of "IRPStackSize" to a higher value
(I have set it to the maximum of 50 decimal)

Solution: Youtube video + notes

https://www.youtube.com/watch?v=ct4OXRB8vtk

https://ignitedsoul.com/2012/10/09/system-error-8-not-enough-storage-is-available-to-process-this-command/

  1. IRPStackSize
  2. Go to the below Registry entry to edit the IRPStackSize

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

If you do not have the Registry entry then create one manually, but make sure the name should be correct as it is case sensitive.

To create the Registry entry follow the below steps:

–          Open REGEDIT

–          Proceed to the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

–          Click Edit, and point to New and then click DWORD Value

–          Type IRPStackSize , Click Edit and then modify the Value

–          The Value should be 0x00000050 in Hexadecimal or 80 in Decimal. This should resolve your issue, normally values are provided to 1 to 15 in decimal notation. Better if you provide higher value so that the problem doesn’t come back.

–          Restart the Server after the changes are done.

  • Hi Moiz,

    Thanks for your tip.I have passed this over to our Research & Development team. We'll see if we can recreate this and then amend our articles.

    We don't support the software on Citrix or terminal server environments, this is possible why a technician couldn't assist any further with his.

    We do have the following Ask Sage article on this error, which covers a reboot and reinstalling ODBC.

    my.sage.co.uk/.../askarticle.aspx

    Thanks again for you tip Moiz, this is really appreciated.

    Thanks,

    Brian
  • Hi Brian,

    The error started after upgrading Sage Line 50 from V 20 to V 22 and Office from 2010 to 2016

    At first I also reinstalled the ODBC drivers, the strange thing was that some users could print and others (including me) could not (the same reports eg.invoices)

    I searched on google for the IM003 error, than narrowed it down to system error 8 and than the solution modifying IRPStackSize on the registry, and restarted the server.

    It took me days, I am not sure that this is the only solution, but it seems to work.

    Moiz
  • Moiz,

    I have a similar problem, in that when I try to update data I have imported into Excel using ODBC I get the following error:

    'Specified driver could not be loaded due to system error 8: Not enough storage is available to process this command. (Sage Line 50 v21, C:\\Windows\SysWOW64\S21DBC32.dll).'

    However, your solution hasn't worked for me.

    I tried creating this registry entry on both my server and my PC (I wasn't sure which, so did both), but I'm still getting the error. If you or anyone out there has another solution, I'd be VERY glad to hear it! We use ODBC a lot for extracting data for reporting but over the last 18 months I haven't been able to find a solution that works.

    Thanks in advance,

    Clive
  • Clive

    We also suddenly got this problem on the more intensive queries (having previously used OBDC into Excel successfully for a long time).

    On ours, it was because 32-bit Excel does not "allocate itself" enough resources to complete the demanding query. I got round it on ours using the advice on this forum, www.mrexcel.com/.../438142-set-priority-shell-command-visual-basic-applications.html , basically its code that gives Excel higher processing priority when it opens, then it can cope with the query.

    However you would want to be careful it does not give you system instability etc, (it's been fine for us but I understand that it can have side effects).

    All the best

    Lyndon