PDA

View Full Version : File Access violation error 4177 ?



DavePorter
11-Feb-2005, 05:57 PM
Hi everyone,

Setup: 2 x Windows XP workstations, simple peer to peer network.
Both machines are fairly new. SP2 and all security updates.

8.2 VDF application.

The one that accesses the data on the other machine comes up with the
following error:
'File access violation error, file may be in use, contacts.dat
error number 4177

This happens if the main computer is running the program or not.

I have replaced contacts.dat.
I have tried a second program that opens contacts.dat with the same error.

The program continues to run, but of course any view that requires
contacts.dat bombs the program.

It works perfectly well on the main computer !

Got me stumped...

TIA - Dave Porter
dj-software

Garret Mott
11-Feb-2005, 06:13 PM
Hi Dave -

Is the data folder by chance under Program Files?

XP SP2 does some weird stuff around sharing anything under Program Files.

If so, try moving it.

HTH

Garret

"Dave Porter" <dave@dj-software.com.au> wrote in message
news:i8QfS0IEFHA.1952@dacmail.dataaccess.com...
>
> Hi everyone,
>
> Setup: 2 x Windows XP workstations, simple peer to peer network.
> Both machines are fairly new. SP2 and all security updates.
>
> 8.2 VDF application.
>
> The one that accesses the data on the other machine comes up with the
> following error:
> 'File access violation error, file may be in use, contacts.dat
> error number 4177
>
> This happens if the main computer is running the program or not.
>
> I have replaced contacts.dat.
> I have tried a second program that opens contacts.dat with the same error.
>
> The program continues to run, but of course any view that requires
> contacts.dat bombs the program.
>
> It works perfectly well on the main computer !
>
> Got me stumped...
>
> TIA - Dave Porter
> dj-software
>
>

DavePorter
11-Feb-2005, 06:20 PM
Hi Garret,

No the data is not under Program Files. But you raise a good point. It
may be worth trying the data in the 'Shared Documents' folder.

cheers, Dave Porter


Garret Mott wrote:
> Hi Dave -
>
> Is the data folder by chance under Program Files?
>
> XP SP2 does some weird stuff around sharing anything under Program Files.
>
> If so, try moving it.
>
> HTH
>
> Garret
>
> "Dave Porter" <dave@dj-software.com.au> wrote in message
> news:i8QfS0IEFHA.1952@dacmail.dataaccess.com...
>
>>Hi everyone,
>>
>>Setup: 2 x Windows XP workstations, simple peer to peer network.
>>Both machines are fairly new. SP2 and all security updates.
>>
>>8.2 VDF application.
>>
>>The one that accesses the data on the other machine comes up with the
>>following error:
>>'File access violation error, file may be in use, contacts.dat
>>error number 4177
>>
>>This happens if the main computer is running the program or not.
>>
>>I have replaced contacts.dat.
>>I have tried a second program that opens contacts.dat with the same error.
>>
>>The program continues to run, but of course any view that requires
>>contacts.dat bombs the program.
>>
>>It works perfectly well on the main computer !
>>
>>Got me stumped...
>>
>>TIA - Dave Porter
>>dj-software
>>
>>
>
>
>

Garret Mott
11-Feb-2005, 06:23 PM
You realize "Shared Documents" is automatically shared with any internet
connection?

Just thought I'd mention it.... Yes, you can (I think) turn that off.

Garret, eternal bearer of glad tidings.

"Dave Porter" <dave@dj-software.com.au> wrote in message
news:UsPqIBJEFHA.1912@dacmail.dataaccess.com...
>
> Hi Garret,
>
> No the data is not under Program Files. But you raise a good point. It
> may be worth trying the data in the 'Shared Documents' folder.
>
> cheers, Dave Porter
>
>
> Garret Mott wrote:
>> Hi Dave -
>>
>> Is the data folder by chance under Program Files?
>>
>> XP SP2 does some weird stuff around sharing anything under Program Files.
>>
>> If so, try moving it.
>>
>> HTH
>>
>> Garret
>>
>> "Dave Porter" <dave@dj-software.com.au> wrote in message
>> news:i8QfS0IEFHA.1952@dacmail.dataaccess.com...
>>
>>>Hi everyone,
>>>
>>>Setup: 2 x Windows XP workstations, simple peer to peer network.
>>>Both machines are fairly new. SP2 and all security updates.
>>>
>>>8.2 VDF application.
>>>
>>>The one that accesses the data on the other machine comes up with the
>>>following error:
>>>'File access violation error, file may be in use, contacts.dat
>>>error number 4177
>>>
>>>This happens if the main computer is running the program or not.
>>>
>>>I have replaced contacts.dat.
>>>I have tried a second program that opens contacts.dat with the same
>>>error.
>>>
>>>The program continues to run, but of course any view that requires
>>>contacts.dat bombs the program.
>>>
>>>It works perfectly well on the main computer !
>>>
>>>Got me stumped...
>>>
>>>TIA - Dave Porter
>>>dj-software
>>>
>>>
>>
>>

Peter Donovan
12-Feb-2005, 06:33 PM
Hi Dave,
The host is a XP Pro, yes?
Peter

Peter Donovan
12-Feb-2005, 06:50 PM
Here's a challenge that would indicate a firewall problem:
Can you simply copy and paste a DAT file from the host computer to the other
computer? You might get an error refusing to do so.
Peter

DavePorter
12-Feb-2005, 07:39 PM
Hi Peter,

Thanks for the feedback...

I don't think it is a firewall problem. Why would just one .dat file
not open. The application opens around 300 dat files and just this one
gives the problem ! I have copied files backwards and forwards on this
network many times without any issues.

cheers, Dave


Peter Donovan wrote:
> Here's a challenge that would indicate a firewall problem:
> Can you simply copy and paste a DAT file from the host computer to the other
> computer? You might get an error refusing to do so.
> Peter
>
>

Phil Kirby
14-Feb-2005, 07:46 PM
We have also seen this problem.
No rhyme nor reason. Random, unexplainable. Reboot, and most time all is
well. Windows is placing crazy attributes on the file.
Phil Kirby


"Dave Porter" <dave@dj-software.com.au> wrote in message
news:i8QfS0IEFHA.1952@dacmail.dataaccess.com...
>
> Hi everyone,
>
> Setup: 2 x Windows XP workstations, simple peer to peer network.
> Both machines are fairly new. SP2 and all security updates.
>
> 8.2 VDF application.
>
> The one that accesses the data on the other machine comes up with the
> following error:
> 'File access violation error, file may be in use, contacts.dat
> error number 4177
>
> This happens if the main computer is running the program or not.
>
> I have replaced contacts.dat.
> I have tried a second program that opens contacts.dat with the same error.
>
> The program continues to run, but of course any view that requires
> contacts.dat bombs the program.
>
> It works perfectly well on the main computer !
>
> Got me stumped...
>
> TIA - Dave Porter
> dj-software
>
>

Garret Mott
22-Feb-2005, 05:01 PM
Hi Again -

Now I've gotten bit by this!

I had the app running fine for weeks from the user's machine. Today I used
DBBldr to add 4 fields to the system file (to match what a new EXE needed).
Now the user machine gets this error 4177 on Sysfile.dat. It comes up about
5 times (every time it's accessed at startup), then a msg saying "File not
open, TableNumber=1" and the startup goes no further (i.e. the app does not
start). The server (which is also a workstation) can use it fine. None of
the files are in Program Files or SharedDocs & sharing on the folder is
unchanged from before the problem occurred.

Both machines are XP Home (don't ask...) - but the only thing I see that has
changed is that before I used DBBldr, the Owner of the file was the same
("Owner") as all other files in the folder. Now it's blank.

I've rebooted both machines twice. Tried changing the file attribute to
read-only & then back. Run XP's "error checking" on the drive (steps 1-3
only).

I can copy files back & forth between the machines & I can open Sysfile.dat
with Notepad from the User's machine.

Any thoughts anyone? Besides switching the app to use Notepad, that
is...<g> This was working great until I made this change & copied in a new
EXE.

Needless to say, the system file is kinda important....

Thanks!

Garret

"Phil Kirby" <phil@ksoft.com.au> wrote in message
news:VRh%235avEFHA.4924@dacmail.dataaccess.com...
> We have also seen this problem.
> No rhyme nor reason. Random, unexplainable. Reboot, and most time all is
> well. Windows is placing crazy attributes on the file.
> Phil Kirby
>
>
> "Dave Porter" <dave@dj-software.com.au> wrote in message
> news:i8QfS0IEFHA.1952@dacmail.dataaccess.com...
>>
>> Hi everyone,
>>
>> Setup: 2 x Windows XP workstations, simple peer to peer network.
>> Both machines are fairly new. SP2 and all security updates.
>>
>> 8.2 VDF application.
>>
>> The one that accesses the data on the other machine comes up with the
>> following error:
>> 'File access violation error, file may be in use, contacts.dat
>> error number 4177
>>
>> This happens if the main computer is running the program or not.
>>
>> I have replaced contacts.dat.
>> I have tried a second program that opens contacts.dat with the same
>> error.
>>
>> The program continues to run, but of course any view that requires
>> contacts.dat bombs the program.
>>
>> It works perfectly well on the main computer !
>>
>> Got me stumped...
>>
>> TIA - Dave Porter
>> dj-software
>>
>>
>
>

Peter Brooks
3-May-2009, 08:24 PM
Garrett what did you eventually do to solve this problem. I have a similar situation. I changed some table structures and only those tables are causing the problem. There are 2 workspaces involved and I made changes to the equivalent tables in both folders. One workspace continues to work and the other does not. I copied the 'faulty' data folder to a temp folder on the server and reset up the workspace from the PC on the network which is the problem and it works. There is also a DOS dataflex app running along side a vdf14 app.
My solution eventually will be to remap the rouge folder for all workstations unless something better comes along? I was leaning towards a firewall permission issue on the 'bad' workstation - the pc's run AVG. I played with some settings swithing stuff off, but maybe not the correct ones. My last piece of the puzzle is they have reported a similar issue in the past and an ex-employee (un-contactable) would make a change on the rouge PC and fix that problem.

Garret Mott
3-May-2009, 08:37 PM
Garrett what did you eventually do to solve this problem. I have a similar situation. I changed some table structures and only those tables are causing the problem. There are 2 workspaces involved and I made changes to the equivalent tables in both folders. One workspace continues to work and the other does not. I copied the 'faulty' data folder to a temp folder on the server and reset up the workspace from the PC on the network which is the problem and it works. There is also a DOS dataflex app running along side a vdf14 app.
My solution eventually will be to remap the rouge folder for all workstations unless something better comes along? I was leaning towards a firewall permission issue on the 'bad' workstation - the pc's run AVG. I played with some settings swithing stuff off, but maybe not the correct ones. My last piece of the puzzle is they have reported a similar issue in the past and an ex-employee (un-contactable) would make a change on the rouge PC and fix that problem.

Hi Peter -

I think you hit on it. I don't remember what I did then (hey - 4 years!), but I have run into something similar recently. In this case I've found that making a copy of the data folder, deleting the original & then renaming the copy back to \Data makes the system happy.

I'll guess that it's a thing where on XP/Server 2000, dbBuilder permissions/file locksdon;t get updated/released. However - that's a total WAG...

Anyway - it works for me & would explain why your temp folder works.

HTH

BTW - Is a "rouge" PC something more than one painted red?

kenjohnson
13-Jul-2009, 01:32 PM
Thanks Garret
that copy back data directory worked!
Ken

Garret Mott
13-Jul-2009, 01:48 PM
Thanks Garret
that copy back data directory worked!
Ken

Glad to hear it!

Peter Crook
9-Sep-2011, 10:33 AM
Hi Peter

Your idea of copying the data folder to a new folder and back again just worked for me - thanks for the suggestion!

The system is deployed under one user account on my W7 pc and development work is done under another. I'd used db Builder while logged on to the development account to alter a file definition in the deployment account and got the error when trying to open the app when logged on to the deployment account. VDF 16.1.