-
[quote user="Rashed"]somebody probably ran security sync and wasn't part of a dbowner and security admin role. This will cause it to delete the user since the user can't see if they real users. In the latest exe it checks that you have right permission before running sync. [/quote]...
-
[quote user="Rashed"]somebody probably ran security sync and wasn't part of a dbowner and security admin role. This will cause it to delete the user since the user can't see if they real users. In the latest exe it checks that you have right permission before running sync. [/quote]...
-
If you have Navision 4.00SP3 or 5.00, you can put the Security level to Standard (and not Enhanced). With this you don't need Synchronization anymore. Synchronization has to be done everytime an object is added or something in the security is changed.
-
[quote user="Nuno Maia"] David, During your error fix, were you able to run 3.70 with SQL 2005 ? [/quote] By the time I got it all working, I had already converted to 4.00SP3. But I don;t think there would be a problem with 3.70, and I will try that next time.
-
[quote user="Jörg Stryk"] Hi David! Once, I encountered similar problems; means that after a failed conversion of a database, I got the same error as you described. The problem is, that the column "securityoption" was added to $ndo$dbproperty with the first attepmt, after failure...
-
Hi David! Once, I encountered similar problems; means that after a failed conversion of a database, I got the same error as you described. The problem is, that the column "securityoption" was added to $ndo$dbproperty with the first attepmt, after failure the column still remained, thus the...
-
[quote user="Nuno Maia"] SQL server 2005 has a different security model and Navision below 4.0 SP3 is incompatible. I already a similar issue when making a db conversion from 3.70B SQL 2000 to 4.0 SP3 in SQL 2005 (DB objects are still from 3.70B). The only way I solved was to restore using...
-
SQL server 2005 has a different security model and Navision below 4.0 SP3 is incompatible. I already a similar issue when making a db conversion from 3.70B SQL 2000 to 4.0 SP3 in SQL 2005 (DB objects are still from 3.70B). The only way I solved was to restore using Navision Client and not using SQL Server...
-
I am having trouble restoring a database, and hope someone can give me some help. (Note this is not a live scenario, its just for me to create a local live system, so it doesn't need to be perfect, it just needs to work). The client it on 3.70B running on SQL server 2000. From this database they...
-
I really can recommend you to read this whitepaper document: Security Synchronization in Navision 4.0 SP3