Hi
When trying to synchronize users (tools->security->synchronize) I get the ffw error:
"Microsoft Business Solutions-Navision has encoutered a problem and needs to close..."
The only time I have had Navision crash out in that way was when the Role didnt have permission to do something at the time.
For example remove the permission for a user to register time. Then try and change from one company to another in the same database. Rather than give you a message saying you dont have permission, the whole program crashes out.
So there is probably a permission you need to add to your role to be allowed use that sync option. What permission it is I dont know.
Hi
The issue is (partly) solved. It works on an other SQL Server 2000 with SP3 without problem. I therefore guess its a problem with Service Packs.
Regards
Thomas
Hi
I found another interesting fact.
If the db user who has created the db (now the dbo) is added to the database logins in navision, synchronisation is not possible anymore. The Synchronisation stops with the ffw message: The Microsoft Business Solutions-Navision and SQL Server security have not been synchronized successfully. The database user xy does not exist in the database xyz."
Comments
For example remove the permission for a user to register time. Then try and change from one company to another in the same database. Rather than give you a message saying you dont have permission, the whole program crashes out.
So there is probably a permission you need to add to your role to be allowed use that sync option. What permission it is I dont know.
The issue is (partly) solved. It works on an other SQL Server 2000 with SP3 without problem. I therefore guess its a problem with Service Packs.
Regards
Thomas
I found another interesting fact.
If the db user who has created the db (now the dbo) is added to the database logins in navision, synchronisation is not possible anymore. The Synchronisation stops with the ffw message: The Microsoft Business Solutions-Navision and SQL Server security have not been synchronized successfully. The database user xy does not exist in the database xyz."
Has somebody similar experiences?
Thomas
I had to change the database owner using SQL Query Analyzer.
Peter Ng
Funny stuff, I had the same problem today again (as stated in the first message of the thread) with a customer installation. ](*,)
Technical upgrade is not an option at the moment.
Any input on this will be highly appreciated.
Thanks
Thomas
RIS Plus, LLC
You mean a technical upgrade to 4.03?
Thomas
It's like the doctor saying 'take an aspirin and call me in the morning'
RIS Plus, LLC
OK then, I'll tell to the customer:
"'We'll give you an aspirin and call you in the morning"