| Subject | Re: [firebird-support] Re: Mislocated firebird.msg after Backup/Restore |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-12-05T21:05:55Z |
At 02:28 PM 5/12/2005 +0000, you wrote:
database header or the system tables; and, anyway, the database header
doesn't store anything that relates to where the pieces of the server
should be. C'est-a-dire, the database doesn't store any knowledge of the
host's filesystem, except in the case of multi-file databases, where the
primary file stores links to the secondary files. However, these links are
not stored in a backup.
What's likely here is that IBExpert has a hard-coded path that it installs
somehow (perhaps in the Registry or in an ini file) when it discovers that
firebird.msg and firebird.log are not where they should be. I can't guess
the logic, though. Ask Holger on firebird-tools....
root directory and actually runs instreg.exe itself, with its own
parameters, if it finds the key is missing or invalid. Did you move the
root directory from the original installation path without running
instreg.exe? Or installed Firebird from the .zip kit without running instreg?
Also, I suppose you know that having the matching versions of client
library, message file and server is the only way to guarantee correct
message decoding....?
./heLen
>--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>Coincidence, for sure. User applications don't write things in the
>wrote:
>
>Thanks for your answer, Helen, but there must still be something
>amiss. And I have such an impression that it is connected with
>IBExpert, rather than with Firebird itself.
>
>Sorry, but only now did I have the idea of trying to reproduce the
>same error with other software; and.... no error-message... happens
>only with IBExpert, although I don't understand how that could be.
database header or the system tables; and, anyway, the database header
doesn't store anything that relates to where the pieces of the server
should be. C'est-a-dire, the database doesn't store any knowledge of the
host's filesystem, except in the case of multi-file databases, where the
primary file stores links to the secondary files. However, these links are
not stored in a backup.
What's likely here is that IBExpert has a hard-coded path that it installs
somehow (perhaps in the Registry or in an ini file) when it discovers that
firebird.msg and firebird.log are not where they should be. I can't guess
the logic, though. Ask Holger on firebird-tools....
>My root directory on/for the classic server is: c:\system\firebirdIt's possible, then, that IBExpert relies on the Registry key to find the
>and the "firebird.msg" _is_ there.
>And it always was there, and before restoring this very backup, I
>never had this error-message.
>And if I do copy exactly this "firebird.msg" into a local folder
>"c:\temp\fb" which never existed before, then the error-message does
>not occur.
>Now, in the same folder, suddenly also appears the firebird.log-file
root directory and actually runs instreg.exe itself, with its own
parameters, if it finds the key is missing or invalid. Did you move the
root directory from the original installation path without running
instreg.exe? Or installed Firebird from the .zip kit without running instreg?
Also, I suppose you know that having the matching versions of client
library, message file and server is the only way to guarantee correct
message decoding....?
./heLen