English > Support

Cannot connect to database

(1/3) > >>

rick.ca:
My new computer finally arrived. I'm struggling with Vista x64 while waiting for my Win7 upgrade. (I know, it was released a month ago! I'll never buy a Dell again...) As if that's not enough, I can't get PvdImport working—or PVD to load while it's running. Trying to run PVD when PvdImport is connected to the database causes this error...

1:I/O error for file "C:\Data\PVD\MY MOVIES.PVD" Error while trying to open file
The process cannot access the file because it is being used by another process.
Unsuccessful execution caused by a system error that precludes successful execution of subsequent statements
Error Code: 24

Trying to run MC/PvdImport while PVD is connected to the database causes what appears to be a similar error...

Failed to open database! Exception: I/O error for file CreateFile (open) "C:\Data\PVD\My Movies.pvd" Error while trying to open file.

Didn't raldo have a problem similar to this a while back? I thought it might have something to do with me using the newer x64 version of Firebird, but I get the same results with the older x32 version.

I suspect PVD is actually connecting via Firebird Embedded, and thereby locking the database. Firebird Server Properties (the Control Panel applet) indicates no database/attachment when PVD is supposedly connected. When MC is running, it indicates one.

Nostra, I'll email a few exception reports, in case they include any useful information.

raldo:

--- Quote from: rick.ca on November 21, 2009, 06:05:18 am ---
Didn't raldo have a problem similar to this a while back? I thought it might have something to do with me using the newer x64 version of Firebird, but I get the same results with the older x32 version.


--- End quote ---

Quite a few users have had this problem when using PVD and PvdImport simultaneously.

The last item in the newest PvdImport release thread FAQ shows how the .ini file should look. However, I'm not sure if the Network key in this file *really* tells the whole truth!

It's definitely related to how PVD connects to the database. If it's via embedded while your server (and PvdImport) is running, there will be this kind of exception.

nostra:
Which path are you entering when connecting to server?

rick.ca:

--- Quote from: raldo on November 21, 2009, 02:51:57 pm ---The last item in the newest PvdImport release thread FAQ shows how the .ini file should look. However, I'm not sure if the Network key in this file *really* tells the whole truth!
--- End quote ---

My configuration...


--- Code: ---[DataBase]
Network=1
FileName=C:\Data\PVD\MY MOVIES.PVD
RecentFiles=..\..\Data\PVD\TEST.PVD|C:\Data\PVD\TEST.PVD
RecentTypes=0;1;
Mode=0
--- End code ---


--- Quote ---It's definitely related to how PVD connects to the database.
--- End quote ---

Yes, it seems so. I realize this is not conclusive, but here's another experiment: I disabled fbembed.dll. Not surprisingly, this caused an exception on starting the program, but it did start—without loading a database. Attempting to connect to server then caused the same exception, suggestion the program is trying to use the DLL instead of the server.


--- Quote from: nostra on November 21, 2009, 04:46:36 pm ---Which path are you entering when connecting to server?
--- End quote ---

As shown in the configuration above... C:\Data\PVD\MY MOVIES.PVD.

I didn't find this before my original post, but this issue seems to be exactly the same as that reported in April (version 0.9.9.5): PVD locks the Firebird database.

It seems I've stumbled onto a workaround. I shut down PVD, MC and Firebird, then restarted Firebird as an application (rather than a service. Then I started PVD and reloaded/connected databases as indicated here...


--- Code: ---[DataBase]
Network=1
FileName=RIX:C:\Data\PVD\My Movies.pvd
RecentFiles=..\..\Data\PVD\TEST.PVD|C:\Data\PVD\MY MOVIES.PVD|C:\Data\PVD\TEST.PVD
RecentTypes=0;1;1;
Mode=0
--- End code ---

...to reconnect using the computer name as well as the database filepath. Unlike previous attempts, the Firebird Server Manager instantly indicated a connection. I've since switched back to running Firebird as a service, and it still works fine.

nostra:
I am pretty sure the only thing you had to do is using path with computer name. It seems like there must be a bug that makes PVD only use local connection when using normal local paths in some circumstances.

Navigation

[0] Message Index

[#] Next page