Prev: navision .fbk -->MsSQL
Next: 100% agree! : Produce a quality set of manuals.
From: Luke Stokes on 19 May 2005 12:52
We went through the drama of upgrading to 4.00 improvement 1 SQL Navision
Navigator. After a day or two we figured out why we were having so many
security issues and we had to add everyone to db_owner. Now we have another
problem:

A majority of the time we close Navision and sometimes when we just close a
form we get the following errors:

Internal error 1 in Module 5.
Contact your dealer if you need assistance.

This is then followed by:

Internal error 2 in Module 7.
Contact your dealer if you need assistance.

What can be done to fix this?

Again, we're using the SQL version of Navision Navigator, 4.00 improvement 1.
From: jouhayna on 20 May 2005 09:41
You don't have to add db_owner for each one ...

I suffered a lot of this drama but now it's perfect ....

But tell me first are you still keeping V3.6 on same SQL ?


"Luke Stokes" <LukeStokes(a)discussions.microsoft.com> wrote in message
news:0BD41076-1D58-4D8C-B969-F5A869632CF4(a)microsoft.com...
> We went through the drama of upgrading to 4.00 improvement 1 SQL Navision
> Navigator. After a day or two we figured out why we were having so many
> security issues and we had to add everyone to db_owner. Now we have
> another
> problem:
>
> A majority of the time we close Navision and sometimes when we just close
> a
> form we get the following errors:
>
> Internal error 1 in Module 5.
> Contact your dealer if you need assistance.
>
> This is then followed by:
>
> Internal error 2 in Module 7.
> Contact your dealer if you need assistance.
>
> What can be done to fix this?
>
> Again, we're using the SQL version of Navision Navigator, 4.00 improvement
> 1.


 | 
Pages: 1
Prev: navision .fbk -->MsSQL
Next: 100% agree! : Produce a quality set of manuals.