Note 1050605 - No response for the toolbars in BEx Analyzer

Summary

Symptom

*
After installing the frontend either from the CD or through applying the frontend support package or the patches, the BEx Analyzer toolbars dont respond at all.

Other terms

BEx Analyzer, workbook, BExInstaller, Event Viewer, Toolbar, BEx Analyzer Toolbar, Addin, BEx Addin

Reason and Prerequisites

This problem is caused by a computer settings in the local system..

During the installation of the frontend, the program called "BexInstaller.exe" will get executed. This program put the SAP connector files and the syncfusion controls to the GAC of the client system. If this program fails to get executed , then the Analyzer toolbar wont respond to the Analyzer functionalities at all.

Solution

Before the installation, Please check whether you have met all the pre-requisites for the frontend.

For BI 7.X in GUI 720:
Please check the note 1424366 for general information and
limitations. The hardware and software requirements can be found
in the note 1425805.


Solution-1: Upgrade from SAPGUI710 to SAPGUI720
when a PC with SAPGUI710 patches is upgraded with SAPGUI720 patch the registry key HKEY_CLASSES_ROOT\CLSID\{7B262C9C-1B8C-4BC6-82A8-8AFAED94DDDC}\InprocServer32\7100.0.0.0 is not deleted.
1. GoTo run and type regedit.
2. Search for the above key.
3. Delete the 7100.0.0.0 key

Only 7200.0.0.0 key should exist in the registry under InprocServer32.


Solution-2: Manual execution of BexInstaller.exe
The Bexinstaller.exe is a self executable file. This file will be copied to the client system. Normally it will be in the \BW folder. ( By default it is "C:\Program Files\SAP\FrontEnd\Bw" ). Here double click on the file "BExInstaller.exe". Please wait for 1 minute and restart the BExAnalyzer.

Solution-3: Error persists even after triggering BexInstaller.exe

During the installation the BI installer executes the program called BexInstaller. Bexinstaller writes the event logs in the event Viewer of the client system. If the log size is too small, then an overflow occurs in the event viewer and it is no more possible to write the log files in the Event Viewer.
In order to solve this issue please perform the following steps in the client machine.

*) Go to ControlPanel --> Administrative tools --> EventViewer.
*) In the left Panel select the EventViewer "Application". In the context menu, check the log size in the properties.
*) Increase the size ( Normally 1000 KB wont be enough )


Apparently you can save the current event views and clear it before the Installation.
*) In the context menu select " Save log file as "
--> This enables to save the events in the local file system.
*) Then Select "Clear all events" In the context menu.

Please run the "BexInstaller.exe" after executing these steps.

Solution-4: Microsoft Office updates
Please see that you have to run some of the Microsoft updates for the BEx .NET applications
For Excel 2002\XP please refer note 1121263
For Excel 2003 please refer note 1025122

Solution-5: .Config file
There is a configuration file for the office application to denote which version of .NET framework has to be used while starting the program. A config file, which asks the Excel to use the .NET framework 1.1, is attached with this note i.e. excelexe-v1.ZIP.
So if the client PC is running BI 7.X in GUI 7.10 which needs .NET framework 2.0, then need to follow these steps
1. For Office2003
a. Download the zip file "excelexe-v20.zip" attached with this note for .NET 2.0
b. Unzip the file and place the "excel.exe.config" to C:\Program Files\Microsoft Office\OFFICE11 folder.
c. Run BexInstaller.exe.

2. For Office2007
a. Download the zip file "excelexe-v20.zip" attached with this note for .NET 2.0
b. Unzip the file and place the "excel.exe.config" to C:\Program Files\Microsoft Office\OFFICE12 folder.
c. Run BexInstaller.exe.

Solution-6: Check BExConnect entry in Registry
After BI installation, check the entry for BExConnect in Registry. To check that please follow these steps
1. GoTo run and type regedit.
2. This will open the registry entry and then select MyComputer which is header.
3. Find for BExConnect using Ctrl+F
4. You will find the entry for BExConnect in HKEY_CLASSES_ROOT, which will have a key and path for BExAddin.DLL
If you don't find this entry in HKEY_CLASSES_ROOT and then please uninstall the BI, restart the system and then install the latest patch and then restart the system again and after that also check the BExConnect in registry .

Header Data

Release Status:	Released for Customer
Released on:	13.10.2011 08:20:01
Master Language:	English
Priority:	Correction with medium priority
Category:	Installation information
Primary Component:	BW-BEX-ET-WB Queries in Workbooks