--- In firebird-support@yahoogroups.com, Sam Hunt <shunt@n...> wrote:

> Helen Borrie wrote:
>
> >At 12:37 AM 28/05/2005 +0000, you wrote:
> >
> >
> >>I just installed SS 152 4731 on a server running XP and I get this
> >>error when I run my D7/ADO app against the DBs. Every other
> >>aspect of this install is exactly the same as the dev pc. (DS
> >>names/definitions, etc.) The connection string is U:\MyDatabase.
> >>fdb, where "U" is a mapped network drive pointing to a "D"
> >>partition on my local drive.
> >
> >This is your problem. You can't connect to a mapped drive AT ALL.
> >The connection string must be an absolute file path as seen locally
> >by the server.
> >
> >>"U" is a partition on the new app pc. The ODBC manager test
> >>connection worked fine on both machines using TCPIP.
> >
> >If "U:" is ***also*** a partition designation on the server (i.e.
> >not a mapping to a partition that has a different name) then the
> >correct TCP/IP string for remote connections will be:
> >
> >servername:U:\absolute\path\to\database\MyDatabase.fdb
> >
> >>I had this exact same problem on a laptop and a workstation here
> >>at work, and solved it by rebooting the machines.
>
> I think I provided TMI. The machine I am having trouble with uses a
> partition drive U (not a mapped drive) for FB152 4731 and the app.
> However, I still got the "UNAVAILABLE DATABASE" error. Like I
> stated in my first post, I have experienced this error three times
> b4 (not immediately after an install, but on machines that had
> successfully run FB against this same app) and rebooting the pcs
> solved the problem. Why, I do not know. These 3 problem pcs were
> all running FB and the app from their own drv C.
> Sam H.

Could it be due to file system backup or virus scanning at the time
you try to connect to the database (or worse, a restore taking place)?
Just a wild guess, I've no reason for asking this.

Set