internal error 1 and 2 in module 5 and 7

jazzyjess

We have just upgraded our client to 4.0 SP1 and it had been deployed last week. However, we have one nagging problem right now, when closing Navision client, we keep getting these 2 errors:

Internal error 1 in module 5
Internal error 2 in module 7.

Are these errors NAS related?

I searched the forum, and found that some ppl had the same problem too, but there was no solution so far?

THanks in advance.

JJ

kine

Try to check your CU1 if you have some custom global variables. If yes, try to define them as local. Some triggers have problems with global variables in CU1...

Timo_Lässer

It could be that you call a codeunit from CU1 which is not defined as SingleInstance.
There are two solutions:
1. Put the neccessary functions from the external codeunit into CU1
2. Define the codeunit you are calling as SingleInstance

jazzyjess

thank you very much, we tried the suggestion, and the problem is fixed !

Thanks
JJ

Savatage

It would be great if you placed [Solved] in the post's topic \:D/

Arhontis

Hi,

I have encountered another time those errors:

Internal error 1 in module 5
Internal error 2 in module 7.

So I post it here for future reference.. Maybe it will help someone else...

I was using Nav 4.0 SP2 as a client with the hotfix about the page markings (272944_intl_i386) but I wasn't using the updated nassql.exe and the dlls for the NAS.

The NAS worked fine, but when tried to stop the service I got those error messages.

After overwritting the files (nassql and dlls) and used the new from the hotfix, it worked fine...
[/code]

anon2132

Also before you go delving into codeunit 1, you might try adding an id to your shortcut (which creates a new zup):

Previously:
"C:\Program Files\Microsoft Business Solutions-Navision\Client\fin.exe"

And now:
"C:\Program Files\Microsoft Business Solutions-Navision\Client\fin.exe" id=2

This did the trick for me.

David_Singleton

anon2132 wrote:

Also before you go delving into codeunit 1, you might try adding an id to your shortcut (which creates a new zup):

Lets hope that the issue was already resolved, other wise I am sure the users would be getting a little bit angry by now :whistle: