Excel 2007 (.xlsx) Import File on FDM 11.1.2

Hi
I have taken an excel upload file (Office 2003 .xls format) that we have used in the past and loaded succesfully in FDM 9.2 and opened it in Office 2007, re-saved the file in the Office 2007 .xlsx format, attempted to load the file in FDM 11.1.2 and I receive an error. "Error: An error occurred importing the file.
Detail: No [ups] range name found in file!"
Please note the following:
* The 2003 .xls version of this file loads perfectly fine in FDM 9.2 and FDM 11.1.2
* Saving the same file in 2007 .xlsx and trying to load it in 11.1.2 produces the error mentioned above
* I have verfied that the ups named range does indeed exist in the .xlsx file I am trying to load to via FDM 11.1.2. Additionally as stated in bullet one the same file as .xls loads just fine.
Is there anything I am missing? I have looked at the readme of FDM 11.1.2 for any bugs and was not able to see anything that would prevent this load.
Thank you all in advance for your guidance.

Hi Wayne
Thank you for your lightning fast response (as always). My apologies but I am slightly confused...am I reading this wrong but the 11.1.2 FDM Readme file http://download.oracle.com/docs/cd/E17236_01/epm.1112/fdm_1112000_readme.pdf states:
New Features
FDM
Additional 3rd-Party Support
FDM now supports the following 3rd-party applications:
Windows Server 2008
MS SQL Server 2008
IIS 7
Internet Explorer 8
Windows 7 Client
.NET 2.0 Framework SP2
Support for Excel 2007 (including xlsx file compatibility)
The last item there states support for Excel 2007 including xlsx file compatibility?

Similar Messages

Download to Excel 2007 (.xlsx) Help

Hi Everyone, I have an issue with the Download options - Download to Excel.
We have a few on-demand bulk reports that basically allows users to fire a detailed obiee report through GoURL.
Once the report is done, the Download Option - Download to Excel allow them to export data to an Excel Spread-sheet.
The issue is, OBIEE is exporting the data to Excel as Microsoft Office Excel 97-2003 Worksheet, (.xls) format. As we all know this has a max row count limitation (65000) per sheet.
I was wondering if there is any setting in OBIEE side that would force the Download to Microsoft Excel 2007, (.xlsx) format which has a max row count of 1 million.
If anyone can help me finding the configuration file or settings in OBIEE that would do the above requirement, is greately appreciated.
Thanks
Sai

Hi,
Your Problem is related to Excel only, kindly make the Changes in your Excel File,
   1. Select Column or Cell.
   2. Choose Format > Cells from the menu to open the Format Cells dialog box.
With the Format Cells dialog box open:
Note: For help on these steps, refer to the image above.
   1. Click on the Number Tab (circled in red in the image above).
   2. Select General in the Category Window.
When finished, Click OK at the bottom of the Format Cells dialog box.
It will Show you 4 instead of 4:0000

Downloaded file from SAP to excel 2007(*.xlsx, *.xlsm) - unable to open

Hi All,
I am downloading a data from SAP to excel(*.xlsx) format. I am able to conver/download the file in *.xlsx format, but if try to open the downloaded excel file, it gives teh error message '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 matches the format of the file'. with a OK button. When I press the OK button, no data is displayed.
So kindly let me know how to download the file from SAP to *.xlsx format without any errors.
Note: I am able to download the data in *.xls format without any erros.
Thanks in advance,
Regards,
Vijay

Hi,
You are probably not being able to open the file of .XLSX format because you do not have Microsoft Office 2007 installed on your system. You might be having a lower version of Microsoft Office. e.g. 2003.
What you can do is, before opening the .XLSX file directly on a system which does not have Microsoft Office 2007, you can convert it into .XLS format and then open the same.
See the below code.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_COPY
EXPORTING
    SOURCE               = 'C:\Users\Danish\Desktop\test1.xlsx'
    DESTINATION          = 'C:\Users\Danish\Desktop\test2.xls'
EXCEPTIONS
    CNTL_ERROR           = 1
    ERROR_NO_GUI         = 2
    WRONG_PARAMETER      = 3
    DISK_FULL            = 4
    ACCESS_DENIED        = 5
    FILE_NOT_FOUND       = 6
    DESTINATION_EXISTS   = 7
    UNKNOWN_ERROR        = 8
    PATH_NOT_FOUND       = 9
    DISK_WRITE_PROTECT   = 10
    DRIVE_NOT_READY      = 11
    NOT_SUPPORTED_BY_GUI = 12
    OTHERS               = 13.
IF SY-SUBRC NE 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Regards,
Danish

Excel 2007 Slow Opening File

We were looking at migrating to Office 2007. To verify compatibility, several key users have loaded Office 2007 on their machines. There seems to be several problems related to opening files in Excel.
If Excel is open and the user does a File/Open, files will open quickly. However, if the user clicks on a file to open it, it can take up to a minute to open. I found a fix for this on this forum. It is to add "%1" to the end of the Open command line in the defined file types for XLS files. After this worked, I found that also needs it for the New on XLT, Open for XLSX, New on XLTM, and New XLTX files.
After adding in the above fix I wanted to verify that it worked correctly by recreating the problem so I went in and removed the "%1" from all of the commands. When I tried to open a file, I got an error. So I went back into the File Types and checked the command lines. Now all of the command lines had a %1 at the end of them without the quotation marks. When I would try to delet this %1, it would now allow me to. I could remove it but when I reopened the line, it was back again. If I added the "%1" back to the end of the line it would take that and it would fix the problem again but I was still unable to remove the %1 from the other commands such as New, Print, Save As, etc. I had to Restore my system in order to remove them.
Further testing on the fix reveals that when I file is opened, it attempts to open the file twice. The first time it opens very quickly and then a minute later it opens the second time. Notice that this is the same delay that was experienced previously. It you open the file and make a change before the minute has elapsed, then you get a message stating that the file is already open and if you open it again you will lose your changes. This is probably due to the Use DDE being selected. But If I turn off DDE, then when I click on the first file, it opens quickly and when I click on the second file, it also opens quickly but if I look at the Task Manager, their are 2 copies of Excel running. If I go to the View tool bar in either copy of Excel and try to view the other window, I can not. So it appears that there physically 2 copies of Excel running. When I went back into the File Types, the Use DDE that I had unselected before is now checked again but the DDE command line is blank.
Thinking that may this was something that was surely fixed now that it is 2008 and the software is 2007, I looked for updates and found that IT had not run the updates. Loaded the Compatibility Pack and Service Pack 1 and high hopes that this would correct the problems. After loading the updates, I found that the File Types had reverted back to their original form without the "%1". Now I was really excited. Why would they reset user changes unless they fixed something related to them? To my dismay, the slow startup was back. I had to go back and set the "%1" back into all of the proper command lines.
As of now, my recomendation to IT is to stay as far away from Office 2007 as possible until Microsoft gets their act together.
By the way...I have tried all of the other recomendations from Microsoft about Excel being slow to start. They make a difference of less than 1 second. They also only make the App start quicker. They are not related to clicking on a file to open it.

I didn't seem to get much help from this forum but I will pass on the fix that I have found.
The problem doesn't have anything to do with the %1 fix that everyone is using. All that does is to open the file before Excel is fully started. In particular, before the add-ins are opened.
You can verify this by changing the command line in the File Types to use a /s parameter which will bypass loading the add-ins.
What I found was that even though I had removed the Adobe AcrobatMaker add-in, the file PDFMaker.xla was still in the XLSTART folder and was being loaded.
Since Office now has it's own PDF functionality, this is no longer needed. I did however want to keep Acrobat so that I could print PDFs from other applications and edit PDF files so I wanted to keep it. Just not in Office.
Here are the steps to remove PDFMaker from Excel.
Choose Start > Control Panel > Add/Remove Programs.
Select Acrobat Professional and click Change/Remove.
Click Next.
Select Modify and click Next.
Expand the Create Adobe PDF menu, then select the Acrobat PDF Maker option, and change the status to "This feature will not be available".
Click Next, and then click Finish to complete the process and allow Acrobat to remove the PDFMaker component. Note: You need the installation disk to do this.
After completing this process, it is interesting that it disabled but did not remove the PDFMaker.xla add-in. It is therefore necessary to remove it manually by exploring to C:\Program Files\Microsoft Office\Office12\XLSTART and manually deleting PDFMaker.xla.
Now for those of you who have already tried the "%1" fix and found that it causes new problems and doesn't fix things, you may have already found out that when you try to remove the "%1" from the File Type Open command line, something puts it back in as %1 without the quotation marks. This causes errors when you open a document that has spaces in it's path such as unable to open C:\Documents.xlsx, Unable to open And.xlsx, unable to open Settings.xlsx. No matter how hard you try, you cannot remove the %1.
So here is 2 ways to overcome this.
You can change the parameter from %1 to "%10". This will work as long as you don't try to open 10 files at the same time.
Or you can edit your registry and remove the %1. The easiest way I found was to open the registry editor and search for excel.exe" /e %1. Notice that this is the end of the command line. When I found it, I removed the %1. If you edited more than just the Open command for XLS files, you will need to keep searching until you remove all of the changes. This will get you back to where you were before you tried the "%1" fix.
There may be other add-ins that cause similar problems. Look in the C:\Program Files\Microsoft Office\Office12\XLSTART folder to see what is really getting loaded.

Excel 2007 data file

I am not able to create a new conection with a file saved in excel 2007 (*.xlsx) does anyone know why??

Hi Brian,
I use Crystal XI, what I do to conect to my database is just click on "creat a new conection" and click on "access/excel (DAO)" then browse to pick my file, It has been working with no problems but I just changed my excel version from 2003 to 2007, and It is giving me the following error
LOGON FAILED.
DETAILS : DAO ERROR CODE 0xcca.
SOURCE :DAO Workspace.
DESCRIPTION : EXTERNAL TABLE IS NOT IN THE EXPECTED FORMAT"
Thanks so much for taking the time to try to help me
Nela

OpenXML Excel file, works in Excel 2007, OpenOffice, etc but not in Excel 2010

Hi everyone,
I have a problem. I host a free website, sharing source code and ideas with other developers. One of my projects is a very simple C# class, which generates an Excel 2007 .xlsx file. All source code is provided, along with a demo showing
how to use it, free of charge. No registration required.
http://www.mikesknowledgebase.com/pages/CSharp/ExportToExcel.htm
The .xlsx files that this class generates are fine, they open in Excel 2007 & OpenOffice, I've run the OpenXmlValidator
on the files, and there are no reported problems.
However, If I open the file in Excel 2010 (with SP1), it opens, but if I go to the Print or Print Preview screen, Excel 2010 crashes.
Googling around, I've found that many many users have experienced problems with HP print drivers, I followed some suggestions, such as turning off multi-threading in Excel, but it makes no difference. I tried setting the default printer as
the "Microsoft XPS Document Writer", but it made no difference.
Here is a copy of the Excel file that my demo produces (and which crashes Excel 2010). Can someone tell me why it opens okay, but then crashes Excel 2010 ?
http://www.MikesKnowledgeBase.com/SampleCode/Sample.xlsx
I can get around the problem by loading this file in Excel 2010, saving it as an ".xls" file (!!) and re-loading that... but it kinda defeats the purpose.
And, more generally, why does Excel 2007, OpenOffice and the OpenXmlValidator consider it to be in the correct format, but it crashes Excel 2010 ? I'm surprised that Excel 2010 doesn't at least attempt to report some kind of problem with the Excel
file, rather than bombing out.
Mike

It seems Workbook.XML doesn't have all the information needed by Excel for pagination while prepare for print.
Using your sample code, here is the XML generated for Workbook.XML part within Open XML package :
<?xml version="1.0" encoding="utf-8"?>
<x:workbook xmlns:x="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
<x:sheets>
    <x:sheet name="Drivers" sheetId="1" r:id="rId1" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" />
    <x:sheet name="Vehicles" sheetId="2" r:id="rId2" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" />
    <x:sheet name="Vehicle owners" sheetId="3" r:id="rId3" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" />
</x:sheets>
</x:workbook>
Replace above content with below XML and print should work fine:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<workbook xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships">
<fileVersion appName="xl" lastEdited="5" lowestEdited="5" rupBuild="9303"/>
<workbookPr defaultThemeVersion="124226"/>
<bookViews>
    <workbookView xWindow="510" yWindow="510" windowWidth="4455" windowHeight="2520"/>
</bookViews>
<sheets>
    <sheet name="Drivers" sheetId="1" r:id="rId1"/>
    <sheet name="Vehicles" sheetId="2" r:id="rId2"/>
    <sheet name="Vehicle owners" sheetId="3" r:id="rId3"/>
</sheets>
<calcPr calcId="0"/>
</workbook>
The change is not with data but few elements which define the view for Excel. The required code change can be found using Open XML SDK tool code-reflect.
Shiv Khare

SQL 2008 R2 Export to Excel 2007

I want to export data using the Import and Export Utility to Excel 2007.
I choose a destination of Microsoft Excel and choose an existing (empty) Excel 2007 .xlsx file.
The following errors result. A new worksheet is created in the Excel file with the name of the table and with column headings but no data. If I repeat the export choosing the now existing Excel file it works fine.
How can I make it work the first time?
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21. (SQL Server Import and Export
Wizard)
Error 0xc0202025: Data Flow Task 1: Cannot create an OLE DB accessor. Verify that the column metadata is valid. (SQL Server Import and Export Wizard)
Error 0xc004701a: Data Flow Task 1: component "Destination - RELEASE_LOG" (58) failed the pre-execute phase and returned error code 0xC0202025. (SQL
Server Import and Export Wizard)
- Executing (Warning)
Messages
Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import
and Export Wizard)
Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import
and Export Wizard)

Thanks for your reply.
I think the datatypes are correct.
This is the sql for the SQL 2008 table:
CREATE TABLE [dbo].[q_table](
[Q_No] [nvarchar](40) NOT NULL,
[data1] [nvarchar](255) NULL,
[data2] [nvarchar](255) NULL
) ON [PRIMARY]
This is the sql for the Excel table create.
CREATE TABLE `q_table` (
`Q_No` LongText,
`data1` LongText,
`data2` LongText
There is only one row in the table:
Q_No data1
data2
2 444 aaa
The same export works fine if I select .xls (Excel 1997-2003). This error happens with every table I try to export to .xlsx. I created this table and export to try to debug the issue.
We do this sort of export all the time and I want to use 2007 becuase we often have more than 65K rows to export. Now we export to Access and then export to Excel but it adds time to the job.

AIR and Excel 2007

Hi,
I am trying to find a Flex tool/lib to read/write Excel 2007 files (including XSLX).
Have to do it from AIR app (would be useful with Flex apps too).
Does anybody know whether AS3XLS lib supports XSLX format ?
Please help !
TIA,
Oleg.

I tried to look into details of XLSX, so created a tiny spreadsheet in Excel 2007 (size - 9KB zipped) and opened it in WinZip.
It created a complex file structure with 6 directories and 12 files, mostly XMLs.
I found that it writes data to 2 files: : xl/sharedStrings.xml & xl/worksheets/sheet1.xml
That is a way too complex to figure out & implement without running into a lot of troubles.
So I decided to change approach and switch to using Apache POI framework (XSSF), with Blaze in between.
POI API is not too complex: http://poi.apache.org/spreadsheet/quick-guide.html
Can anybody suggest how to architect/design an AIR app which can read Excel 2007 XLSX file (via POI),
get data into a DataGrid, user updates it and saves into XLSX ?
Do I need a separate Java Servlet ?
Communicate AIR-to-servlet via HTTPService ? FileStream ? XML Object ? sockets ?
How do I read/write a file from AIR app via Java ?
Please help !
TIA,
Oleg.

Excel 2007 Problems while sending E-Mail with Excel Attachment

Hello all,
i wrote a small WD application for uploading a file and sending this file
vie e-mail to some recipients.
I'm using class "cl_document_bcs". No problem with ".doc", ".pdf", also no problem
with ".xls" files generated by old Excel version. But when generating an .xls document with
Excel 2007, the attached file is not readable (just non usable signs).
For attaching the .xls file i use:
TRY.
      lr_attachment = cl_document_bcs=>create_document(
          i_type        = lv_filetype " --> 'XLS'
          i_subject     = 'excel document'
          i_hex         = lt_file_solix
    CATCH cx_document_bcs .
ENDTRY.
Are there any restrictions regarding Excel 2007?
The data element of i_type is just char3, so XLSX
wouldn't be possible.

hello Christopher Linke ,
if you Programatically generation a excel file and you have 2007 version you can use OLE automation to save file as .xls i.e. a 2003 work book ..
if you have a excel file ready and you just want to send it across the you will have to convert the xlsx to xls and then send it you can do this as well using OLE automation
(in 2007 in SAVE AS option you can save it excel 97 2003 workbook)
Edited by: Anup Deshmukh on Mar 3, 2010 3:38 PM

32-bit...64-bit...Excel 2007...Excel 2010...nonetheless a .xlsx File

My head is spinning...soooooo here's the deal...
The client provides us a .xlsx File. Now I have no idea how this is created and saved...via Excel 2007...Excel 2010
When I attempt sourcing the .xlsx File in my SSIS Package I get the error "External Table is not in the expected format"
Sooooo, I figure I'd write a C# Edit Script to read .xlsx File and Save it as a .xls file using the following syntax...
string StrFileName = (Dts.Variables["User::FileName"].Value.ToString());
StrFileName = Path.GetFileNameWithoutExtension(StrFileName);
string StringSourceFile = (Dts.Variables["User::FilePath"].Value.ToString()) + StrFileName + ".xlsx";
string StringDestinationFile = (Dts.Variables["User::FilePath"].Value.ToString()) + StrFileName + ".xls";
// This initiates the Excel Application
Microsoft.Office.Interop.Excel.Application excelApplication = new Microsoft.Office.Interop.Excel.Application();
// This Opens the Source .xlsx File from Emdeon ePaySmart
Workbook workbook = excelApplication.Workbooks.Open(StringSourceFile, XlUpdateLinks.xlUpdateLinksNever, true, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing);
// This will Save the Source .xlsx Emdeon ePaySmart File as a .xls File...note xlFileFormat.xlExcel5
workbook.SaveAs(StringDestinationFile, XlFileFormat.xlExcel8, Type.Missing, Type.Missing, Type.Missing, Type.Missing, XlSaveAsAccessMode.xlExclusive, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing);
// This will Close the Source
workbook.Close(false, Type.Missing, Type.Missing);
// This shuts down the Excel Application
excelApplication.Quit();
Note xlFileFormat.xlExcel8
Now this worked PERFECTLY client side. Then when I created a SQL Server Agent Job it blew up and from what I read the SQL Server Agent Job does not like running dynamic Excel commands.
Soooooooo now I'm back at the drawing board and figured I'd use OLE DB to source the file.
I am using this Connection String for the .xlsx File
string StringConnection = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + sourceFile + ";Extended Properties=\"Excel 8.0;HDR=Yes;IMEX=1\"";
Now I understand that the OLEDB.4.0 Connection string is incorrect for a .xlsx File. (Which is why I probably tried to do this with dynamic Excel commands to begin with)
Now comes the chicken and the egg problem...
If instead I try using the OLEDB.12.0 Connection String it tells me it isn't installed
My network, copied Microsoft Office 2010 installed is 32-bit
So if I try to install the 64-bit Microsoft Access Database Engine 2010 it tells me I have to Uninstall Microsoft Office 2010. Well that is not possible
So my question is this...How in God's name can I try and process this .xlsx File??? I am at a complete loss here.
I did come upon this Posting previously...in italics below but it fell short in terms of providing a solution.
Can anyone please help me out here?
Thanks in advance for your review and am hopeful for a reply.
ITBobbyP85
When I create my connection manager to connect to a .xlsx file, I get the error message that says:
"Test connection failed because of an error in initializing provider. External table is not in the expected format."
The provider selected was the ole db "Microsoft office 12.0 Access Database Engine...", and in the All tab I entered "Excel
12.0" at the top where it says Extended properties.
Here is the stumper:
My import package(s) has (have) been running manually for the last 2-3 weeks, but now i've finished an automated system that downloads
the files from the ftp site, unzips them, validates all the expected files are there, renames and relocates the files to the names/locations expected by my ETL, and then runs the ETL.
I found out today that the people who manually did this process were each time opening the file and then saving it to the correct location
in Excel 2007.
When I try to run my ETL on the files in the automated process, it fails with the above error. If, however, I just open the file and
save it (also in 2007), it runs fine. I have been trying to figure out what saving the file is doing to change it to be in the expected format.
I have tried to use an excel 2003 connection to connect to a copy of the file with a modified extension of .xls and that didn't work.
(in case it was in another version of excel and someone just changed the ext)
I then tried to access the file with the OLE DB provider, as above, but instead of entering 12.0 on the Extended properties line, entering
9.0 or 14.0 in turn (creating new sources/connections each time), and when I do that, both times I get an error that says:
“Test connection failed because of an error in initializing provider. Could not find installable ISAM.”
Am I missing something? Is there something else that simply opening and saving the file might be doing to make it paletable to ssis?
If we install excel on the db server I realize i could probably open it up and save it as excel 2007 and that would do the trick, but
the dba is resistant to this idea, so I thought I'd see if anyone has any other ideas?
If we do have to install excel on that server, does the version have to be excel 2007 in order to programmatically save it as type 2007?
thanks in advance for your thoughts on the issue...

You just need to install the latest ACE OLEDB (JET) provider, then when you set the package to run use a proxy with proper rights to access the Excel file on the file system.
http://www.microsoft.com/en-ca/download/details.aspx?id=13255
Arthur
MyBlog
Twitter

Excel 2007 file *.xlsx

I use Crystal XI, what I do to conect to my database is just click on "creat a new conection" and click on "access/excel (DAO)" then browse to pick my file, It has been working with no problems but I just changed my excel version from 2003 to 2007, and It is giving me the following error
LOGON FAILED.
DETAILS : DAO ERROR CODE 0xcca.
SOURCE :DAO Workspace.
DESCRIPTION : EXTERNAL TABLE IS NOT IN THE EXPECTED FORMAT"
This is happenning when I try to create a new report.
I have also tried with "ODBC(RDO)" I select the data as "Excel files" click on finish, select the file, click "OK", but it shows in the tree below "ODBC(RDO)" an "Excel Files" directory and "Add command" ..... I can't connect to my data table
Can anyone please help me??

Can you check Note 1010935 - Can you increase the number of rows for an export file?
Symptom
Is it possible to increase the maximum number of rows used in an export?
Solution
Yes, it is possible to increase the maximum row limit used in an export.
For hosted customers, please contact Support who will be able to change this on your behalf.
For On Premise customers, you need to log into the application using the "system" login. The property can be found by going to the following:
Setup / System Setup / Configuration / select System Properties from the drop down list and find the property system.ResultSet.maxNumberRowsExported
The description on this property is as follows:
Maximum number of rows in a query result set which may be exported to PDF, Excel, or CSV before the operation is prohibited. This is also used to limit the size of a result set being produced by a scheduled report task.
Please note that Excel also has some limitations on the maximum number of rows, therefore you may still experience a limit to 65K (which was the Excel Limit in Excel97 - Excel 2003). Therefore if you export to excel and your limit is higher than 65K, you will still only see 65K of records. The reason for this is that the open source Apache POI that is used to do the export has not been updated to support Excel 2007 which has a higher limit
Thanks

How can I get Firefox to recognize Excel 2007-2010 XLSX file extension?

There is an Applications setting (under Tools/Options) for Excel 97-2003 Worksheet file extension. How can I add another setting for newer Excel file extension XLSX?

Check the URL that doesn't work.
''If it is an http:// URL:''
When a web server sends Firefox a file, it includes a content-type header. This is what Firefox uses to determine how to handle the file, not the file extension. The server might be sending a generic download type such as "application/octet-stream" which you cannot assign to any one application. That's just a guess because I don't use that software.
''If it is an st:// URL:''
Firefox will check the Windows registry for novel protocols. This article has more information: http://kb.mozillazine.org/Register_protocol

Excel 2007 and Smartview 11.1 file open slow

We are in the process of upgrading to HFM system 11.1 and smartview 11.1.1.3 and as part of this process we are starting to use Excel 2007. I am encountering an interesting problem when opening files in Excel 2007 using smartview 11.1 and I am wondering if any one else has seen this problem and found a solution.
First I converted an excel 2003 file to excel 2007 and saved the file as an xlsx file type. Then I am able to open the file and it would take about 30 seconds to open the file. The file has about 15,000 formulas on for spreadsheets. If I click on each spreadsheet individually and use the "Refersh" button I can save the file in about 10 seconds and then close the file. When I open the file again it will open in 30 seconds. Now using the same file I click "Refresh All" and the file processes fine. I am able to save and close the file in about 10 seconds. However, when I try to open the file again it takes about 20 minutes to open, and then 20 minutes to close.
This only happens with two or three files. I have another file that is 40 spreadsheets and about 3,000 formulas that is not affected when I click Refresh or Refresh All.
Any help would be apperciated.
Rich

Hi
On metalink i found some notes about this issure
"Background
SmartView communicates over HTTP using .NET. This just means that requests and responses are sent in a standard XML format that is tucked in the HTTP headers. The mechanism is the same as when your internet browser requests a file or submits a form (simplification). A standard Microsoft component that is part of Internet Explorer is used for this.
There are three components (four if you include the network) in a SmartView refresh:
-the client
-the web server
-the HFM application server
It is easiest to troubleshoot when they are on separate machines. (Running SmartView on the server to see whether it works better is a useful test to see what effect the network is having, but doesn't show any other bottlenecks.) If you run Task Manager on these 3 machines showing the Performance tab, you will see initial activity on the client as Excel clears the cells and the request is converted into XML. Then you see the web server get busy as it receives and parses the request. Then the application server is busy as it send the data, then the web server is busy as it compiles the results into XML again, and finally the client parses the XML, pushes the data into cells and runs an Excel calculation. This last stage is the longest of all. Overall, it is typical to see the client doing 90-95% of the work, so client performance is a very important factor. Look out for Excel's memory usage increasing and RAM becoming in short supply. Often, user dissatisfaction with refresh times can be alleviated by giving them more RAM or a faster PC.
The situation we are dealing with here, however, is when the chain of events described above is interrupted. In this case, you will see the client or the web server wait in vain for a response from the next machine in the chain. The case of invalid XML is similar, but the response is truncated so that the XML is not well-formed when it arrives. XML consists of matching pairs of tags and is not well-formed when a closing tag is missing. This can be caused by certain network settings such as packet size (see later). The end result in either case is the same: as Excel cleared the cells before sending the request, cells are left blank or with zeroes.
Your job now is to work out why the particular component is failing.
Client
Check the HTTP time out in the registry:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]\
"ReceiveTimeout"=dword:00dbba00
"KeepAliveTimeout"=dword:002BF20
"ServerInfoTimeout"=dword:002BF20
The time-out limit is five minutes for versions 4.0 and 4.01 and is 60 minutes for versions 5.x and 6. Also, the time-out limit is 30 seconds for Windows Internet Explorer 7. To change the settings, add the above keys. The above values are hexadecimal, not decimal and correspond to 18000 milliseconds (3 minutes) and 240 minutes for the receive time-out. See
- http://support.microsoft.com/kb/813827
- http://support.microsoft.com/kb/181050
Once you make those changes, my recommendation is that you reboot the client machine.
Web server
Look for errors in logs showing that the web app didn't respond/disconnected or timed out waiting for another application (i.e. the HFM application server). Eliminate load balancers etc. during testing in order to isolate the problem and to ensure that the user always goes to the same web server otherwise, logs can be hard to interpret. See also the IIS Tuning Guide for IIS settings. We cannot recommend particular settings, as each client must establish the optimal settings for their own environment after performance testing. If necessary, engage the services of a suitably qualified consultant.
Application Server
HFM application server performance is very dependent on whether the data is already in RAM or not. One symptom, where the first refresh fails but the second one succeeds, is probably a sign that the cache needed to be populated and once that had been done (by the first refresh) it went faster. HFM loads whole subcubes (Scenario, Year, Value and Entity) into cache, so asking for lots of accounts in the same subcube is fast, but asking for lots of entities will inevitably slow things down as it runs out of RAM and starts unloading subcubes to make room for more. The HFM event log (HsvEventLog.log) shows this happening, but don't forget that the messages you see are a normal consequence of the way HFM works and are not a problem unless you see a hugely elevated number of them during the period the refresh occurs. Another sign would be page file thrashing.
If there are several servers in a cluster, use sticky sessions in HFM to make sure tests always go the same server, or hit one server directly rather than using the cluster.
Solutions here involve giving more RAM to the server (probably not possible because of the 2 GB limit) and changing the worksheet design to restrict the number of subcubes accessed. A separate consolidation server, so that reads are not competing with intensive consolidations and calculations, would be a good thing.
Network
To find out if packets get fragmented, use
ping -l size -f
to send a big packet with the 'don't fragment' flag. E.g.
Ping -l 1024 -f oracle.com
If you see a reply like Reply from 141.146.8.66: bytes=1024 time=200ms TTL=245 then the size you specified is below the packet limit of the network. But if you use, for example, 2000 in place of 1024, you get Packet needs to be fragmented but DF set, then you know you have exceeded the limit. Combine this investigation with a Fiddler trace (https://www.fiddler2.com/fiddler2/) to see what size data messages are being sent and received.
Troubleshooting Guidance
If you seriously want to go into this in more detail, then it will take a considerable effort on your and your IT Department's part. My general advice would be:
1. During this process, fix your environment so that it is predictable. Register a single HFM application server and connect to that. Use a single web server and don't go through Apache or any other redirector. Make sure we know which machine to go to for logs. This would be a temporary measure and it doesn't stop the other users using the full, load balanced system so long as it doesn't involve your server.
2. As far as possible keep other users from using it during testing, unless you are specifically testing for performance under load. We want to see what activity is due to SmartView and not random other jobs.
3. Use PerfMon on all three machines: client, web server and application server.
4. Clear Logs before testing and note the times of each test so the logs can be correlated.
5. Log CPU activity, memory usage, network throughput, page faults, thread count etc. I'm no expert on this so get advice from someone who is.
6. In addition to the performance logs, from the IIS Server get:
* HTTP.SYS Error Log - %windir%\System32\LogFiles\HTTPERR (Default location; configurable)
* IIS Website Log - %windir%\System32\LogFiles\W3SVC# (Default location; configurable)
* Event Log (both System and Application) in EVT and TXT (tab separated) formats
7. From HFM Application server get:
* HsvEventLog.log (in <HFM install>\Server working Folder)
* Event Log (both System and Application) in EVT and TXT (tab separated) formats
8. Be aware of all timeout settings in your environment (i.e. IIS & the network) and time your tests. This can show whether it is an ASP timeout, script timeout, client side timeout or whatever. Note that the Web Session Timeout setting for SmartView in HFM's Server and Web Configuration is a separate issue from IIS timeouts. Web Session Timeout controls the length of idle time before SmartView makes the user log in again. Default 20 mins.
9. Run Fiddler traces to directly observe the XML and check for HTTP failures.
Further resources
- Tuning IIS 6.0 for HFM
- SmartView Performance FAQ
Both are available from Support.
Author: Andrew Rowland
Version: 11.x (Fri, 30 October 2009)"
regards
Alexander

Ipad Numbers apps unsuccessfully importing Microsoft Excel 2007 spreadsheet

Here are what I did. I first sent a Microsoft Excel 2007 spreadsheet (the format is xlsx) to my email. And then I opened it via Numbers in iPad Mini. The Numbers was importing the Microsoft Excel 2007 spreadsheet. It took about 2-3 minutes importing the file. The importing status bar was indicating the progress. When the importing status bar was about completed and then the Numbers apps closed itself. I first thought it completed importing the file. I opened the Numbers apps, there was nothing. I attempted opening it for several times but it ended up the same. That seemed the Numbers was having a problem importing Microsoft Excel 2007 spreadsheet. By the way, there are several tabs in the Microsoft Excel 2007 spreadsheet. Would that be a reason why Numbers couldn't import the file successfully? Or maybe Numbers only import Microsoft Excel 2007 spreadsheet with single tab in the file? Please help!

gogreen2e wrote:
It's just general worksheet. No pivot table, no VBA logic. But there are several tabs. One of the tabs has formulas linked to other tabs. For example, formula like: '=Sheet2!B2'.
Its possible either of those could be a factor. I'm not sure if there is a top end limit on the number of tabs Numbers will handle (at least haven't run into to it yet). The formula syntax you have does not match what number presents, so that could be the issue, but I seem to recall it has not had an issue converting in the past. Could be wrth a look however.

BSP - download xlsx(excel 2007) document - error

Hi all,
i have a requirement to download different types of documents saved in server. All MS office documents are downloading correctly. it is supporting .xls files but .xlsx files are beiong saved and opened but with empty data, when opened in text document, it shows unrecognized characters(corrupted data)
i am using the below code.
1. FM to get the data in bianry format, file name and mome type.
2. then....
    concatenate 'attachment;filename=' <filename> into lv_content_disposition_value .
    loop at <binary data> into LT_CONTENT_BIN.   " LT_CONTENT_BIN is of RAW(1022) type
      CONCATENATE xstr LT_CONTENT_BIN-line INTO xstr IN BYTE MODE.
    endloop.
    me->response->set_data( data = xstr ).
    me->response->set_header_field( name = 'Content-Type' value = lv_mimetype ).
    me->response->set_header_field(
       NAME = 'content-disposition'
       VALUE = lv_content_disposition_value ).
    navigation->response_complete( ).
the above code is written in Controller - do_request. no view is being called at the end. only the controller is available.
this is of high priority.. so please respond quickly.
thanks in advance.
Ajay.

Hi Guys,
How did you solve the problem, as I am facing
the same issue with 'SCMS_STRING_TO_XSTRING'
in an existing custom BSP application while converting the string to a XLSX file.
FM 'SCMS_STRING_TO_XSTRING'
was working fine with XLS format but for XLSX format(Microsoft excel 2007) I am
not able to open the file.
I have tried with the MIMETYPE “application/vnd.openxmlformats-officedocument.spreadsheetml.sheet”
but was not successful.
Can you guys
toss some light on this please!!!

Excel 2007 (.xlsx) Import File on FDM 11.1.2

Similar Messages

Maybe you are looking for