During mirror initialization your may get one of the following messages:
- This database is registered with several NAV Server instances. You must choose an instance to use before performing this activity. Do you want to continue?
- A service tier could not be contacted by the development environment (finsql.exe). Please open finsql.exe directly (without the id parameter), and select a service tier under menu 'File | Database | Information'. Then close the development environment again and synchronize the mirror again
- There are no NAV Server instances available for this database
- This database is registered with several NAV Server instances. You must choose an instance to use before performing this activity. Do you want to continue?>/li>
The issue is that mirror synchronization uses the finsql.exe command-line, which (for some reason unknown to us) needs to connect to a service tier in order to export objects as txt files. This requires that the database "knows" which service tier to connect to. C/SIDE stores this information in the default zup-file.
Here is how you let C/SIDE know which (unique) service tier to connect to:
- Close all classic clients that you have open for the database
- Open classic client; this must be the exact finsql.exe that you have specified in the mirror configuration
- Open menu: File | Database | Information
- In the field "Server Instance", choose a service tier
- Close classic client
- In Prism, open the mirror manager and press the "Synchronize all mirrors now" button
- When synchronization has finished, you should be able to open the mirror. If not, please let us know via the built-in feedback facility (Help | Feedback...)
Object permission issues
Mirror synchronization uses the finsql.exe command-line to export objects as txt files. The export command uses the NAV license uploaded to the database, so if license does not permit to export an object as txt, then you will get a message like this:
- You do not have permission to read the <object name>' <object type>. Contact your system administrator to have your permissions changed.
If you get a message like this during mirror synchronizationand and you haveuploaded the correct NAV license to the databae, then do the following:
- If the NAV version is 2015, then change the mirror adapter to Nav2015Adapte; the Nav2015Adapter automatically deals with unlicensed objects via the undocumented finsql.exe command-line option named ExportTxtSkipUnlicensed
- If the NAV version is 2013, then change the "Object ID Include Filter" of the mirror to only include objects that are definitely licensed for export. When the initialization has finished successfully, you can relax the filter to include more objects. (On subsequent synchronizations, synchronization will not fail if an object is unlicensed. Instead, the mirror will remember that the object is unlicensed and not try to export from NAV again)