Shimadzu LCSolution - trouble with data files

[HPLC_Help]

Hi, all -

We're using Shimadzu HPLCs with Shimadzu LCSolution software. We purchased licenses to use for remote access, and to use it we needed to save the data to the network, instead of locally to the computer hard drive.

When we save to the network, we consistently - albeit intermittently - get an error message telling us "file is in use and cannot be accessed." This stops the entire run, without shutting down, leaving solvents pumping away and column ovens baking. There is a database error (I believe its Oracle) # Ox0337 associated with it.

Has anyone experienced this? Any ideas? The Shimadzu rep thinks it's a network problem, and I'm inclined to agree, but I wondered if anyone had seen anything similar.

Thank you!

H_H

[unmgvar]

I have never used LC solution from shimadzu,
still the error is a common one for all softwares

you can replicate it in windows.
open a file with its software
then try to copy paste and delete it while it is opened in the software

this meas the problem is yes related to LC solution.
it means that as you are doing the copy process the file is either opened or my guess actually being created because it is in mid run
check when this happens to you if this is the case you will see the correlation. otherwise the data is still hanging in the software and not being entirely closed from use

Now I am guessing that you have created an automated procedure to bulk copy and dump all your data from the local hard disk to the network.
if it is the case you will need to create a specific command that will only copy files created up to a certain time only and prevent a copy of the files in mid run.
I do not know what is the longest run you have but there are 120 minutes applications, so I advice to transfer files only more then 2 hour old at the start of the transfer procedure.


a copied file can only be deleted after it can actually be safely copied and removed by the CDS, and a smart CDS knows to recognize such a problem of logic and not to perform it.

again if all my assumption are correct, you might have a work around solution.
back up the data only, then delete only old files, for a while you will have a small double set of data, locally and in the network

[HPLC_Help]

unmgvar -

Thank you for the detailed explanation!

In our case, we are writing the file directly to the network - it is not being moved there. However, it does seem to be the case that when the file is created, it is somehow left "open," and so when the software attempts to begin writing data to it, we get the message.

Our time stamps indicate that this happens at the beginning of a run, meaning it is something to do with the file creation or initial running.

It also is an intermittent problem, which makes it more frustrating.

Since it's not (apparently) backup related (unless the network is attempting to back it up immediately after it's written) do you have any other suggestions?

Thanks VERY much! This is VERY helpful!!

H_H

[unmgvar]

there is another possibility maybe,

because it does look like a situation of copy and delete action it could be related to network failure.

in case of communication problem to the DS in a network, the data is stored locally until connection is restored,
after communication restored the software will transfer the data to the DS where it should be from the local temporary storage location.
again a good CDS should have built in logic to deal with this.

[HPLC_Help]

I'll check with my IT guy tomorrow!

Thanks again!

H_H

[Ron]

I believe there is a function under the Tools/Option menu in Real Time Analysis called Autocopy. You can set this to collect the data on the local computer and then automatically copy this to the network drive. This should get around the network issues, the only question would be if your protocols allow the file to exist on two computers at once.

[varossf]

Another thing to look at is the virus scanner. add the file storage to the excluded list of the virus scanner. in some cases the virus scanner grabs the file at opening to check it, this sometimes gives the error as well.