Edit in Office Read-Only

Karie Kelly
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2014

I have a user that started having the issue where files are being opened in read-only status.

We are using Confluence 5.4.2; the user tried in both FF 27 and IE 9.

Here wiki version, browser version, nor operating system changed over the weekend.

We have shut down, logged out/logged in and tried - no luck.

She has reset her password to confirm it wasn't a credential issue - no luck.

Anyone have any other ideas of what we can do to troubleshoot the issue?

Other users are not experiencing a problem.

3 answers

1 accepted

0 votes
Answer accepted
Xiangfei.Li February 23, 2014

May the information here be helpful for you.

0 votes
Karie Kelly
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2014

We had tried the various items mentioned in the articles without any luck. In a couple of days, it just started working again. Not sure why.

0 votes
Rodrigo Girardi Adami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 17, 2014

Hi Karie,

There are multiple reason for why the edit in office could be read only. We usually troubleshoot and investigate using the steps listed on this page

I hope this helps to investigate the problem. As this is happening to one user only, it may be a configuration from one server only and not a confluence issue. You may want to check that.

Regards,

Rodrigo

Karie Kelly
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 23, 2014

We did look at that page first and were still not successful. However, in this case, after a couple of days, the issue stopped happening, but we didn't do anything. So, that's good for the user, but disconcerting to me as we did nothing to fix it and it makes it higher risk that other users will encounter for 'no reason'.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events