|
| 1 | +Firebird Database Server $MAJOR.$MINOR.$RELEASE |
| 2 | +=============================================== |
| 3 | + |
| 4 | + |
| 5 | +This document is a guide to installing this package of |
| 6 | +Firebird $MAJOR.$MINOR on the Windows platform. These notes refer |
| 7 | +to the installation package itself, rather than |
| 8 | +Firebird $MAJOR.$MINOR in general. In addition, these notes are |
| 9 | +primarily aimed at users of the binary installer. |
| 10 | + |
| 11 | +It is assumed that readers of this document are already |
| 12 | +familiar with Firebird. If you are evaluating Firebird $MAJOR.$MINOR |
| 13 | +as part of a migration from some older Firebird version you are advised |
| 14 | +to review the Firebird $MAJOR.$MINOR documentation to understand |
| 15 | +the changes made between your version and $MAJOR.$MINOR. |
| 16 | + |
| 17 | + |
| 18 | +Contents |
| 19 | +-------- |
| 20 | + |
| 21 | +o Before installation |
| 22 | +o Deployment of gds32.dll |
| 23 | +o Installation of the Guardian |
| 24 | +o Re-installation of Firebird $MAJOR.$MINOR |
| 25 | +o Known installation problems |
| 26 | +o Uninstallation |
| 27 | +o Installation from a batch file |
| 28 | + |
| 29 | + |
| 30 | +Before installation |
| 31 | +------------------- |
| 32 | + |
| 33 | +It is recommended that you UNINSTALL all previous |
| 34 | +versions of Firebird or InterBase before installing |
| 35 | +this package. It is especially important to verify that |
| 36 | +fbclient.dll and gds32.dll are removed from <system32>. |
| 37 | +See the UNINSTALL section below for more info on this. |
| 38 | + |
| 39 | + |
| 40 | +Installation of the Guardian |
| 41 | +---------------------------- |
| 42 | + |
| 43 | +We are hoping to phase out the Guardian. It doesn't |
| 44 | +work with the Classic server and the binary installer |
| 45 | +does not offer it at install time if Classic is |
| 46 | +chosen. If SuperServer or SuperClassic are chosen |
| 47 | +it is offered but not selected by default. |
| 48 | + |
| 49 | + |
| 50 | +Re-installation of Firebird |
| 51 | +--------------------------- |
| 52 | + |
| 53 | +The binary installer does its best to detect and |
| 54 | +preserve a previous install. If the installer detects |
| 55 | +firebird.conf or security$MAJOR.fdb it will not offer the |
| 56 | +option to set the SYSDBA username and password. |
| 57 | + |
| 58 | + |
| 59 | +Known installation problems |
| 60 | +--------------------------------- |
| 61 | + |
| 62 | +o It is only possible to use the binary installer |
| 63 | + to install the default instance of Firebird $MAJOR.$MINOR. If |
| 64 | + you wish to install additional, named instances you |
| 65 | + should manually install them with the zipped install |
| 66 | + image. |
| 67 | + |
| 68 | +o Unfortunately, the installer cannot reliably detect |
| 69 | + if a previous version of Firebird Classic server |
| 70 | + is running. |
| 71 | + |
| 72 | +o The service installer (instsvc) uses the same |
| 73 | + default instance name for 32-bit and 64-bit |
| 74 | + installations. This is by design. Services exist |
| 75 | + in a single name space. |
| 76 | + |
| 77 | +o Be sure to install as an administrator. ie, if |
| 78 | + using the binary installer right click and choose |
| 79 | + 'Run as administrator'. Otherwise the installer |
| 80 | + may be unable to start the Firebird service at |
| 81 | + the end of installation. |
| 82 | + |
| 83 | +o Installation may fail on older versions of windows up |
| 84 | + to Win 8.1 and Windows Server 2008 if the most recent |
| 85 | + security updates have not been installed. This will |
| 86 | + also affect users of the zip packs as the problem |
| 87 | + lies with runtime library dependencies of |
| 88 | + applications such as instclient and instsvc. |
| 89 | + |
| 90 | + If you do run into this problem you should consult |
| 91 | + the microsoft knowledge base article KB2999226 for more |
| 92 | + information on how to upgrade your version of windows |
| 93 | + to use the latest run time libraries. |
| 94 | + |
| 95 | + |
| 96 | +Uninstallation |
| 97 | +-------------- |
| 98 | + |
| 99 | +o It is preferred that this package be uninstalled |
| 100 | + correctly using the uninstallation application |
| 101 | + supplied. This can be called from the Control Panel. |
| 102 | + Alternatively it can be uninstalled by running |
| 103 | + unins000.exe directly from the installation |
| 104 | + directory. |
| 105 | + |
| 106 | +o If Firebird is running as an application (instead of |
| 107 | + as a service) it is recommended that you manually |
| 108 | + stop the server before running the uninstaller. This |
| 109 | + is because the uninstaller cannot stop a running |
| 110 | + application. If a server is running during the |
| 111 | + uninstall the uninstall will complete with errors. |
| 112 | + You will have to delete the remnants by hand. |
| 113 | + |
| 114 | +o Uninstallation leaves six files in the install |
| 115 | + directory: |
| 116 | + |
| 117 | + - databases.conf |
| 118 | + - firebird.conf |
| 119 | + - fbtrace.conf |
| 120 | + - replication.conf |
| 121 | + - firebird.log |
| 122 | + - security$MAJOR.fdb |
| 123 | + |
| 124 | + This is intentional. These files are all |
| 125 | + potentially modifiable by users and may be required |
| 126 | + if Firebird is re-installed in the future. They can |
| 127 | + be deleted if no longer required. |
| 128 | + |
| 129 | +o A new feature of the uninstaller is an option to |
| 130 | + run it with the /CLEAN parameter. This will check |
| 131 | + the shared file count of each of the above files. If |
| 132 | + possible it will delete them. |
| 133 | + |
| 134 | + |
| 135 | +Installation from a batch file |
| 136 | +------------------------------ |
| 137 | + |
| 138 | +The setup program can be run from a batch file. |
| 139 | +Please see this document: |
| 140 | + |
| 141 | + installation_scripted.txt |
| 142 | + |
| 143 | +for full details. |
| 144 | + |
0 commit comments