Excel 2003, 2007 data recovery

Hi Friends,
A folder containing lot of excel files (.xls & .xlsx) had been deleted from my drive which I had retrieved back from the hard-disk. But out of these few files had been corrupted.
When I open the file, it displays an error ---
1) "Excel cannot open the file 'FileName.xlsx' because the file format or file extension is not valid. Verify that the file has not been corrupted and that the file extension matched the format of the file".
2) "Excel found unreadable content in 'FileName.xls'. Do you want to recover the contents of this workbook? If you trust the source of this workbook, click yes". When clicked Yes it displays - "Unable to read file". Again when clicked ok - "The workbook
cannot be opened or repaired by Microsoft Excel because it is corrupt"
Please help me on recovering the datas of all the corrupted .xls & .xlsx file, solving these kinds of error.
Best Regards, Raj

The best way is to find another copy: backed up someplace, emailed copy, co-worker/boss, at home.
Alternatively, the OpenOffice/LibreOffice programs can sometimes open corrupted .xls files (some say).
Both programs are free, but are very large downloads. If you try one of them, please post back with your results.
Jim Cone
Portland, Oregon USA
http://www.mediafire.com/PrimitiveSoftware
(Formats & Styles xl add-in: lists/removes unused styles & number formats - in the free folder)

Similar Messages

Report Manager - Template Conversion Problems Excel 2003/2007

Hello,
We are having an issue in which templates created using excel 2003 are showing incorrectly formatted outputs in excel 2007. We have performed testing by creating new templates in Excel 2007 and most formatting is correct as long as we only make minimal changes to the initial template. Once the template is changed to a further extent the formatting is correct but no actual output shows, just the token defaults. Patches have been applied for both the issue of incorrect formatting caused by Excel's smartcutandpaste and also the problem with the token defaults showing instead of actual Oracle data. We would prefer not to have to recreate the templates as this would be a lengthy process. To me it seems as something was modified that affected the existing templates (other than the Generic FSG Template, which works fine), but does not affect newly created templates. Other methods of viewing the data work fine (pdf and html).
Any ideas?
References:
Patches Applied to try and fix problem: 8792030, 9020608, 86607013
Metalink Ref: 960409.1, 1082349.1, 811853.1
Thanks,
-Steve
Edited by: sanstey on Oct 15, 2010 12:08 PM

The BNE.log for the report that would not show the data (due to column deletion):
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
The same error appears on the report that works fine (one without deleting columns):
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
The client is testing now and believes the report output is what she needs and will not need to delete the columns afterall, but for my curiosty, any ideas?
Thanks,
-Steve

BO 6.5 - save as excel 2003 (problem date 31/12/2099)

hi,
i've a query result in BO with a date "31/12/2099". This date come from an oracle db file.
I save it into xls (save as) but the result in xls give me "30/12/1900".
With other date, there is no problem.
an idea to correct this ?
thanks

A workaround for this issue is to select the entire document, go to Edit > Copy All, and then paste it into an Excel spreadsheet. You will get the correct dates and the table will remain in the same format as the original *.rep document. You can then do further calculations in the Excel spreadsheet.
Note: If the *.rep document contains gaps, then they will not be pasted into the Excel spreadsheet unless you use "Paste Special". If you do this, then you will be able to view the data but you will not be able to do further calculations in the Excel spreadsheet.
Regards,
Sarbhjeet Kaur

I can't transfer data properly to Excel 2003 with the report generation toolkit.

I have a table with number to transfer into Excel. I use EasyGraph.vi and it works correctly with Excel 2000. But when I try the same program to transfer my data into Excel 2003, the data are not transfered correctly. When I have for example 0,56, it is read as text in Excel and when I have something like 53,300 Excel 2003 read this 53 300 as if there was no coma.
Do you know what's happening with Excel 2003 ?

Separators have always been a pain in Excel !
A work around is to avoid using any separator at all, and to format numbers as power of 10.
For instance :
0.12345 -> 12345E-5
12.345 -> 12345E-3
The attached vi does the trick.
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
NoSeparatorEnumbers.vi ‏20 KB

Hard-disk Data Recovery

Anybody have any personal experience or recommendation about data recovery specialists for a hard-disk that has hardware failure ?
Would appreciate if you would share your experience or rating for any companies that you may have used for this service, in the past.
I've heard of names "Drive Savers Inc", and "Total Recall".

[DriveSavers|DriveSavers.com], [Ontrack Data Recovery|www.ontrack.com] and [Lazarus|www.lazarus.com] all have excellent reputations for data recovery. They are not cheap, however, but they do not charge if they don't recover anything.
Best of luck.

Problem opening BEx Analyzer Workbook (saved in Excel 2007) in Excel 2003!!

Dear all:
I know there are threads about this issue and numerous support tickets have been provided, but we still can't get any Excel 2007 Query to be opened by Excel 2003.
I have tried to save Excel 2007 BEx Analyzer Query into 97-2003 XLS format. But when we reopened (by both Excel 03 and 07), it prompted the warning messages and broke down the query workbook into several sheets with scrambled data. What am I missing here...? According to the support ticket, it seemed pretty straightforward just by saving the format to 2003 XLS, but in reality it just doesn't work as "advertised"
Thank you...!!!
Brian

I have the solution for this.
It works to my environment.
Follow the steps :
1. you must open the xlsx workbook from Bex Analyzer.
2. Save As workbook locally to your PC for excel 97-2003
(Not "save as" from bex Toolbar but from excel)
3. Now save that workbook with Save As->Workbook from Bex Toolbar into your BI database.
Now go to detail properties of your workbook and there you can see the format xls for your workbook.
Good Luck

BPC 7 : Excel 2003 and Excel 2007 Conflict

Hi Experts,
I have created a template in BPC 7 MS on my computer which has Excel 2003 version.
But when I try that template on another computer which has Excel 2007. The format (in the format Range) did'nt seem to work or it has diff effect on Excel 2007.
Is there really a conflict between them?? and cannot have different Microsoft Office version?? Or is there An Add-on that we have to Install so that Excel 2003 and Excel 2007 can be used at the same Time??
Thanks,
Bennie Jay

Sorin:
Situation
I also have the same issue with Excel formatting in Excel 2007, and I found a work-around specifically to my issue.
At the format section's CRITERIA, I have one entry: HEADING="New Budget" in the Column direction, apply certain color and number format to the cells of that column. However, I used Excel function CONCATENATE("HEADING=",EVDES("FINANCE",CATEGORY)) to come out with HEADING="New Budget", rather than just typing the string value.
With the above exercise, in Excel 2003 the format would apply no problem, but in Excel 2007, the entire formatting went wild and broke. After I dropped CONCATENATE() and just typed in HEADING="New Budget", the formatting applied OK in 2007.
Data
We are currently on BPC 5.1 SP5
The original report was built in Excel 2003
Question
Is there a setting in Excel that would allow me or bypass the restriction to use Excel functions to come out with CRITERIA definition?

Opening an Excel 2003 file in Office 2010 Universal Data Connection error when opening the file from a domain.

Hi.
One of my users are having problem with old accounting files in Excel 2003 when opening Excel 2010.
The user experience that linked information is not being updated properly.
And suspects that it something do with Universal Data Connection .
How can an Excel 2003 spread sheet be converted to Excel 2010 spread sheet and still contain active links?
When the user is opening and converting the file as mention in your suggestion, on the common share on a common domain, the links "breaks".
we are not using SharePoint on our domain.
But when doing it on a local machine, the links does not "breaks".
Looking forward to get solved to this problem.
Thank you in advance.
Rgds

it sounds link, the links changed from relative paths to absolute path. You need to use absolute path in original file.
KR

How to open excel files from email in macro enabled workbooks NOT 2003-2007 worksheets?

I have recently installed Office 365 and it was working great. I needed to open excel documents via email with the macro enabled option. Yesterday it flicked back to only giving me the option to open in 2003-2007 workbook so now I am having issues with the
macros. I am contracting and trying to get work out and this has now caused huge problems.
Am thinking of uninstalling and reinstalling. I did have older versions of ms office so maybe there is some residual content there to remove? I have tried to change the associations and protocols to open in excel macro enabled workbooks but these tick boxes
are greyed out and I do not know how to gain access to these. Have been hunting all through my computer system but do not know how to do this. Am no expert.
If someone could help I would really appreciate it otherwise will need to find some computer shop expert I suppose...urgently ha.
Thanks in advance

it's sound like excel 13 disable the macros, turn on it will fix your issue.
see here:
http://office.microsoft.com/en-us/excel-help/enable-or-disable-macros-in-office-files-HA010354316.aspx
ps: use the local admin to change the setting, the reason why the setting grey out.
KR

Workbooks created in excel office 2007 do not open with excel office 2003

Hi,
We have created workbooks using office 2007 and BEx 7.1 but they do not open with office 2007 (BEx 7.1, patch level 11). The error message is as mentioned ' workbook format .xlsm is supported only from office excel 2007 version'
Plz help.
Regards,
Saurabh Diwakar

Hi,
There is a workaround for this.
Save the workbook locally with ".xls" format in Excel 2007 and try to open with Excel 2003.Now it will open.
(Or)
There is one more option available in the Global Settings dialog where you can mention the "Use XLS File Format" under Default Workbook Tab.This is available from FEP8
Rgds,
Murali
Edited by: MuraliKrishnan E on Apr 28, 2009 1:22 PM

Best practice for Smartview when upgrading from Excel 2003 to Excel 2007?

Does anyone know the best pratice for Smartview when upgrading from Excel 2003 to Excel 2007?
Current users have Microsoft Excel 2003 with Smartview 9.3.1.2.1.003.
Computers are being upgraded to Microsoft Excel 2007.
What is the best pratice for Smartview in this situation?
1. Do nothing with Smartview and just install Excel 2007.
2. Install Excel 2007 and then uninstall and reinstall Smartview
3. Uninstall Smartview, Install Excel 2007, and then install Smartview
4. Somthing else??
Thanks!

We went with option 1 and it worked out fine. Be aware that SV processes noticeably slower in Excel 2007 than 2003. Many users were/are unhappy with the switch. We haven't tested SV v11 yet, so I'm not sure if it has improved performance with Excel 2007 or not (hopefully it does).

OBIEE 11.1.1.7 Exporting to Excel 2003 and 2007 difference

Hi
I have a simple analysis, a couple of measures, some formatted so tat if they are negative show them as Red, minus, 1 decimal and thousand separator. Another measure is not formatted to be Red, just black, minus, 1 decimal and thousand separator.
So ... now to the issue. When I export to Excel 2003 the measures are fine, the numbers are numbers, all fine and dandy.
When I export to Excel 2007+ ... the red minus numbers are now text and impossible to change them all to number. I can only convert to number those that are less than 1000 ... the rest are just impossible.
The other measures, the ones that are black, minus, 1 decimal and thousand separator ... are numbers in Excel 2007+.
Why?
What can I do to solve this?
Kind Regards

Sorry guys ... forgott to say that I'm not the one exporting to Excel ... is my business user and I cannot ask them to save the reports to another format or to cast a column or more?
I will try them both and see what happens ... but this is something that Oracle must fix. It's the year 2013 for godness sake!! This is not a Beta software. In my opinion this is so ridiculous I can hardly find words for it hahahaha
I have tried to cast and convert ... well that doesn't work and I found that some people are using macros to convert text to numbers in Excel ...
Sub txttonum()
For Each tcell In Selection.Cells
If TypeName(tcell.Value) = "String" Then
tcell.Value = Val(tcell.Value)
End If
Next
End Sub
As goes for the CSV option ... I just cannot ask my business user to copy from a CSV file to the Excel file they want to work on, not even if they are advanced Excel users.
Thanks for your suggestions, I really that the cast would work ...
Any other suggestion.

Start OutlookSoft 4.2 with Excel 2003 when Excel 2007 is also installed.

Does anyone know how to get OutlookSoft 4.2 to use Excel 2003 as the default u2013 when both Excel 2003 and 2007 are installed? Iu2019ll take any suggestions. Thanks.

Thanks, Joost and Sorin, for your responses! We will be considering both of them.
My name is Christine, and I work with Ellie (who originated the question).
Sorin, where do you insert the launch command described in your response?
Neither Ellie nor I are computer programmers. We have learned on the job as we go. So it's not obvious to us what to do with your command/path. I have changed the "Open With" property for Web Excel to use the exe file for Excel 2003, but the result is that Excel 2007 opens in compatibility mode, and not as Excel 2003.

Upgarde Excel 2003 to 2007

Hi ,
We are dev stage and we are using MS 7.0 version with excel 2003 .
we are planning to move excel 2003 to 2007 in comming days .
Pls let me know what are impacts , if we upgared excel 2003 to 2007 for BPC developument .
Regards,
PSR

Hi,
Migrating from Excel 2003 and Excel 2007 should be smooth if you take care of the reports, Input Schedules and Dimension Membersheets. Please make sure that all the reports and Input Schedules are properly resaved with correct extension like "xslx" for 2007. Also make sure you have compatibility pack installed on the users machines.
If all of your users are being migrated at once , this would be good, in this way you can avoid the few users opening in Excel 2003 and few opening and saving in Excel 2007. Also if you are migrating in phases, then make sure that BPC Admin users who access the dimension membersheets use one version at once. Because if one Admin User makes changes to dimension sheet in 2003 and the other Admin user open the same membersheet in 2007 then you might get issues like "invalid index format" error and your dimensionsheets might get corrupted. So make sure that all Admin users use same Excel Version. If these things are taken care then migration should go smooth.
Thanks.

Slow query performance in excel 2007 vs excel 2003

Hi,
Some of our clients recently did an upgrade towards BI 7.0 and also upgraded towards excel 2007.
They experience lots of performance problems when using the Bex analyser in excel 2007.
Refreshing queries, using 'simple' workbooks works till 10 times slower than before using excel 2003.
Has anyons experienced the same?
Any tips/tricks to solve that problem?
With regards,
Tom.

Hello all,
1) Please set the following parameters to X in transaction
    RS_FRONTEND_INIT and check the issue.
Parameters to be set are
ANA_USE_SIDGRIDDELTA
ANA_USE_SIDGRIDMASS
ANA_SINGLEDPREFRESH
ANA_CACHE_WORKBOOK
ANA_USE_OPTIMIZE_STG
ANA_USE_TABLE
2) Also refer to below KBA link which would help to resolve the issue.
   1570478 BW Report in Excel 2007 or Excel 2010 takes much more time than
3) In the workbook properties please set the flag
     - Use Compression When Saving Workbook
4) If you are working with big hierarchies please try to improve
performance with following setting directly in AnalysisGrid:
   - Properties of Analysis Grid - Dispay Hierarchy Icons
   - switch to "+/-"
Regards,
Arvind

Excel 2003, 2007 data recovery

Similar Messages

Maybe you are looking for