error other user using file

Josh Sled jsled at asynchronous.org
Mon Jan 28 20:00:19 EST 2008


Forwarding…

(Please remember to CC: the gnucash-user mailing list on all replies, using
your mailer's "Reply To List" or "Reply To All" function.)

"John Cullen" <gishaust at gmail.com> writes:
> Thankyou for the reply.
>
> Yes I did not explain myself  when you open the file it will work for a while and then it would crash. This started before I tried to open it on the xubuntu box. It won't save. It justs wants to
> keep sending errors to microsoft. That is what I mean by buggy. I should have been more descriptive. Sorry.
>
> I have found that when I have tried to open the file it will not show the network share straight away I have to open my computer and click the share even thought I have been using the share not a
> moment before hand. Untill I enter my computer it will not show the network share.
>
> I hope this is useful,
>
> Gishaust
>
> On Jan 29, 2008 1:41 AM, Josh Sled <jsled at asynchronous.org> wrote:
>
>     gishaust <gishaust at gmail.com> writes:
>     > I have three computers one is ubuntu server that holds gnucash accounts that
>     > I have setup with my information. So that it can be backup automatically and
>     > two others that have gnucash installed.
>     >
>     > When I try and open the infomation through the network I get this error
>     > below. There was one only software package, trying to access. So I thought
>     > it might be a windows issue as windows is trying to access. so I put gnucash
>     > on my xubuntu machine and I am still getting the same error.
>     >
>     >
>     > "GnuCash could not obtain the lock for Z:\Business\Gishaust"
>     > "That database may be in use by another user, in which case you should not
>     > open the database. What would you like to do?"
>    
>     This error specifically means that the lockfile is present.  There's
>     generally two scenarios where this is the case:
>    
>     1/ Another instance of gnucash is running, and is (validly) holding the
>     lockfile.  In this case, you should not use the second copy of GnuCash
>     against the same datafile.
>    
>     2/ Another instance of gnucash terminated without removing the lock file,
>     because of crash or a bug in handling the lockfile on a network share.
>
>     > If I try and access the file it will open but it is buggy can someone give
>     > me some direction to why this is happening
>    
>     Yes, you should be able to ignore the lock file, if you're sure there is no
>     other instance of gnucash running at the same time.
>    
>     … But in what way is it then buggy?  After ignoring the lock file, the app
>     should behave just as if there was no lock file in the first place.
>    
>     --
>     ...jsled
>     http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
>
-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://lists.gnucash.org/pipermail/gnucash-user/attachments/20080128/a1761d75/attachment.bin 


More information about the gnucash-user mailing list