Excel Locking Documents Sporadically -- File Server
-
@Dashrender said:
If I could send a nurse home for the day because she reported something wrong - damn - it wouldn't be long before that would no longer be a problem. Sadly management doesn't see the value in that, which seems ridiculous when you consider one of their primary jobs is accurately recording data into medical charts.
I don't suggest that IT be police any more than any other department. But it is important that we recognize what is happening and report it if there is policy. HR should be handling these things, that's their job. If they decide that these ethics problems are allowed, that's their problem, not IT's.
-
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
-
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
-
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
So killing indexing didn't solve it?
-
@Dashrender said:
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
So killing indexing didn't solve it?
No it didn't. It seemed like it did but she still ran into the same problem. I posted this above:
"Appreciate the effort. For the record she told me it said "read only" but it actually says "open by another user". She was making an assumption which I specifically asked her about and she gave me false information. The thing is there is no other open version of the file from the servers point of view. I think this might be a case of excel being closed improperly so to test this I had her start excel, open the file within excel, close the file in excel (while keeping excel running) and then open a new file. Rinse and repeat. We have not had this issue occur since then. We have probably opened at least 150 documents up until this point. So my question is where do i go from here?"
-
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
OHH!!!
-
@Dashrender said:
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
So killing indexing didn't solve it?
Kill the user instead?
too soon?
-
@scottalanmiller said:
@Dashrender said:
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
So killing indexing didn't solve it?
Kill the user instead?
too soon?
I actually really like this particular user. I just don't know where to go with this
-
@wirestyle22 said:
@Dashrender said:
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
So killing indexing didn't solve it?
No it didn't. It seemed like it did but she still ran into the same problem. I posted this above:
"Appreciate the effort. For the record she told me it said "read only" but it actually says "open by another user". She was making an assumption which I specifically asked her about and she gave me false information. The thing is there is no other open version of the file from the servers point of view. I think this might be a case of excel being closed improperly so to test this I had her start excel, open the file within excel, close the file in excel (while keeping excel running) and then open a new file. Rinse and repeat. We have not had this issue occur since then. We have probably opened at least 150 documents up until this point. So my question is where do i go from here?"
So I'm lost - is the problem solved? You say it hasn't happened since you started having her close using this new method of closing the file, then closing Excel.
I'm sure you agree that this is ridiculous and shouldn't be required, but you did find at least a solution, or so it seams.
-
When I had this problem before, I checked on the server side to see what files where open.
When the user closes the file (and has the locked error) I looked on the server and saw that the server still had a file lock on the file in question - claiming to be form the user in question.
I have no idea why it would not release it.
-
@Dashrender said:
@wirestyle22 said:
@Dashrender said:
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
Apparently this is an ethics thread now
There must be a reason for this. Something tangible that I need to know even if I can't realistically fix it. It's driving me nuts.
For why user's lie? Just because that's how they are.
No for the excel problem
So killing indexing didn't solve it?
No it didn't. It seemed like it did but she still ran into the same problem. I posted this above:
"Appreciate the effort. For the record she told me it said "read only" but it actually says "open by another user". She was making an assumption which I specifically asked her about and she gave me false information. The thing is there is no other open version of the file from the servers point of view. I think this might be a case of excel being closed improperly so to test this I had her start excel, open the file within excel, close the file in excel (while keeping excel running) and then open a new file. Rinse and repeat. We have not had this issue occur since then. We have probably opened at least 150 documents up until this point. So my question is where do i go from here?"
So I'm lost - is the problem solved? You say it hasn't happened since you started having her close using this new method of closing the file, then closing Excel.
I'm sure you agree that this is ridiculous and shouldn't be required, but you did find at least a solution, or so it seams.
I'm scared to say yes because the last time I thought It was fixed it wasn't. I'm monitoring the issue and will report back.
-
@Dashrender said:
When I had this problem before, I checked on the server side to see what files where open.
When the user closes the file (and has the locked error) I looked on the server and saw that the server still had a file lock on the file in question - claiming to be form the user in question.
I have no idea why it would not release it.
I did exactly that and as far as the server knows the file is closed and there should be no issue.
¯_(ツ)_/¯
waiting.
-
hmm.. sounds like our issues were/are different then.
