5,838
edits
FAQ: Difference between revisions
m
→I am getting I/O error 32 or I/O error 103: mention back-up (forum thread about cloud back up)
m (→I am getting I/O error 32 or I/O error 103: mention back-up (forum thread about cloud back up)) |
|||
| Line 721: | Line 721: | ||
I/O error 32 = ERROR_SHARING_VIOLATION; I/O error 103 = ERROR_TOO_MANY_SEM_REQUESTS mean something on your system has one of the Cumulus files open, preventing Cumulus writing to it (Cumulus needs exclusive access). If you are seeing "file access denied", you may have a permissions problem. | I/O error 32 = ERROR_SHARING_VIOLATION; I/O error 103 = ERROR_TOO_MANY_SEM_REQUESTS mean something on your system has one of the Cumulus files open, preventing Cumulus writing to it (Cumulus needs exclusive access). If you are seeing "file access denied", you may have a permissions problem. | ||
Possible reasons for locked files: | Possible reasons for locked files: | ||
# Anti-virus or | # Anti-virus, or back-up, software scanning/accessing the file (this is the cause in almost all cases that I've seen). | ||
# An edit or file transfer in progress (the Cumulus thread for logging and the Cumulus thread for FTP are independent so can overlap). This is likely to happen if you are getting Cumulus to upload the log file to your web site. | # An edit or file transfer in progress (the Cumulus thread for logging and the Cumulus thread for FTP are independent so can overlap). This is likely to happen if you are getting Cumulus to frequently upload the log file to your web site. | ||
# Some other software that a user is running which is processing the file in some way. | # Some other software that a user is running which is processing the file in some way. | ||
# More than one instance of Cumulus running (see [[#Can_I_run_2_copies_of_Cumulus.3F]]). | # More than one instance of Cumulus running (see [[#Can_I_run_2_copies_of_Cumulus.3F]]). | ||