Error 1355 in module 19

geja

Hi,

We are using Attain 3.1 and we constantly experience this error when running MRP. It doesn't have a consistent way of occuring though as it may pop up at the start of the process or in the middle. I noticed this because the progress bar of the MRP run may already be in 33% level when the error occurs but when I rerun the process, it may occur already earlier than this. The error window recommends that we talk to the system provider but my experience with them is that they would ask us to wait while they study the problem and I though I may as well ask here first.

Thanks.

fb

See http://www.mibuso.com/forum/viewtopic.php?t=1207 -- especially the following post:

found this regarding error 1355 in module 19. Maybe you can make sence of it..................

The short description for this error is "DBM not re-entrant".

The most common situation for it is that a function (say f1) in the database layer on the client, is executing a database command (op1) that requires a "server dialog". This is just a message giving feedback about what is going on - it can be a true dialog box, like that used for creating an index, or a status bar message like that used for counting records. The server (this can be just dbm.dll locally) tells the client that op1 is taking more than 200ms or so and that a server dialog should be thrown up to give the user some feedback. The point about it, though, is that it is created on a separate thread that now enters a windows message loop. Once you're in this loop, many messages gernated both by windows (in response the painting and the user's actions) and by Navision internally are read off the queue and processed. Sometimes a message will cause more code to execute on the client (such as doing a record FIND). If this happens, the client database layer is called again with database operation op2 and eventually we get down to function f1 again but on the new thread. Function f1 has already noted that it is currently executing on an original thread, trying to execute database operation op1. However, function f1 is not re-entrant - it cannot be re-executed by a different thread for any reason (the database code is protecting itself from bad callers) - it should never happen and this is the error.

The problem is that the UI message processing in Navision should never have picked off messages from the message loop while processing the server dialog that did not belong to the server dialog alone. Unfortunately it does, and the other messages lead to further database operations - and bang.

As of 3.70, this error is still possible but should be fixed soon. There was a hotfix for 3.10 that addressed it and reduced it, but did not solve it.

dmccrae

This is now fixed in hotfixes for 3.10A, 3.60 and 3.70. Getting the latest hotfix for your version should help you.

There is still a situation that can provoke the error, but it is rather obscure and involves changing Control Panel settings whilst Navision is executing database commands. I don't think you'll get this with your scenario.

fkryszon

running v3.10A this error seems to appear while using the scroll-bar
while using "Page Up/Down" sems 2 work

just my 2 cents

Savatage

We use 3.10b database with 3.6 executables.

We had this problem forever until Hotfix 23 for 3.6

P2) Internal Error 1355 in Module 19
Error
An internal error message “Error 1355 in Module 19” could occur in the Navision client in several scenarios including:
• Performing lengthy database operations such as creating indexes
• Waiting for table locks placed by other users during normal database activity
This has been corrected
Service System reference: AU-614-161-9U2T