Excel Locking Documents Sporadically -- File Server
-
tagging @scottalanmiller as he would probably know
-
LOL, not so likely. Not much of an Excel user.
-
This post is deleted! -
-
@wirestyle22 said:
wat
why
Friends of the internet assemble @Dashrender @dafyre @MattSpeller @coliver @travisdh1
Is that the event you are getting when somebody tries to open the locked file?
-
@dafyre said:
@wirestyle22 said:
wat
why
Friends of the internet assemble @Dashrender @dafyre @MattSpeller @coliver @travisdh1
Is that the event you are getting when somebody tries to open the locked file?
Yeah. The thing is it's not really locked. It opens a bunch of times perfectly fine but sporadically says it's locked. No one else has the file open. Another thing is I'm using two different version of Excel--BOTH VERSIONS have this happen. They can close it afterwards and then open it perfectly fine. It's not just one file either its any excel files. Driving me nuts
-
@wirestyle22 said:
@dafyre said:
@wirestyle22 said:
wat
why
Friends of the internet assemble @Dashrender @dafyre @MattSpeller @coliver @travisdh1
Is that the event you are getting when somebody tries to open the locked file?
Yeah. The thing is it's not really locked. It opens a bunch of times perfectly fine but sporadically says it's locked. No one else has the file open. Another thing is I'm using two different version of Excel--BOTH VERSIONS have this happen. They can close it afterwards and then open it perfectly fine. It's not just one file either its any excel files. Driving me nuts
Is it ONLY Excel files? What about Word files?
-
Just curious, have you tried restoring it from the latest backup (change the filename or directory to restore to), and seeing if the restored file has the same issue? Could be something as simple as a corrupted bit in the wrong place.
-
@travisdh1 said:
Just curious, have you tried restoring it from the latest backup (change the filename or directory to restore to), and seeing if the restored file has the same issue? Could be something as simple as a corrupted bit in the wrong place.
It's not just a single file it's all files and I'm not sure when this started. I think it most likely has been longer than 7 days (backup tapes). I don't think it's the files themselves.
-
@wirestyle22 They have a procedure for this type of thing here, it's called "Throw it in the pond." Good luck, I'll be watching to see the cause/fix.
-
@travisdh1 said:
@wirestyle22 They have a procedure for this type of thing here, it's called "Throw it in the pond." Good luck, I'll be watching to see the cause/fix.
Sad frowny time
-
@dafyre said:
@wirestyle22 said:
@dafyre said:
@wirestyle22 said:
wat
why
Friends of the internet assemble @Dashrender @dafyre @MattSpeller @coliver @travisdh1
Is that the event you are getting when somebody tries to open the locked file?
Yeah. The thing is it's not really locked. It opens a bunch of times perfectly fine but sporadically says it's locked. No one else has the file open. Another thing is I'm using two different version of Excel--BOTH VERSIONS have this happen. They can close it afterwards and then open it perfectly fine. It's not just one file either its any excel files. Driving me nuts
Is it ONLY Excel files? What about Word files?
Word seems fine. I cannot replicate the problem and the user can't either (in word).
Note: This doesn't just happen with one user as well. I am just using one person to test it in addition to my accounts. User has full access permissions to the folder and inherited permissions are on for it. I also removed inherited permissions and applied them manually. Same thing.
-
Argh grief, had this SOOO many times when I was mainly helpdesk based.
Excel files like to be annoying.
What file format are the spread-sheets exactly?
-
If what I think I found is the cause of this I'm going into the woods to punch dance until I can't feel feelings anymore
-
So I noticed indexing was enabled. I disabled it.
I have not been able to reproduce the problem. Might be too early to judge but after opening over 60 documents I have not run into the issue.
-
@wirestyle22 said:
So I noticed indexing was enabled. I disabled it.
I have not been able to reproduce the problem. Might be too early to judge but after opening over 60 documents I have not run into the issue.
I find the indexing system to almost always be bad.
-
@scottalanmiller said:
@wirestyle22 said:
So I noticed indexing was enabled. I disabled it.
I have not been able to reproduce the problem. Might be too early to judge but after opening over 60 documents I have not run into the issue.
I find the indexing system to almost always be bad.
I never enable indexing. I have no idea why it is enabled. I must have not noticed it when I started here. I will keep everyone updated once I test this further.
-
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
So I noticed indexing was enabled. I disabled it.
I have not been able to reproduce the problem. Might be too early to judge but after opening over 60 documents I have not run into the issue.
I find the indexing system to almost always be bad.
I never enable indexing. I have no idea why it is enabled. I must have not noticed it when I started here. I will keep everyone updated once I test this further.
Microsoft has "helpfully" enabled that feature in updates for desktop versions of Windows, I wonder if that's what happened here?
-
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
So I noticed indexing was enabled. I disabled it.
I have not been able to reproduce the problem. Might be too early to judge but after opening over 60 documents I have not run into the issue.
I find the indexing system to almost always be bad.
I never enable indexing. I have no idea why it is enabled. I must have not noticed it when I started here. I will keep everyone updated once I test this further.
On by default.
-
What error message does the user get when they try and open one that has this problem?
Oh, never mind - read only. One minute.
