This error can be caused for a number of reasons. One of the common ones is as Nuno mentions about permission to the drive. Since D: is probably a local drive it is probably not, but in any case you should always install the Navision server logged in as Admin.
Another common cause of this error, is a misinterpretation of the file name. Firstly what is the actual error message. It could be that the “…” part of the “d:…\database.fdb” is thebit that counts, so please can you give the entire message.
Anyway, in some cases, the install process messes up if the database name has spaces in it, such as “D:\My Database Directory\database.fdb” you can find this out by looking at the registry entry where database.fdb is, an dsee if it “looks right”, ofeten you may see an entry such as ““D:\My Database Directory\database.fdb”” (that is two double quotes “” instead of one " ) this can be fixed with reg edit, BUT I have found that often if you have this error, you need to completely clean the registry before it will install, and if you already have a running Navision server on the machine, that is dangerous. But if you have no other solution, then here is how to fix it:
- Uninstall any and ALL versions of Navision client on the machine.
- Uninstall any and ALL versions of Navision server on the machine.
- Use a registry cleaner to clean up any Navision registry entries.
- Manually search the registry and remove all references to Navision.
- Install Navision server using normal install process for your first server (the one that currently works).
- Copy the Navision server folder for the new server.
- Run Server.exe from the second server folder with all the appropriate parameters.
- stop the service
- run server.exe with the parameter “installasservice”
- Reboot and all should work.
- If so you can now install the Navision client.
Just one point: I have never seen this error happen unless the Client is installed on the server.
The above process is also used to fix an error that you can’t start the service with Commit cache enabled.
Oh, and in many cases, a quicker process than the above, is to format the C: drive and reinstall Windows Server.