Wrong user in “File is locked for editing by another user”
up vote
0
down vote
favorite
We use CIFS shares to store data including Microsoft Office files.
If user tries to open Microsoft Office file which is already opened by another user, there is a message Filename is locked for editing by 'user' but in this message the information about user is not correct.
So the information that file is locked is correct.
But the information about user who locked the file is NOT correct.
What could be the reason for that ?
Where is this information about the user who locked the file coming ?
How to correct this information ?
microsoft-office cifs
asked Nov 21 at 9:09
OrangeSpider
1
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
We use CIFS shares to store data including Microsoft Office files.
If user tries to open Microsoft Office file which is already opened by another user, there is a message Filename is locked for editing by 'user' but in this message the information about user is not correct.
So the information that file is locked is correct.
But the information about user who locked the file is NOT correct.
What could be the reason for that ?
Where is this information about the user who locked the file coming ?
How to correct this information ?
microsoft-office cifs
asked Nov 21 at 9:09
OrangeSpider
1
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We use CIFS shares to store data including Microsoft Office files.
If user tries to open Microsoft Office file which is already opened by another user, there is a message Filename is locked for editing by 'user' but in this message the information about user is not correct.
So the information that file is locked is correct.
But the information about user who locked the file is NOT correct.
What could be the reason for that ?
Where is this information about the user who locked the file coming ?
How to correct this information ?
microsoft-office cifs
asked Nov 21 at 9:09
OrangeSpider
1
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
We use CIFS shares to store data including Microsoft Office files.
If user tries to open Microsoft Office file which is already opened by another user, there is a message Filename is locked for editing by 'user' but in this message the information about user is not correct.
So the information that file is locked is correct.
But the information about user who locked the file is NOT correct.
What could be the reason for that ?
Where is this information about the user who locked the file coming ?
How to correct this information ?
microsoft-office cifs
microsoft-office cifs
asked Nov 21 at 9:09
OrangeSpider
1
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 9:09
OrangeSpider
1
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 9:09
OrangeSpider
1
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 9:09
OrangeSpider
1
asked Nov 21 at 9:09
OrangeSpider
1
1
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
OrangeSpider is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
OrangeSpider is a new contributor. Be nice, and check out our Code of Conduct.
OrangeSpider is a new contributor. Be nice, and check out our Code of Conduct.
OrangeSpider is a new contributor. Be nice, and check out our Code of Conduct.
OrangeSpider is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377218%2fwrong-user-in-file-is-locked-for-editing-by-another-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
