Subject | Re: [firebird-support] Mislocated firebird.msg after Backup/Restore |
---|---|
Author | Helen Borrie |
Post date | 2005-12-05T08:09:53Z |
At 07:45 AM 5/12/2005 +0000, you wrote:
interface. The underlying reason for it is that the Firebird server on
server_B was improperly installed. The file firebird.msg *should* be in
c:\Program Files\Firebird\Firebird_1_5 (if this is your Firebird root
directory).
The reason why you get this message about no message file being found in
the C: drive of the client is this: if the message file is missing from
the server (as is the case here) then the client will search a variety of
paths to try to find one that it can use. That location in C:\temp is a
"resort denier" - ultimately it just tells you it can't format the
message. End of story.
logical reason why the installer program would not install everything in
the proper place...
./heLen
>Moin!No. The message doesn't come from the restored database, but from the API
>
>I did a backup of database_3 from notebook_A(Superserver/Local) into a
>transportable file.
>Then I restored this file into database_8 on server_B (ClassicServer)
>from a remote client using IBExpert.
>
>Hence - with every error - I get a message "can't format message
>nn:nnn -- message file C:\Temp\fb\firebird.msg not found.".
>
>But I never had this .msg file on this client before, and never
>received this error before. I even do not have this foldername on my
>client.
>
>BUT (!!!) I do have the folder and the firebird.msg on the notebook,
>from where I made a backup.
>No real danger over here, I just copied the .msg-file into such a
>folder as was demanded by fbclient/IBExpert... but I just suppose that
>I was doing something wrong, OR that there is any bug in
>backing-up/restoring.
interface. The underlying reason for it is that the Firebird server on
server_B was improperly installed. The file firebird.msg *should* be in
c:\Program Files\Firebird\Firebird_1_5 (if this is your Firebird root
directory).
The reason why you get this message about no message file being found in
the C: drive of the client is this: if the message file is missing from
the server (as is the case here) then the client will search a variety of
paths to try to find one that it can use. That location in C:\temp is a
"resort denier" - ultimately it just tells you it can't format the
message. End of story.
>Can somebody please share an idea of what was possibly going wrong here?What procedure did you follow to install Classic on server_B? There is no
logical reason why the installer program would not install everything in
the proper place...
./heLen