Error - using MS Excel 2007

Hi All,
Very recently I have upgraded my system to MS Excel 2007 from MS Excel 2003. Now when I try to refresh a workbook the system throws an error message saying " Run time error '13' - Type mismatch ". And then gets disconnected from the BW system.
Please help.
Thanks & Regards,
Surjit P

Hi Surjit,
Hi,
See SAP Note 1040856 - Business Explorer 3.X on Windows Vista / Excel
2007 below:
The *Business Explorer (SAP BW 3.x)3 programs are not yet released for
Windows Vista, that means, BEx Query Designer (SAP BW 3.x),*BEx Analyzer
(SAP BW 3.x), 3BEx Web Application Designer (SAP BW 3.x), *BEx Download
Scheduler (SAP BW 3.x)* and BEx Browser (SAP BW 3.x) are not released.
*Likewise, the BEx Analyzer (SAP BW 3.x) for Excel 2007 is not released for
other versions of Microsoft Windows.
Other terms
BEx Analyzer, BEx Query Designer, BEx Web Application Designer, WAD,
Microsoft Windows Vista, 3.x Frontend, Excel 2007, Office 2007
Reason and Prerequisites
We are currently evaluating the usage. Tests have shown that the productive
use of Business Explorer cannot be supported fully at the moment.
Due to changes in the Microsoft Windows and Office environment, problems may
occur when displaying Business Explorer programs (SAP BW 3.x).
Solution
Microsoft Vista and Excel 2007 will be supported officially as of the next
BW 3.5 Frontend patch. These patches should be available by the end of
September 2007.
- BW 3.5 for SAP GUI 6.40: Frontend Patch 13 (see Note 1073426)
- BW 3.5 for SAP GUI 7.10: Frontend Patch 2 (see Note 1006943)
Known problems:
- Microsoft Vista and BEx Query Designer: See Notes 1050174, 1039191,
1013139 and 1050174.
- Microsoft Excel 2007, Vista and BEx Analyzer: see Notes 1045244,
1052761 and 1054250.
- Excel 2007 and BW precalculation servers: You cannot use Microsoft
Excel 2007.
Make sure all the criteria given above are accomplished..
assign points if helpful.
Thanks and Best Regards
lasitha

Similar Messages

Error using percentile excel function in Xcelsius 2008 5.3.0

Hi everybody.
I'm doing an Xcelsius Dashboard and I need to show a percentile value in a line graphic component.
Even I've read that "percentile" Excel function is supported by Xcelsius (Xcelsius 2008 SP3 User Guide), I get an error when trying to preview SWF.
This is the error:
"Incompatible Excel Function".
Anybody knows what's happening?
My Xcelsius version is:
Xcelsius Enterprise 5.3.0.0
Compilation 12,3,0,670
(Spanish)
Thanks in advance.

I had a similar experience with formula Weeknum. I had the Dutch Excel version installed and used the Dutch version of the formula, it did not work same message. Then I tried the formula in English, of course Excel could not execute it, BUT Xcelsius did work fine.
So I guess you have the Spanish Excel installed also, try both languages.

TF86001 Error Using TFS Excel Integration

All,
Any help and insight would be appreciated. I have installed the Workgroup edition of TFS 2005 w/SP1 on a Win2003 Server. I am running VS 2005 Team Software w/SP1 on XP SP2, with Team Explorer. I have Office 2003 Pro with all patches.
I continue to get the TF86001 error:
TF86001: Team Foundation was unable to load the Office AddIn.
This ONLY happens with Excel, my Project 2003 integration works fine.
Here's what I've tried:
I've gone into Add/Remove Programs to ensure that I have .NET Programmability Support enabled for Excel under the Office Pro 2003 entry. I've even unchecked it and rechecked it to try to get it to reinstall.
I've repaired the Visual Studio 2005 Office Runtime (multiple times) and then tried repairing the Team Explorer client (multiple times).
I've uninstalled Team Explorer, then Office, then reinstalled Office, ran updates, reinstalled Team Explorer, etc. Same results - Project works, Excel doesn't.
I have reviewed the Team Explorer install logs from my computer and a computer that the Excel support works on, and can only find marginal differences, no errors. Team Explorer install always completes successfully.
By inspecting and traversing the registry, it seems to me that some of this functionality is encapsulated in the file TFSOfficeAdd-inUI.dll, located in my C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\1033 directory. I've re-registered this file using regsvr32.
I've also played around with reregistering DLLs that I can find in: C:\Program Files\Microsoft Visual Studio 8\Visual Studio Tools for Office. No success there either.
I don't know what to do next. I'm considering calling PSS, but have not had much luck the last few times I've called. Can anyone point me in the right direction? Is there a hotfix for this problem? Thanks in advance.
Thanks,
rockman88

Dennis,
The last part of you suggestion, about 'Excel.exe.config', did the trick. In fact I did have that config file in my C:\Program Files\Microsoft Office\OFFICE11 folder.
It's contents are as follows:
Code Snippet<?xml version="1.0"?>
<configuration>
<startup>
  <supportedRuntime version="v1.1.4322"/>
  <supportedRuntime version="v1.0.3705"/>
  <requiredRuntime version="v1.0.3705"/>
</startup>
</configuration>
Obviously, for .NET framework 2.0, that isn't going to work. I removed the file and it works now.
I do have two additional questions:
Would it have worked if I had simply added a new <supportedRuntime /> entry for 2.0 and should I do that?
I have also noticed now that from withing Visual Studio Team 2005, there is a toolbar, the "Work Item Tracking - Results View" toolbar. This has an Excel button on it, to view the current selection in Excel. I notice that, even after I remove the Excel.exe.confg file, when I click this button when viewing a work items query, I get an error MessageBox that states: "Interface not registered (Exception from HRESULT: 0x80040155)" with a critical (red X) icon. Any ideas on how to fix this (can I re-register something)?
Thanks in advance,
Erik (rockman88)

How to keep the column with FIXED? When I use pivot refreshes in Excel 2007, it keep changes

I use MS Excel 2007.
I want to keep the column fixed whenever I refresh data in pivot tables.
I tried even coding it with a macro:
Columns("B:F").Select
Columns("B:F").EntireColumn.AutoFit
And, in another time I tried columnwidth value to a fixed number; both doesnt work.
Please suggest a solution
Thanks in advance
Rafeek KBM

Hi Rafeek,
One solution is to set the column width after manually or programmatically refresh the PivotTable, for example:
Private Sub Worksheet_PivotTableUpdate(ByVal Target As PivotTable)
Dim ws As Worksheet
Set ws = Application.ActiveWorkbook.ActiveSheet
ws.Columns("A").ColumnWidth = 10
End Sub
Another option is to set the column width, then protect the columns from been updated by the user, before refreshing the PivotTable, unprotect the worksheet. For example:
Public Sub LockColumnA()
Dim ws As Worksheet
Set ws = Application.ActiveWorkbook.ActiveSheet
ws.Columns("A").ColumnWidth = 10
ws.Columns("A").Locked = True
ws.Protect "123"
End Sub
Public Sub UnprotectWorksheet()
Dim ws As Worksheet
Set ws = Application.ActiveWorkbook.ActiveSheet
ws.Unprotect ("123")
End Sub
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error while opening Excel file with Add-ins "CtExcelLinksWeb.xll" for BOFC

Hi,
While opening an excel sheet with the Add-ins, "CtExcelLinksWeb.xll", the following error is being displayed,
The file you ar trying to open , "CtExcelLinksWeb.xll", is in different format than specified by the file extension.
Verify that the file is not corrupted and is from a trusted source before opening the file. Do you wnat to open the file now?
If any setting is required for solving the error kindly help me on it.
Thanks
Prity

Hi ,
I think you are using older version,use microsoft excel 2007 version,then it will opens.
Regrads,
SVS
Edited by: svskumar on Aug 19, 2010 12:18 PM

Error while opening excel integration with sap

Hi
While view planning with excel integration in SAP, I am getting error. I am getting this error in CCA and COPA also.
Can anybody help me how to resolve the issue. Please see the meessage
Error while opening document
Message no. SOFFICEINTEGRATION143
Diagnosis
An error occurred in the desktop application while opening a document.
Procedure
Check first whether you can insert a document from this desktop application as an embedded object in another application. The necessary menu item is usually 'Insert --> Object'. The application then lists all of the OLE document types. Choose the type corresponding to the desktop applciation. If the insertion fails, the error is in the desktop application itself.
This error has various causes. Often, it is caused by activating certain add-ins. Sometimes, the desktop application is wrongly installed. The error should not recur once you have disabled any add-ins or reinstalled the desktop application.
Procedure for System Administration
If you cannot solve the problem as described above, enter a problem message. There are notes relating to how to generate the log file using the program SAPROFFICEINTEGRATIONTRACE.
Regards
Sekhar Datta

Hi ,
I think you are using older version,use microsoft excel 2007 version,then it will opens.
Regrads,
SVS
Edited by: svskumar on Aug 19, 2010 12:18 PM

Exporting CRM 2011 SSRS 2008 report to excel uses old Excel 1997-2003 version

The Notes field is appearing cut off on the exported excel spreadsheet. I am wondering if it is related to the version of excel when exporting from CRM report. The only option is MS Excel 1997-2003, when in fact we have MS Office 2010 installed. How can
I get the report export to excel to use the 2010 version? Will this clear up the issue of the excel cell from being too small to dispay the entire field? Any help would be appreciated, Thank you, Mark A M

Hi Mark A M,
In SQL Server 2008 Reporting Services, the Excel rendering extension renders a report that is compatible with Microsoft Excel 1997-2003. This is the unique renderer for Excel renderer in SSRS 2008. Since SSRS 2012, the default Excel renderer is the version
compatible with Microsoft Excel 2007-2010. So we cannot export the report to excel use Microsoft Excel 2007-2010 version in SSRS 2008. This is by design.
As to your issue, please note that the width of the column in Excel which inherit the width in the report. So we need make sure the cell width is sufficient to display the Notes field in report.
Reference:
Exporting to Microsoft Excel (Report Builder 2.0)
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Crystal Reports 2008 - Excel 2007 Data Source

Have been using Crystal reports 10 and have downloaded 2008 but I can't see a way that I can use an Excel 2007 spreadsheet .xlsx as a datasource. The reason I need 2007 is due to the increased number of columns.
Can anyone confirm if it can be done if so how
cheers
Malcolm

Hello,
Sorry its not supported. Next version of CR will support it.
CR 2008 will generate sheets for every 65,000 rows of data.
If you need that many coumns you may want to look at some other export format or refining your data.
Thank you
Don

Bring Excel 2007 to the front when called from LabView v9 in Windows 7

I am building a duplicate system using Windows 7, LabView v9 and Excel v2007. The original system used WinXP, Excel 2007 and LabView v8.6. The issue is that the original system was able to bring Excel to the front when called from Labview using the property node -application-> visible. This new configuration runs Excel, loads the data, runs the macros but does not bring Excel to the front. The icon blinks in the Win7 taskbar and when selected displays over LabView. If I minimize the Labview window, Excel is there. This leads me to conclude that Excel is visible, as requested but will not come to the front until selected from the taskbar. The only differences, besides the versions, is the original system template files used the .xls extension in and was run in Excel in compatible mode. At the customers request, the new system uses the .xlsm extension on the Excel template files. I have tried using application.visible = True in the macro as well. Could be a setting in Labview? Could be a setting in Excel? Could be .xls vs. .xlsm? Or an issue with Windows 7 and the newer version of Labview.
HP workstation - Labview v9 - Windows 7 - Excel 2007 sp2
Thank you in advance
Stephen
Solved!
Go to Solution.

I will try the windowstate change. Were these done in succession? (i.e. property node -> property node -> property node) Or were they done along the way such as call the ActiveX open and a property node then in a worksheet modification area etc. so there was some time between calls?
I am not sure about the API since the discussion there is with regard to DDE. (Taken from the link document: If you want to call a DLL that contains ActiveX
objects, use the Automation
Open VI with the Property
Node and the Invoke
Node.). I am calling Excel as an application not as a library call unless I am mistaken, which I could certainly be. Are you thinking that once Excel is active through the Automation Open VI that a DLL call to set the application visible would work? I may be trying this already but in Excel through the use of the macro I call from LabView. It contains application.visible = True at the beginning before reading files and plotting data.
I may try sprinkling Property node with application->visible in various locations in the LabView diagram as I do update cells after the call to the plot macro. The puzzle for me is the blinking Excel icon in the task bar. This means active and running but not visible or something wrong as well. There are a few #VALUE cells if not all test in the system are run. Again not a problem in Excel 2007-WinXP-LV8.6
Thank you again one and all.

Error when using BeX Analyzer 7.0 with Excel 2007

When i try to execute a query in BeX analyzer 7.0 and my microsoft excel version is 2007, there will always have a fatal error showing. However, when i use the Bex Analyzer 3.5 , i could execute the query.
Anyway to solve this problem?

You need to do the following
Identify the SAP GUI version you're using, 6.40 or 7.10, and the patch level.
Identify the BW or BI Add-on and patch level of it.
From there, check to see if the versions you have actually support BI 7.0 and Excel 2007. Reliable Excel 2007 support requires failry current patch levels of both the SAP GUI and the corresponding BW/BW Add-ons..
Do you have access to a PC that has a more recent version of the SAP GUI and BW/ BI Add-on? If so, try using that PC and see if you still have the problem.

"Out of memory" error using SmartView v11.1.1.3.500, MS Excel 2007 & MS Win7 Prof SP1 (all 32-bit)

Hi All,
A user is regularly experiencing "Out of memory" error messages while retrieving large MS Excel 2007 worksheets (ad-hoc analysis; approx 700 rows by 13 columns) connected to a Planning cube via 32-bit SmartView v11.1.1.3.500 (Build 008) on a 32-bit MS Windows 7 Prof (SP1) computer with 4GB of RAM. The same user is reporting experiencing a number of other issues (eg, TCP-related time-out, unable to connect to the APS, SmartView add-in disappearing, etc) at the same time.
I could not locate any specific KB document from the My Oracle Support website which addressed these specific issues all at once but from various posts out there, the recommendations to address similar issues were as follows:
Tick the Options > Display > Reduce Excel file size option;
Tick the Options > Display > Improve metadata storage option;
Rebuild the MS Excel workbook from scratch;
Delete all temp files located in the C:\Users\USER NAME\AppData\Local\Temp directory;
Disable auto-recovery for MS Excel;
Add misc TCP-related registry entries (eg, TcpTimedWaitDelay, MaxUserPort, MaxFreeTcbs, etc) on both the client PC and server;
Adjust MS Windows for best performance;
Increase the page file by 25%-50% more than the physical amount of RAM installed on the client PC;
Relocate the page file to a different drive as compared to the drive where MS Windows is installed on the client PC;
On top of the above, are there any other recommendations anyone else would like to share to address the "Out of memory" issue?
Many thanks in advance,
JBM

Monitor the Full GC in GC log and see if there is any gradual increase in the free memory retained after every Full GC over a period, if there is a gradual increase and if its reaching maximum specified heap over a period of time, that means there might be some slow leak from application or native libraries.
Also please check if you have any pattern or request which might be triggering OOM all of the sudden.
If its memory leak best way to investigate that is to capture JRA's at regular interval's and monitor top 10 objects and see which one is growing and consuming more % of heap over a period of time.
You can also have this by captured by print_object_summary and print_memusage options in JRCMD command over a period of time.
Hope this helps.
- Tarun

Error in Excel 2007.

We have a user who gets an error when he will start the BPC for Excel in Excel 2007. And he can not open the BPC for Excel. The following error message appears: "In order to open the file Ev4Excel.xla the file had to be repaired or it was forced to remove unredable materials. The workbook has lost its VBA projects, ActiveX controls and all other programming functions." And it can not open the BPC for Excel
The user also has Excel 2003 installed on his computer and if he uses Excel 2003, it works.
Is it possible to have both Excel 2003 and Excel 2007 installed on the same computer and run SAP BPC against both
Are there some Excel add-ins that you have to install when you install the Excel 2007?

Hi,
In SAP BPC installation guide you will find below recommendation
Note: In order for the software to function correctly in Excel 2007, you must
install the Microsoft.ACE.OLEDB.12.0 provider, which you can get from the
Microsoft website. The provider must be installed on the Application server.
This provided in 25mb in size. We installed it on our application server. but still some errors with excel 2007 is not resolved. Finally we tried with office 2003, but still error continued. When we moved back to office 2007, some excel-addins which were available earlier went missing.
regards,
Lokesh Nandula

Error message when opening a shared workbook with Excel 2007

Hello,
We would like to share a workbook outside BW (by saving into a serveur).Since we use Excel 2007, we can't anymore open this workbook.
We have a message error (see bellow).
For your information, it was ok with Excel 2003.
When whe save the workbook in local disk and then copy from local disk
to a serveur, it's ok.
We use SAPGUI 7.10 support package 8, patch 1 Revision 1443 & BI 7.0.
Best regards
Nicolas Triqnuand

hey Nicolas,
first of all, your error message is in French... not too many people out there will be able to understand. Eventhough I do understand French, it doesn't make much sense to me... BUT... in Excel2007 all macro's are by default disabled. When you enable them (you should get a "Security Warning" right under "the Ribbon"), your BI stuff should work again.
Just gave it a try, and it runs smoothly over here.
Cheers,
RafB

Conditional format with large data fails and show error as "Selection is too large" in Excel 2007

I am facing a issue in paste special operation using conditional formats for large data in Excel 2007
I have uploaded a file at below given location.
http://sdrv.ms/1fYC9qE
The file contains two sheets, Sheet "Data" contains the data on which formats are to be applied and sheet "FormatTables" contains the format tables which contains conditional formating.
There are two table in "FormatTables" sheet. Both have some conditional formats applied on it.
Case 1:
1. Select the table range of Table1 i.e $A$2:$AV$2
2. Copy it
3. Goto Sheet "Data"
4. Select data area i.e $A$1:$AV$20664
5. Perform a paste special operation on full range and select "Formats" option while performing paste special.
Result:
It throws error as "Selection is too large"
Case 2:
1. Select the table range of Table2 i.e $A$5:$AV$5
2. Copy it
3. Goto Sheet "Data"
4. Select data area i.e $A$1:$AV$20664
5. Perform a paste special operation on full range and select "Formats" option while performing paste special.
Result:
Formats get applied successfully.
Both are the same format tables with same no of column and applied to same data range($A$1:$AV$20664) where one of the case works and another fails.
The only diffrence is Table1 has appliesTo range($A$2:$T$2) as partial of total table range($A$2:$AV$2) whereas the Table2 has appliesTo range($A$5:$AV$5) same as of its total table range($A$5:$AV$5)
NOTE : This issue is only in Excel 2007

Excel 2007 No Supporting formating to take a formatting form another if source table has more then 16000 rows and if you want to do that in more then it then you have ot inset 1 more row in your format table to have 3 rows
like: A1:AV3
then try to copy that formating and apply
Solution Case 1:
1.Select the table range of Table1 i.e AV21 and drage it down to one row down
2. Select the table range of Table1 i.e $A$2:$AV$3
3. Copy it
4. Goto Sheet "Data"
5. Select data area i.e $A$1:$AV$20664
6. Perform a paste special operation on full range and select "Formats" option while performing paste special

Excel 2007 accessing PivotItem.Visible gives error if the field item value is a DATE

I have VBA code to manipulate the content of a pivot table - essentially it hides all but the first N items in a pivotfield. Under Excel 2003 the code works fine, as expected irrespective of the data content of the pivot field item. Under Excel
2007, if the data content is a date, the VBA code generates one of several error conditions.
pivotItems(i).Visible = True
Generates error 1004 - Unable to set the visible property of the pivot class
If pivotItems(i).Visible = True then...
Trying to test the visibility generates error 13 - type mismatch
?pivotItems(i).Visible
Trying to determine the visibility of the pivot item in the VBA immediate window, this generates error 2042
I have an illustrative spreadsheet which permits the code to process two different pivot tables, one using a field containg dates; the other a field containing text. Under Excel 2003, the code works on both pivot tables. Under Excel 2007 it works
on the text field table, but fails on the date field table.
I have looked for answers on numerous support forums including answers.microsoft but found not found any answers... only the same or similar unanswered question.

Hi Herbert,
Thank you for your continued interest; please find a revised illustration of the problem here -
http://www.mediafire.com/download.php?zc6ty9ctl1n7yd9
I have made the following changes / additions to the problem illustrator:-
Adopted the use of lists for the data source of the pivot table
Removed reference to '(blank)' as a reserved item not hidden by the VBA code to avoid the possibility of hiding all items
In respect of my original code (MK1), utilised a 'real' item name to be the
reserved item
Added a new (MK2) macro to alter the number of visible items which
hides all but one of the VisibleItems collection
makes the first N items in the collection visible
checks that there are only N items visible (the position of the reserved item
might be greater than N)
The code still executes as expected under 2003, but fails (the same as before) under 2007 when the data type of the PivotItem is date.
The MK1 code fails when testing the current visibility of the Item before trying to set the visibility with:- RTE 1004 Unable to
get the PivotItems property of the PivotField Class
The MK2 code fails when trying to set the visibility with:- RTE 1004 Unable to
set the Visible property of the PivotItem Class as reported above. Note - given that MK2 avoids trying hide invisible items or unhide visible items, I no longer believe that this error is due to the attempt
to set visibility to current state as seen under Excel 2003. I am deeply confused by this now!
I observe with care the different CLASSES on which these failures are reported even though in each case the operations are on the PivotItem.Visible property - MK1 queries it / MK2 attempts to alter it.
Just in case you have been wondering where this is going, this spreadsheet has no prupose beyond illustrating the Excel 2003 / 2007 problem being encountered elsewhere when manipulating pivot table items whose value are dates. The requirement
is to provide a simple user interface to a complex managing reporting spreadsheet consisting of a significant number of pivot tables and charts - altering one cell causes the VBA code to modify the collection of pivot tables to deliver a revised view of the
data. All works fine for 2003 users of the model, but not 2007 users. I need one spreadsheet which will work correctly on both 2003 & 2007.
Regards.

Error - using MS Excel 2007

Similar Messages

Maybe you are looking for