Business Explorer crashing excel

Question

Hello,
Each time I attempt to start Business Explorer Analyzer it crashes Excel before Excel will fully load.
This morning it worked, but between this morning and now I installed the following files to the Excel startup folder: Personal.xls, book.xlt, sheet.xlt, and toolbar.xlb. 
After I installed these files to the startup folder, BEx analyzer started crashing Excel.
I have since removed all of these four files, but now BEx analyzer still crashes excel on load each time, and I cannot find any way around this.
Please help.  Thanks,
Jon

Answer 1

hi Jon,
what's the 'red' status ? something dll file ? you may try to re-install bw add-on or re-register the files,
check if oss 615800 may help.
oss message is a message we create and send to sap to report error found and through sap propose solution, service.sap.com/message, need id, you can ask basis for one.
please don't forget to reward helpful answers.
ps. Peter is our bw frontend expert (especially excel, vba)
oss note
Symptom
After upgrade of a BW Frontend installation from a 4.6 GUI (BW 2.x)
to a 620 GUI (BW 3.x), the frontend check program sapbexc.xla
causes a memory-Access violation / Dr. Watson on execution
on verification of the wdttree.ocx
The Query-Designer causes a similar memory Access violation.
Other terms
wdttree.ocx, sapfwdraw.dll, sapfewrm.dll,  sapfhook.dll, sapfewut.dll
sapbexc.xla, Bex Analyzer, Bex Query Designer
Reason and Prerequisites
The removal of the 4.6C/D gui was incomplete.
A number of DLL's have remained in system libary path (c:\winnt\system32.exe).
The 620 Frontend attempts to load several dll's formerly shipped with the 46C gui if started from BW-Programs (presumably in non-new visual design mode).
The SAPGUi relies on these DLL's beeing no longer present.
In the specific case, the following DLL's were still present in the c:\winnt\system32 directory in a 46 version (Right mouse-> Properties -> Version 46xx.x.xx.xxx ).
c:\winnt\system32\sapfhook.dll
c:\winnt\system32\sapfewrm.dll
c:\winnt\system32\sapfdraw.dll
c:\winnt\system32\sapfewut.dll
Solution
Case specific solution:
Remove the remainders of the 46C/D gui installation:
Unregister the files by executing the following steps from the
commandline ( or via a script).
regsvr32 /u c:\winnt\system32\sapfhook.dll
regsvr32 /u c:\winnt\system32\sapfewrm.dll
regsvr32 /u c:\winnt\system32\sapfdraw.dll
regsvr32 /u c:\winnt\system32\sapfewut.dll
Subsequentlyremove them from the library directories.
General Solution:
1). Remove all 4.6C DLL's prior to installation of the
620 GUI. Refer to the SAPInstall-Documentation for this process.
2) Verify that all sap components have been removed from the PC.
Check specifically the c:\winnt\system32 directory for components
labelled sap.dll or sap.ocx.
Check via the respective properties whether the components is
a) delivered by SAP ( Manufacturer ).
b) part of the 46 Setup ( Version 46xx.xxx.xxx.xxx ) .
2.1) Manually unregister these components by the script above.
(regsvr32 /u   <yourdll/ocx> ). Note that some DLL's need not/cannot
be unregistered, this is not a cause for alarm.
2.2) Remove them from the pc ( keeping a backup).
2.3)(optional) You may want to run Dlister.exe ( See Note 585643 ) to check for suspicious dll's of potentially SAP origin. Look for dlls with an sap  versioning pattern (SAPGui 46xx.x.x.x, BW 3xxx.x.x.x).
3) Install the 620 SAPGui and the 3.x BW Frontend.
Please refer to the respective documentation. Note that there have been changes to some commandline options for the sapinst setup.
The 620 GUI/3.x BW should bring all SAP components required for a clean installation on a new PC.