Sapbexc.xla is an Excel file with macros which carries out a version check of all BW frontend files. Incorrect or problematic files are highlighted in color and marked with an Excel comment.
Two types of checks are possible:
- Check of the BW Frontend installation on a PC
- Check of a BW Frontend installation directory on a server
With every patch a new sapbexc.xla file is delivered. You recognize by the header of the 3rd column of page "PC check" or "Server Check" (row 8) whether you opened the current sapbexc.xla for the patch.
Make sure that your installation is correct (green/yellow) before you report a problem to SAP.
Check of an installation directory
Before you start with the installation of the BEx frontend, you should first check in the installation directory on the server whether all current files exist.
The installation directory is the directory, into which you have copied your BW Frontend CD and imported your BW Frontend patches.
1. Start Excel on the server or on any PC.
2. In the Windows Explorer, create a network connection to the installation directory if you want to start sapbexc.xla on any PC.
3. Open the file sapbexc.xla (can normally be found on the CD under .../Win 32/bw)
4. Choose the "Server Check" worksheet.
5. Enter the installation directory (for example "e:") in cell C3 of the Excel worksheet (the installation directory is the directory with the file setup.exe).
6. Choose "Start".
Checking an installation on a PC
After the installation directory on the server was checked, the installation can be carried out on individual PCs. After the installation, you can use sapbexc.xla to check the installation in an easy and fast way.
1. Start Excel.
2. Open the file sapbexc.xla (it is usually on the PC under c:program filessappcbw).
3. Select the worksheet "PC check".
4. Choose "Start".
Result of check
With the check the versions of the files on the PC or in the installation directory are compared to the versions stored in sapbexc.xla and are highlighted in color:
- Green means everything is alright
- Yellow means that the version on the PC or in the installation directory is higher than expected. However, this must not necessarily be a problem.
- Red means that a version is smaller than required. You must solve this problem before you create a problem message or before you carry out the installation (see below).
- Blue means that the version of files is higher than required. The files highlighted blue do not really belong to BW but are used by BW. This may be a problem but is not necessarily one.
As of BW 3.0A Frontend Patch 7 (see Note 496976) and BW 3.0B Frontend Patch 1 (see Note 496984) and higher, the OCX and DLL files are checked more strictly. The program tries to generate an instance of these controls. This action allows to detect incorrect file registrations.
Remarks and troubleshooting
After the installation, in the Windows directory there is a log file sapsetup.log. In this file, all steps of the installation are logged. If a file appears red or yellow, by means of the log file the exact cause of the error can be determined. In the log file, several installations can be logged so that you must pay attention to the date and the time.
Before you copy and maybe register the files as described below in the Windows Explorer you should check the error cause in the log file sapsetup.log.
If the registration of a file should not work, make a screen shot of the error message. This helps SAP to analyze the error later. If you have access to the Microsoft TechNet or Microsoft Developer Network, you can search for the error code of regsvr32 there.
The files under BW Components are the most important parts of the BW Frontend. All files should have a version marked green.
In case of problems in the installation directory check whether the Frontend patch is downloaded from SAPservN correctly and is unpacked and copied correctly into the installation directory (see Note 96885).
If a file is not found on the PC, you can copy the file into directory c:program filessappcqbw with the Windows Explorer. Afterwards DLL's and OCX's have to be registered with regsvr32 .
The message SAP.BusinessExplorer.Analyzer not registered during the PC check means that the BW component of the SAP GUI was not installed or there are serious problems in the installation. The cause could be described in log file sapsetup.log where you should search for the "SAP.BusinessExplorer.Analyzer".
The message Cannot locate SAP GUI patch is displayed, if the SAP GUI path cannot be determined with the Registry and file front.exe. You should repeat the installation with the standard path c:program filesappc.
The message SAPBrowser.SAPBrowserCtrl.1 not registered shows that file wdbbctrl.ocx could not be copied and registered successfully (usually under c:program filessappcbw).
With SAP.TableTreeControl.1 it is reported that the most important SAP GUI file wdttree.ocx could not be copied and registered.
Message Could not create an object of wdbrlog.ocx, wdbcbexc.dll, ... requires a manual registration of the file concerned. Please also register the files specified in Note 417397.
Extension for ArcView
The file sapext.avx is only installed if the complete BW component is installed or is selected under BW component "Extension for ArcView".
The file has no version so that only the size is an indicator. If problems occur, just copy the file with the Windows Explorer into the directory c:program filesappcbwArcView.
The files of the BEx browser 1.2B are installed, to ensure the access to a BW 1.2B System with the newer BW Frontend.
These files are used for BEx Map and are stored under c:program filecommon fileESRI.
The message MapObjects.MemFile.1 not registered means that file memfile.dll (usually under c:program filecommon fileESRI) could not be copied and registered, as a result the system cannot find the directory with the MapObjects files.
OLE DB for OLAP
The files are only installed if the complete BW component is installed or below the BW component "OLE for OLAP" is selected.
BW 1.2B Components
The files were used by the BW 1.2B frontend and are no longer used in higher BW releases. Therefore they should no longer be installed on the PC or be contained in the installation directory.
If the files are still on the PC, this points to an incorrect deinstallation of the old frontend or no deinstallation was carried out at all. Before you can delete the files in the Windows Explorer they must be deregistered with regsvr32 /u .
In the Windows Explorer you can just delete these files from the installation directory.
SAP GUI core components
Under SAP GUI, there is a selection of files which are used especially by the BW Frontend. Since these files are delivered with the SAP GUI they depend on the basis release. The lowest possible versions are specified, therefore some of the files may be highlighted yellow.
If files are highlighted in red, the required SAP GUI patch has not been imported. The required SAP GUI patch is specified in the note for the corresponding BW frontend patch. At least component SAP GUI/SAP GUI 32-bit must be selected for the installation.
If a SAP GUI release higher than required is installed, single SAP GUI files may be marked in red. The BW 2.0B Frontend can run both on SAP GUI 4.6C (4630...) and on 4.6D (4640...). The build number (last number from the right) can be smaller in 4.6D than in 4.6C. If the latest SAP GUI 4.6D patch has been imported, the red mark may be ignored.
In BW 2.0B Frontend Patch 9, file wdtaocx.ocx requests version 46188.8.131.52 by mistake. The correct version is 4640.x.0.100 (where x is the version of the SAP GUI Compilation CD).
As from SAP GUI 6.10, the last number in the version of file wdtaocx.ocx is smaller than with SAP GUI 4.6D. For this reason, the file is displayed in blue, since normally, the last number should be larger. This does not present any problems, however.
As of a certain SAP GUI 6.10 Patch, version 184.108.40.206 of file chart.ocx is delivered. An older version may be version 220.127.116.11 (from the SAP GUI 6.10 Compilation 1 CD). In this case, ...10 is marked red by mistake despite of the version being higher than ...3. Version ...10 is suitable and can be used without any restrictions. This is an error in the version comparison which is corrected with BW 3.0A Frontend Patch 8 (see Note 496977).
A SAP GUI Patch must always be completely imported, that is all files from the SAP GUI Patch must be copied to the installation server.
If individual files are marked red, these files must only be overwritten manually with the required version. An individual file from a newer SAP GUI Patch must not be imported individually, since there may be dependencies between the files.
The file LIBRFC32.DLL is of major importance for the BW Frontend for the communication with the BW Backend. Errors that involve crashes or server messages are particularly likely to be caused by an incorrect LIBRFC32.DLL. There are third-party manufacturers (for example Insight) who also deliver this file and register it in a separate directory - although this is not necessary. For this reason it might be required to scan the entire hard disk for the file LIBRFC32.DLL. You must delete all copies that are not in the Windows system directory (for example c:windowssystem or c:winntsystem32). The file in the Windows system directory must be registered with regsvr32 librfc32.dll.
It is not possible to use a LIBRFC32.DLL from a higher release without a corresponding SAP GUI. Its use can cause errors.
Microsoft core components
The files of Microsoft are only listed for information. On a PC, if a file with a higher version exists it is highlighted blue. A red file with low version should be replaced by the version from the installation directory.
Certain programs store information on OLE components in special files. These files are not updated automatically during a new installation so that for the replacement of the OLE component during the installation outdated information may remain. Therefore, we recommend that you delete all files with extensions "*.EXD" and "*.OCA" before the new installation.
File MSFLXGRD.OCX is displayed in red in BW 3.0A Frontend Patch 5 and the following message is issued "Could not create Object" - this is incorrect. With BW 3.0A Frontend Patch 5, a more thorough test is carried out which can detect registration problems. Apart from BW files, other files are checked as well, such as file MSFLXGRD.OCX. With MSFLXGRD.OCX, there may be situations where a problem is reported despite of everything being in order. If the BW Frontend works properly (i.e. all components can be called), this message may be ignored. With BW 3.0A Frontend Patch 6, this problem is solved.