Cumulus Support

For the past few days i am getting error 32 and error 103 showing up every day.
I can't copy and paste errors here though?

I am using Cumulus version 1.9.0 build 136

I'm not sure why you can not copy and paste the errors. Can you take a screen shot?
http://wiki.sandaysoft.com/a/Screen_capture

Hello,

I am getting a similar issue though I am using a different build and version of Cumulus.

Screenshot attached.

Error 32: "The process cannot access the file because it is being used by another process."

AV running, files being backed up by another program?

Hint for folks, from a command prompt type...
> net helpmsg 32

I had these a week or so ago - turned out to be the Toolbox backup and a couple of processes I had started to tun to automatically update my SQL databases.

Modified the back and other processes to starft about 5 mins after Cumulus should have finished its daily turnover and also allowed a minute or two between each action.

So far (touch wood) this has cured the problem for me.

Note that once you get this error (or any other error writing to the log files), you will probably continue to get this error until you restart Cumulus. I may have fixed this particular aspect of the problem in the latest builds.

Steve - if it's any help - I didn't have to re-start mine. It only happened on two days and it was about a week before I had even noticed it (suggestion daj - maybe some other type of warning for this type of error rather than just logging it??) and it had straight after 'corrected itself'.

The latest builds of Cumulus do warn rather than just logging (see screenshot above).

What is really needed is some way for Cumulus to find out which process has the file locked. But I have never been able to find a way to do this. If any clever Windows programmer knows, please do let me know.

For now though - couldn't it implement a mail message with the error(s) in it? At least that would give the user a warning that something has happened?

Obviously if Cumulus is being used on a desktop that is being monitored this isn't an issue, but from what I can recall you have said about C2 being able to run as a service, this 'visibility' won;t be there (and this is why I missed the errors in C1 - running on a service on a server which has no screen, KB or mouse - it is only seen when I remotely connect to it).

serowe wrote:For now though - couldn't it implement a mail message with the error(s) in it? At least that would give the user a warning that something has happened?

That would have to be Toolbox doing that, as Cumulus has no email facility and I don't propose to add one at this point, as Toolbox does it so well. But this has reminded me that someone - probably David - asked for the last error to be put into a web tag (I think?), which I guess would allow what you're suggesting.

Probably not - from what I have seen, and the reason for this thread, this error appears to come in three's as two distintly different error and one of them (the 103 I think) doubling up.

steve wrote:.... But this has reminded me that someone - probably David - asked for the last error to be put into a web tag (I think?), which I guess would allow what you're suggesting.

yes, it would be me. was just another idea for the pot

On a side point, when Toolbox takes a backup I try to open the file without locking it to take a copy, just in case Cumulus needs to write to it. The backup only takes a second anyway but I will look to see if there is anything else I can do to help this along. Of course, it could be another process locking the file but who knows

daj wrote:yes, it would be me. was just another idea for the pot

I'll add it to the next build. I can't work out what the 'probably not' above was a reply to, but this seems to me to be a reasonable solution.

Of course, it could be another process locking the file but who knows

It could even be Cumulus itself, but I have searched the code on many occasions and can't find anything which would cause it. And I've never had the problem myself.

David,

I'm not sure about the backup being the culprit because unless you are actually reading the file, the OS will be handling it for you and should take care of any sharing/locking. I could be wrong but I'm not sure how you back the files up.

steve wrote:It could even be Cumulus itself, but I have searched the code on many occasions and can't find anything which would cause it. And I've never had the problem myself.

I've never had it either in just over 2 years.