Paradox Community

Items in pnews.paradox-development

Subject:Re: not exact read write error
Date:23 Aug 2023 14:11:53 -0400
From:"Kevin Zawicki" <numberjack@wi.rr.com>
Newsgroups:pnews.paradox-development


>
my question, is the read-write error on the lock file itself getting written
to, or is the lock file telling us the problem is locking or 
<

That is tough one. 

It seems like it might be hardware issue, cables, drive, net card, etc.
But I think you would see it more and more frequently.

Corrupt table? Maybe even the that  that repair OK.
Can you manually replace the table from scratch?



>>
copying one of the files? can't manually reproduce this anywhere outside
of those two places in the code.. but those two places in the code get hit
on all day long, in a variety of contexts, including the exact same 
<<

Can you narrow it to a table, a user, a machine?
Can you be there when it occurs and run same right after?

Is that lock fil on a users machine?
Move the PRV folder?

Gremlins?

>proc calling the exact same files, in other processes
Steve Green <steve@oasistradingpost.com> wrote:
>On 08/23/2023 10:48 AM, Mark Bannister wrote:
>> On 8/23/2023 9:27 AM, Steve Green wrote:
>>> haven't deleted the net file, I can try that on Sunday morning when I

>>> have a clean system
>>>
>>> I've seen the error before, and it leans towards "hardware issue", but

>>> the current scenario has the same thing running all day on the same 
>>> hardware and same OS.. we even replaced the drive
>>>
>> 
>> If hardware related maybe some jobs running at night stressing hardware?
>
>same jobs, no matter where they run, and they run way faster on this 
>particular dial-in
>
>my question, is the read-write error on the lock file itself getting 
>written to, or is the lock file telling us the problem is locking or 
>copying one of the files? can't manually reproduce this anywhere outside

>of those two places in the code.. but those two places in the code get 
>hit on all day long, in a variety of contexts, including the exact same

>proc calling the exact same files, in other processes
>
>it's why they call this thing "paradox" :-)
>
>
>-- 
>Steven Green
>Myrtle Beach, South Carolina USA
>
>http://www.OasisTradingPost.com
>
>Collectibles and Memorabilia
>Vintage Lego Sets and Parts
>- and Paradox support, too
>


Copyright © 2004 thedbcommunity.com