Bug 76709 - Err:520 when using external link in ods format
Summary: Err:520 when using external link in ods format
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-03-27 21:08 UTC by Mike B
Modified: 2015-05-06 16:46 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

sample monthly file with all irrelevant pages cleared (35.37 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-27 21:08 UTC, Mike B
sample stocks file for linkage testing (26.92 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-27 21:09 UTC, Mike B
sample monthly file reuploaded to correct MIME type (35.37 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-27 21:11 UTC, Mike B

Note You need to log in before you can comment on or make changes to this bug.
Description Mike B 2014-03-27 21:08:56 UTC
Created attachment 96487 [details]
sample monthly file with all irrelevant pages cleared

Multi-page spreadsheets. Reference in one spreadsheet to a page and cell in an external (closed) spreadsheet fails in one cell with "Err:520" shown. Other cells with similar references work. 

If other cells are changed to refer to the target page/cell in the external file they work. 
If the failing cell is COPIED to another cell and adjusted to refer to the correct page there, it will initially work but later fail.
If the cell is changed, file saved, then edited to refer to the correct external page/cell again, the correct value will appear but will again fail after the external links are refreshed either manually (Edit-Links-Update) or by save/close and reopen with external links updated.
If the target spreadsheet is open, all links work. 

** If the name of the source spreadsheet (where the failing cell is located) is changed so that the name includes more than just the month and year (say, MAR2014.ODS change to MAR2014C.ODS) all links work. 

Dependency seems to exist between the name of the open file and behavior of one cell in the file?

File setup is, in an annual directory:
Month files:  JAN2014.ODS, FEB2014.ODS, MAR2014.ODS ...
Stock records file:  STOCKS14.ODS

Failure first noted in release; not tested
Failure also occurs in LO release (currently in use)
Not been tested in 4.0
Worked correctly in release

Attachment is the first of 2 files. Will add the external link file afterward.
The failure is in the monthly file, in the cell referring to the external stocks file for the number of shares for IBM. CVX reference always works correctly.

Note: the sample files don't appear to have the problem. No idea why. But they do contain the linkage examples that have the problem.

Workaround: will be changing filenames and/or directory names, but that's a lot of editing ... or building batch files to always open both the monthly and the stocks file for every editing session.
Comment 1 Mike B 2014-03-27 21:09:43 UTC
Created attachment 96488 [details]
sample stocks file for linkage testing
Comment 2 Mike B 2014-03-27 21:11:20 UTC
Created attachment 96489 [details]
sample monthly file reuploaded to correct MIME type
Comment 3 Mike B 2014-03-27 21:12:17 UTC
Comment on attachment 96487 [details]
sample monthly file with all irrelevant pages cleared

Incorrect MIME type detected. See reupload.
Comment 4 Mike B 2014-04-17 21:30:56 UTC
In one other case, I triggered a 'Err:520' by accidentally entering an invalid character ("!") into a file name in a similar external-reference cell - permanently fixed by fixing the file name. The file name is correct in the one triggering the error described here, however.
Comment 5 raal 2014-08-21 06:36:12 UTC
Hello Mike,
I opened both of your files  and doesn't see any 'Err:520'. Please, where you see 'Err:520' in your files (column H,file "stock")? Thank you
Tested with LO version, Linux; Version:, Windows 7
Comment 6 QA Administrators 2015-04-01 14:47:38 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team
Comment 7 QA Administrators 2015-05-06 14:22:01 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team
Comment 8 Mike B 2015-05-06 16:46:59 UTC
Sorry for letting this one get lost. In fact, since about 4.4, the bug no longer occurs reliably so there is no need to keep this open. Not sure what other fix took care of this, but something did.

Recalculating with external links now usually works.

Workaround for times when it occurs is to open both the primary spreadsheet and the referenced spreadsheet at the same time. Workaround is seldom needed as of