Issue 123339 - runtime error soffice.bin Calc to input operations as SUM or +
Summary: runtime error soffice.bin Calc to input operations as SUM or +
Alias: None
Product: Calc
Classification: Application
Component: editing (show other issues)
Version: 4.0.0
Hardware: PC Windows 7
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp
Depends on:
Reported: 2013-09-24 10:46 UTC by decaangeli
Modified: 2017-05-20 11:55 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

error window (37.75 KB, image/pjpeg)
2013-09-24 10:46 UTC, decaangeli
no flags Details
Daily KRA sheet (4.00 KB, application/octet-stream)
2014-08-20 06:06 UTC, Ashok Selvaraj
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description decaangeli 2013-09-24 10:46:27 UTC
Created attachment 81614 [details]
error window

When input any operation between cells, appears the error window bellow
Comment 1 Ashok Selvaraj 2014-08-20 06:06:27 UTC
Created attachment 83857 [details]
Daily KRA sheet
Comment 2 morryporter30 2015-11-13 20:24:59 UTC
Comment on attachment 81614 [details]
error window

how do I resolve the issue of Runtime Errer
Comment 3 orcmid 2015-11-13 21:29:03 UTC
(In reply to Ashok Selvaraj from comment #1)
> Created attachment 83857 [details]
> Daily KRA sheet

If you have a copy of the file that is longer than 4097 bytes, try uploading that.  The attachment 83857 [details] appears to be corrupted. 

 * Excel 2016 also objects to the supplied "Daily KRA.xls" file.  It is not able to recover the file.

 * Apache OpenOffice 4.1.2 reports "Read-Error: Unknown or unsupported Excel file format."

 * LibreOffice 5.0.0 attempts to import the file as text, not as an .xls file.

I examined this 4097 byte file in a Hex Viewer.  It appears that the file has been truncated and also possibly treated as a plain text file by mistake.  The last byte of the file is an ASCII line-feed/newline code.

NOTE: Three different reporters are commenting on this report.  Although all apparently see the same *generic* error message, the causes of the message need not be the same.  We cannot verify the other two reports without being given more information, preferably the file with which the error appears.

PS: I share the disappointment that this issue has been here for over two years without a response of any kind.