Subject RE: [firebird-support] Firebird client: Operating system directive create file failed
Author Helen Borrie
At 10:57 AM 13/11/2008, you wrote:
>> At 09:41 AM 13/11/2008, you wrote:
>> >Hi,
>> >
>> >I am currently using Firebird 2.0 client in my application for doing
>> database operations on client side.
>> >
>> >My application is windows application which is using firebird 2.0
>> ADO.NET wrapper to access the firebird native API's. Whenever this
>> application loads it connects with my GDB file and fetch data from GDB
>> file. And also whenever application exists it just closes the
>> connection with my GDB file and then exists. Now when i try loading and
>> existing of my application with normal user speed than connection to
>> GDB file happens but when the interval between application exist and
>> relaunch of application is very less( I just exit the application and
>> the restart the process) then application does not able to make
>> connection to GDB file. But if i add the delay between the application
>> launch and code that connects to GDB file then application is able to
>> make the connection with GDB file.
>> >
>> >The Error that gets logged while connecting to firebird in this case
>> is "Operating system directive create file failed".
>> >
>> >Any help on this will be deeply appreciated. Any specification to
>> open/close the connection with GDB file.
>>
>> It is very simple - rename your database file to have an extension that
>> is not ".gdb". Windows XP and S2003 do horrible things when something
>> opens any file with the .gdb extension, that should not be done to
>> database files. Unfortunately, Microsoft has made it impossible to
>> disable this activity for ".gdb" files.
>>
>> If renaming the file would break too many things then your only other
>> option is to set up the server so that it never performs SystemRestore
>> on the partition where the database file resides. You can reach the
>> applet for configurng SystemRestore by doing a right-click on My
>> Computer, selecting Properties and going to the SystemRestore tab.
>>
>> ./heLen
>
>I think the issue is the "disk shadow copies" feature, not system restore..?

Depends on Windows version - AFAIU, the SystemRestore problem applies to the XP & siblings, which I guessed, absent any info from the OP....Disk Shadowing replaced it on Vista but I've not *heard* of similar problems occurring as a result of Disk Shadowing....

./heLen