Skip to Content
Introduction

Within SAP NetWeaver 2004s BI, we can still use the traditional BW 3.x Frontend tools. In addition, we have new frontend tools available within the 2004s version. As there are multiple tools, we need to be cognizant of the supported versions of the client side software. Below, you will see links that show the supported internet browsers, operating systems, and Microsoft Office versions that the SAP BEx tools support.

Supported Browsers

Supported OS and Office Versions:

This BLOG will discuss how to configure your browser parameters as well as discuss how to install the latest SAP NetWeaver 2004s BI Frontend Components. Keep in mind that it is always best to keep your frontend patches up to do date.

This is for SAP NetWeaver 2004s SPS8 or greater.

Setting up Internet Explorer 6.0

One of the first things to do if you have a browser issue is to clear all temporary files, cookies, and offline content from your browser cache.

If you’re using Microsoft Internet Explorer, there are number of issues you may run into with the portal and frontend if you don’t have your browser settings configured appropriately. To use the Web Analyzer or any functionality involving the SAP NetWeaver Portal, make sure you have your browser setup correctly.

I highly recommend updating to the latest support package of Internet Explorer (as of this article being written, that would be SP2). For sake of simplicity, I’m going to focus on Internet Explorer 6.0 SP2 or greater. Previous releases have numerous issues and there are numerous hotfixes that apply. If you’re using previous versions, see Microsoft’s knowledge base article at: http://support.microsoft.com/kb/827667/.

One of the key settings within your Internet Explorer Browser is the “Do not save encrypted pages to disk” seting. It is recommended to unselect this setting in your browser as per OSS Notes 901949 and 855500. This may have slight performance issues, but this has been known to cause many javascript errors (many times these are permission denied errors) due to Internet Explorer bugs. If you have to use this setting, make sure you see Microsoft hotfix, http://support.microsoft.com/?kbid=825057 , although it is recommended not to use this setting.

One of the common things that I would also suggest checking is that your proxy information is setup correctly within your Internet Explorer connection settings. I know this is low hanging fruit, but it is very important.

Within Internet Explorer, you should make sure that you add your SAP NetWeaver Portal and BI systems to the list of trusted sites within Internet Explorer. This is available through the Tools -> Internet Options -> Security -> Trusted Sites -> Sites area.

Within Internet Explorer, you should make sure that you add your SAP NetWeaver Portal and BI systems to the list of sites that can always use cookies. This is available through the Tools -> Internet Options -> Privacy -> Sites

Within Internet Explorer, you should make sure that you add your SAP NetWeaver Portal and BI systems to the list of sites that are NOT blocked by the popup blocker. This is available through the Tools -> Internet Options -> Privacy -> Popup Blocker Settings

Within Internet Explorer, you should check your advanced tab settings.
Also, a requirement is to ensure that javascript is enabled for your internet explorer browser. If you disable javascript, your page and portal won’t load. See this Microsoft guide on how to enable javascript on your client browser.

http://support.microsoft.com/?scid=http%3a%2f%2fwww.support.microsoft.com%2fgp%2fnoscript%2f
If you’re having issues with IE such that it won’t decompress HTTP Content on IE 6 SP2. Ensure that your wininet.dll file is at the following version for IE 6 SP2.

10-Jun-2005 01:38 6.0.2900.2695 658,944 Wininet.dll

If it is not, see this Microsoft hotfix page
http://support.microsoft.com/kb/871205

for a resolution to this issue.

One other thing to ensure that if you have any 3rd party popup blockers within Internet Explorer, such as Google Toolbar, Yahoo Toolbar, etc…, make sure you disable the popup blocking or allow popups from the SAP system’s domain.

Next, add your local domain to your trusted sites in Internet Explorer. If you can’t add the entire domain, add the ABAP and JAVA systems manually.
If you’re still having issues with Internet Explorer 6.0 and you’ve followed all these steps, I suggest using HTTPWatch or another http trace program and check your http return codes when loading pages and also use the javascript debugger to get a better idea of the types of javascript errors you are receiving. Then search Microsoft’s Knowledge Base articles at http://support.microsoft.com. Feel free to post them to this blog, and I’ll update other messages I may find as I work with customers.

In addition, you need the latest version of the mshtml.dll version for Windows XP SP2. This is mentioned and available in this microsoft hotfix: http://support.microsoft.com/kb/917425.

Setting up Internet Explorer 7.0

Internet Explorer 7.0 is supported for NetWeaver as of SPS10.

Setting up Mozilla Firefox

I typically recommend keeping your Mozilla Firefox browser up to date. Currently, Mozilla Firefox 1.5.0.4 has no known issues where hotfixes need to be applied.

Clear Cache if you’re having issues.

Make sure that your proxy is defined for Mozilla Firefox.

Make sure you setup your BI and Portal system as “Allowed” to create cookies.

Make sure you setup your BI and Portal system as not blocked by the popup blocker.

Make sure you enable Java and Javascript.

To date, I have not had any client issues with Mozilla Firefox 1.5.0.4, although the Visual Composer Design Time only works with Internet Explorer.

Installing Latest Version of .NET 1.1 framework

Download and install the latest version of Microsoft .NET Framework 1.1. Currently, there is a version 2.0 available, but 1.1 is required. See OSS note 877774 for details.
Keep in mind this must be installed BEFORE SAPGUI or the BI Addon is installed.
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3

Install Microsoft Visual J# .NET

This is a new Prerequisite (Note 964495): You need have installed “Microsoft Visual J# .NET Version 1.1 Redistributable Package”
http://www.microsoft.com/downloads/details.aspx?FamilyId=E3CF70A9-84CA-4FEA-9E7D-7D674D2C7CA1&displaylang=en

Installing SAPGUI Client

To use the BEx Toolset, you will need to install the SAPGUI Client software. In general, you will need to download the following files. Keep in mind that as newer versions of the SAPGUI files become available, it is recommended to keep these up to date.

The first step is to download files. For sake of simplicity, I’m going to talk about a completely new install. I do recommend that to ensure you have a clean install and all your SAPGUI files up to date, a clean install is the best option.

1. Go to Control Panel and remove SAPGUI. Uninstall all your SAP Frontend Components (Control Panel -> Add or Remove Programs -> SAP Front End)

2. The first step is to download the SAP Frontend Installer. Available at:
http://service.sap.com/swdc/
-> Download
-> Installations and Upgrades
-> Entry by Application Group
-> SAP Frontend Components
-> SAP GUI FOR WINDOWS
-> SAP GUI FOR WINDOWS 6.40
-> Installation
-> NW 2004s SR1 Presentation – 6.40 Compilation 5 Present. 1/3
You only need this one file for SAPGUI BI components As of today (6/26/06), this is the latest file:
https://smpdl.sap-ag.de/~swdc/012002523100000185562006E/50078731_4.ZIP?_ACTION=DL_DIRECT

3. Extract the downloaded file to C:\SAPGUI_INSTALL\

4. Run Sapsweep to delete any frontend dlls or other components that are on this frontend machine.

5. Launch Microsoft Excel and run Help -> Detect and Repair to remove any references to SAP Addins.

6. Run Setup from C:\SAPGUI_INSTALL\DVD_NW_2004s_SR1_Presentation\PRES1\GUI\WINDOWS\WIN32\setup.exe Make sure you choose ALL components to install (including all addons). If you don’t want to install all components, make sure you choose BI Addon, BW Addon, and SAPGUI as a minimum.

Update SAPGUI Client to latest patches

1. Download these files: Make sure you save the patch files as “.exe” files.
http://service.sap.com/swdc
-> Download
-> Support Packages and Patches
-> Entry by Application Group
-> SAP Frontend Components
-> SAP GUI for Windows 6.40
-> SAP GUI for Windows 6.40
-> Win32

Latest Patches for:

SAPsetup for SAP GUI 6.40

Currently, this is setup23 located at:
https://smpdl.sap-ag.de/~swdc/012002523100000136352006D/setup640_23-10001615.exe?_ACTION=DL_DIRECT

SAP GUI for Windows 6.40 Patch

Currently, this is patch21 located at:
https://smpdl.sap-ag.de/~swdc/012002523100005644132006D/gui640_21-10001615.exe?_ACTION=DL_DIRECT

SAP BW 3.5 AddOn Patch

Currently, this is BW 3.5 Patch 11 located at:
https://smpdl.sap-ag.de/~swdc/012002523100007596782006D/bw350_11-10001615.exe?_ACTION=DL_DIRECT

SAP Netweaver 2004s BI AddOn Patch

Currently this is SAP NetWeaver 2004s BI FEP 904 located at:
https://smpdl.sap-ag.de/~swdc/012002523100007950122006D/Bw700SP09P_904-10001615.exe?_ACTION=DL_DIRECT

5. Run SAPsetup for SAP GUI 6.40

6. Run SAP GUI for Windows 6.40 Patch

7. Run SAP BW 3.5 AddOn Patch

8. Run SAP Netweaver 2004s BI AddOn Patch

Installing MSXML Parser

The latest version of Microsoft XML Parser should be installed. MSXML parser comes installed on Windows XP machines, but if you’re using a prior operating system, you may need to install it. Also, you should make sure the version you are using is up to date. MSXML Parser is required for Visual Composer designtime.

Currently, the latest version is MSXML Parser 6.0 which is located at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be21-27e85e1857b1&DisplayLang=en

Installing Adobe SVG Viewer

Download and run Adobe SVG Viewer 3.0 http://www.adobe.com/support/downloads/product.jsp?product=46&platform=Windows Adobe SVG Viewer is required for all users that will use the Visual Composer Designtime. It is not required for any runtime users or for any other BEx tools (at least it isn’t required yet …)

Installing Adobe Flash Player

Download and Install Adobe Flash Player (v7.0+) – plug in for Internet Explorer 6.0 Adobe Flash Player is required for Visual Composer (both designtime and runtime). This is located at:
http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash

Ensure that the BExAnalyzer Application has authority to create dll’s in the user’s temp folder

If you have a viruscanner or DLL Creation blocking, make sure you allow the BExAnalyzer the authorization to create temporary DLLs as this occurs when the BEx Analyzer is launched. The dlls are generated from the .NET xml serialization framework and are only persistent while the application is running. These are deleted when the application is closed.

Verify SAPGUI Settings for BI

In excel, go to Tools -> Macro -> Security -> Trusted Publishers Verify the SAP AG certificate and make sure “Trust Access to Visual Basic Project” and “Trust all installed addins and templates” are checked.

Run C:\Program Files\SAP\FrontEnd\Bw\sapbexc350.xla and ensure there are no red files…

Run C:\Program Files\SAP\FrontEnd\Bw\sapbexc700.xla and ensure there are no red files…

Server Side Settings

Step 1 – Ensure that your ABAP and JAVA systems are on the same fully qualified domain name. There are numerous cross-domain issues that could occur. Also, ensure that all communication server side is using the fully qualified domain name.

Step 2 – You may be missing style elements which could cause incorrect rendering. If you are still having issues, try switching to an SAP Delivered Theme instead of Custom Theme on the Portal.

Summary

Keep in mind that this blog and the components are as of 7/26/06

To report this post you need to login first.

119 Comments

You must be Logged on to comment or reply to a post.

    1. Prakash Darji Post author
      Thanks! Glad it helped. If you encounter any other frontend browser issues, feel free to post them here as I’m looking to make this list as comprehensive as possible….
      (0) 
      1. Mayil Srenivasan
        Hi Prakash, This was really helpful in getting our new frontend. One thing i want to share which is mentioned about .net framework 1.1, those prerequisites need to be installed before before sap Gui install. I didnt have .net framework installed and when i Installed the Gui the BI add on is greyed which means you wont get the new Bex front end. After .net framework installation i could see i can select the new NW2004s BI addon. I found this out only after installing and uninstalling couple of times as still had the old 3.5 frontend. Anyways Thanks for the post. Also for everyone go each and every step as in the Blog. Great Blog. Thanks
        (0) 
        1. Prakash Darji Post author
          Thanks for the comments. I updated the BLOG to include the .NET install first and made a note that it is required before SAPGUI. I also added information about any viruscan utilizy or DLL blocker that might get in the way as well, so check that out as well in case you run into issues.
          (0) 
              1. Ram Gowda
                Prakash, we are having trouble with our New 7.0 Bex Analyzer tool as well, the issue is that the query runs fine for a smaller set of data….but whenever we drilldown by a more granualr characteristics which is estimated to bring in say 40K or 50K lines into the excel output, it always fails with a message that the client is out of memory….we have also noticed that a lot of memory is consumed in orders of 2 GB before it errors out….The same test works perfectly fine in the 3.5 Version of bex Analyzer….We are on GUI 7.10 and have updated all latest patches BI710_2-10004472 & GUI710_3-10002995…We have followed all the steps you have mentioned in this blog while installing the GUI…Can you help us or have you encountered this situation before?
                (0) 
                1. Prakash Darji Post author
                  I would log a message on this. I haven’t encountered this problem on my labtop, but I also have very good hardware…

                  Cheers,
                  Prakash

                  (0) 
                  1. Ram Gowda
                    I have already logged a message with them it has been already 3 weeks but they are still unable to find the root casue of the issue……They are actually suggesting me that i should not run a query which has an output that large in Bex, but that is unacceptable because the same query runs fine in older 3.5 bex analyzer….I have tried running this query on machines that has  4GB/ 2GB and even 1 GB RAM but I still get the same error. Do you know typically what is the hardware size you have to have to run queries like this one….One other surprising thing is wht the newer tool takes so much more memory while the 3.5 version is modest in its usage of memroy about 250-300 MB max.
                    (0) 
                    1. Prakash Darji Post author
                      I would expect that a query that works with the BW 3.5 version should also work with the 04s version. Please send an email to Rohit.Kamath@sap.com to see if he can followup with you on your customer message as I’m no longer working on NetWeaver Frontend Topics…
                      (0) 
                        1. Community User
                          Facing the same problem of client run out of memory. We have 4 sheets in our work book and it gives this error. Initially we had 5 sheets and after this error was encountered we reduced the no of sheets to 4. Records count is also not that large to throw this kind of error. We are in BEx 7.1. Please help me out if you guys got any solution.
                          (0) 
          1. HI Prakash,

            I have installed NW2004s SR1 on Windows 2003 server with Oracle 10.2 database.
            When i am checking in SPAM —>Package level–> I can see that my installed components like SAP_ABA, SAP_BASIS, PI_BASIS, SAP_BW have a level of 0010. I have installed the SPS 7 upto 10 in my system, as by default Nw2004s SR1 installation has SPS6 with it.

            I had problems in opening Report Designer and Web Application designer(/thread/279484 [original link is broken]) for which i have been told to install the Frontend Patches.

            According to the blog by Mr.Prakash Darji(Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation)
            and the procedure given it, I have downloaded the latest FrontendPatches like

            1.SAPsetup for SAP GUI 6.40—-SAPsetup640_23-10001615.exe
            2.SAP GUI for Windows 6.40 Patch—SAPgui640_22-10001615.exe
            3.SAP BW 3.5 AddOn Patch —bw350_11-10001615.exe
            4.SAP Netweaver 2004s BI AddOn Patch—Bw700SP10_1000-10001615.exe and started installing one by one in the same sequence.Ihave closed all SAP applications while installing.

            I was able to install the first three successfully. But while installing the 4th one SAP Netweaver 2004s BI AddOn Patch—Bw700SP10_1000-10001615.exe I am getting the following error.

            ” The patch file C:windowsTEMPSAP5.tmp could not be opened. Please make sure the file exists and is a valid frontend patch.”

            I have checked the location C:windowsTEMP and i can see the file exists. I get different file names each time i start execute it again like SAP45.tmp, SAP4B.tmp etc.

            Please tell me what could be wrong??

            Also I have installed Microsft .NET 1.1 with SP1 and Microsoft Visual J#.net redistributable package1.1

            One more thing is that I have downloaded the latest versions of the .exe files which were mentioned in the above said blog. Do i need to use the same .exe files which are mentioned in that blog or can i use the latest one??

            Also today I am able to see in service.sap.com that there is a new version of .exe file SAP Netweaver 2004s BI AddOn Patch—Bw700SP11_1000-10001615.exe released.  I used this latest patch too. but the same problem exists.

            Please tell me how to proceed further ?

            Awaiting for your reply.

            Thanks
            mv_d

            (0) 
              1. Hi Prakash,

                I have checked in my system. Firewall is turned off and I have disabled the symantec antivirus too and tried installing the patches. The error is same as mentioned .

                “The patch file C:\windows\TEMP\SAP5.tmp could not be opened. Please make sure the file exists and is a valid frontend patch”.

                I am able to install all the frontendpatches released till now for  components like SAP setup for SAPGUI6.40(patches 22& 23),SAPGUI for windows 6.40 patch(patches 21 & 22),sapbw3.5 addon patch (patches.5,9,10 &11) succesfully.

                Where as for SAP Netweaver 2004s BI AddOn Patch , I am able to install succesfully BW700SP09-900,BW700SP09P-901,BW700SP09P-902,BW700SP09P-904 patches.

                The problem comes with other two patches.
                BW700SP10-1000 & BW700SP11-1100.

                When i try to install them I get the error mentioned above.

                Please let me know how to proceed.

                Expecting your early response.

                Thanks
                mv_d

                (0) 
                  1. Hi Prakash,

                    I have installed Microsft .NET Framework1.1 along with its SP1 and Microsft .NET Framework1.1Hotfix (KB886903).I have also installed Microsft Visual J#.NET Redistributable Package 1.1 before installing the Sapnetweaver 2004s Frontend.

                    Afterwards I am installin the patches.

                    Thanks
                    mv_d

                    (0) 
                      1. Prakash Darji Post author
                        Work with customer messages on this. I’ve listed any of the issues I’m aware of. I think it’s probably a firewall, admin rights, or virus scanner, but work with sap support to troubleshoot.
                        (0) 
      2. shilpi reddy
        Hi Prakash,

        we are currently testing the compatibility for Firefox browser on Windows Xp to execute queries frow 2004s & 3.x Query designer

        How would we change the default browser in the Query designer to be Firefox

        i was able to execute the BI 2004s & BW 3.x WebApplication on firefox by default on the same system

        but when ever i execute a query its taking IE 6.0 as the default browser

        Can you please suggest

        Thank You
        Shilpi

        (0) 
    2. Prakash Darji Post author
      Thanks! Glad it helped. If you encounter any other frontend browser issues, feel free to post them here as I’m looking to make this list as comprehensive as possible….
      (0) 
    1. Prakash Darji Post author
      What happens when you try this? Are you getting a particular error? Is it just hanging? Please log a customer message and email the message number to me. This way, you can attach all the logs to the customer message and we can figure out what’s wrong. I’m not having this issue on my install…
      (0) 
    2. Prakash Darji Post author
      I’ve had a few people ask about this already now. There is a note (961995) that you need to apply if you’re having the new tools crash when using mandatory variables.
      (0) 
  1. John Reynders
    I’m a little confused about the BI patch numbering scheme.  There’s a BW7_700 patch level 7 and then the patches switch to levels 700, 701, 800 etc…  Many of the Notes aren’t released yet so it’s hard to determine which to apply.

    Thanks,

    John 

    (0) 
    1. Prakash Darji Post author
      The easiest thing to do is go to service marketplace and see the patches. The base component patches for NetWeaver 2004s start with the Support pack number followed by the patch level.

      Therefore,
      700 is SP7 with no patches
      701 is SP7 with patch 1
      702 is SP7 with patch 2
      800 is SP8 with no patches
      801 is SP8 with patch 1
      etc…

      The higher the number, the higher the patch….

      (0) 
  2. Prakash Darji Post author
    I recently became aware of MS IE patch KB918899 causing issues when trying to login and use applications on the NetWeaver Portal (this include BEx Web Analyzer). I would hold off applying MS IE patch KB918899 until this comes to a resolution.
    (0) 
  3. Pom Das
    Good solid weblog,

    802 is now out and is much more stable.  Any ideas when SAP plan to release a hotpack to delete variables from within the query designer and not through rszdelete.

    (0) 
  4. Hi Prakash,
    I have NETweaver2004s,BI 7.0. I have installed SAPGUI 6.40 comp.5. and have istalled the latest FEP Bw700SP08P_802-10001615. the backend SP level is 8. Despite this I am not able to use the BEX analyser or any other BEX component from frontend.When I open the analyzer option brom BEX it,opens the Excel and when I try to open any query, I get the SAP logon option but after logging on Nothin happens, and screen remains to the normal Excel screen.Its the same with all the other BEX components. Can you please help??

    regards,

    Ravs

    (0) 
      1. Hi Prakash,

        I have checked everything and it matches all the prerequisites.
        Excel is 2003 SP2 and .Net is 1.1 which is as specified. the same problem remains evenif I call the BEX from tcd RRMX.  I have run the BEX check installation file also and it shows everything ok.Heres a snapshot of the BEX Trace file. May be this would have some clue.

        BExConnect.Trace3: 0.898713
        BExExcelTraceListener.AddTraceListener: Added a tracelistener for Version: 7005.5.290
        BExConnect.constructor2: 309.656557
        BExMenu.CreateSubMenu1: 0
        BExMenu.CreateSubMenu2: 0.199714
        ListSeparator: ,
        GetSystemInformation
        SUNI Const: 0
        CommunicationFactory.GetSystemInformation (Setting Conn 1)): 0
        CommunicationFactory.GetSystemInformation (Setting Conn 2)): 0
        CommunicationFactory.GetSystemInformation (Setting init Propties)): 0
        CommunicationFactory.GetSystemInformation (SUNI.FUNCTION_EXISTS)): 0.499285
        Serialization failed: Unable to generate a temporary class (result=1).
        error CS1514: { expected
        error CS1001: Identifier expected
        error CS1031: Type expected
        error CS1519: Invalid token ‘{‘ in class, struct, or interface member declaration
        error CS1514: { expected
        error CS1001: Identifier expected
        error CS1031: Type expected
        error CS1519: Invalid token ‘{‘ in class, struct, or interface member declaration

        RSR_XLS_RFCtrc: 2.696139
        CommunicationFactory.LogOn: 4.094137
        BExConnect.LogOn: 34.550522
        BExExcelApplication.OpenQuery: Not Connected
        BExConnect.CloseWorkbook: BExAnalyzer.xla
        BExConnect.Closed
        BExConnect.Dispose: Disposing BExConnect
        BExConnect.Dispose: Disposing BExConnect 1

        Thanks,
        Ravs

        (0) 
        1. Prakash Darji Post author
          Hey Ravi,

          Recently, I had a customer who had a similar issue. You need to ensure that the BExAnalyzer Application has authority to create dll’s in the user’s temp folder. If you have a viruscanner or DLL Creation blocking, make sure you allow the BExAnalyzer the authorization to create temporary DLLs as this occurs when the BEx Analyzer is launched. The dlls are generated from the .NET xml serialization framework and are only persistent while the application is running. These are deleted when the application is closed.

          I’ve updated this BLOG to include that information. Make sure you turn off any viruscan/adblocking software and test again. For productive environments, you can turn that back on, but make sure you allow the BExAnalyzer authorization to create DLLs in the user’s temp folder.

          (0) 
        2. Jesper Christensen
          Ravi,

          I had the exact same problem. The solution is not simple to find but here it is:

          1. Check to see if you have .net hotfix KB886904 installed on the pc
          2. Uninstall it as it is for .net 1.1
          3. Install .net 1.1 SP1
          4. Install .net 1.1 hotfix KB886903 which is the one for .net 1.1 SP1

          This should resolve your problem.

          Best regards
          Jesper Christensen

          (0) 
  5. Hi,

    First I uninstalled my GUI 620 and run sapsweep.  In excel I could not find “Detect and Repair” Perhaps there are  some restrictions in the installation from our admins. I have Excel2003.
    Then I installed everything as you described it. But when I start the WAD for BW 3.x I receive an error “Runtime error 438 – object does not support this method…”

    What went wrong? I also installed all the actual patches…

    Kind regards
    Stefan

    (0) 
  6. Sini Kumar
    Hi Prakash,

    Patch level : SPS 8/ FEP 802

    PROBLEM: Workbook with VBA works in 3.X Bex Analyzer.
    Opening the same workbook and saving it in NW2004s BEx Analyzer goes to debug when we run the macros in NW2004s Bex Analyzer.(logged in to BW sysytem)
    The macros run fine when opened in NW2004s Bex Analyzer and saved locally in the desktop. The same workbook when opened in NW2004s Bex Analyzer without logged on to BW system also goes to debug mode when the macro is run.

    Trace Info:
    OpenWorkbookOpenTheSavedWorkbook 4
    BExExcelApplication – OpenWorkbookOpenTheSavedWorkbook —- Windows visible is set to true
    RSR_XLS_RFCtrc: 0.300558
    BExExcelItem.Range(Overload2): Exception from HRESULT: 0x800A03EC.
    BExExcelApplication.New: Invalid index.
    BExExcelApplication.New: Upgrade failed
    BExMenu.AdjustToolbarsNavigation: Object reference not set to an instance of an object.
    RSR_XLS_RFCtrc: 0.300558

    NOTE: It is hard to work on changing the macro because after making changes and running in the NW2004s Bex Analyzer gives a critical error dump.

    Eg of the dump: Trace Info
    System.Runtime.InteropServices.COMException (0x8002000B): Invalid index.at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)at com.sap.bi.et.analyzer.addin.BExExcelApplication..ctor(String iWorkbookName)
    Invalid index.at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)at com.sap.bi.et.analyzer.addin.BExExcelApplication..ctor(String iWorkbookName)

    I am having the following installed on my desktop.
    Microsoft .NET Framework 1.1
    Microsoft .NET Framework 1.1 hotfix (KB886903)
    Microsoft Office Professional edition 2003
    Windows XP service pack 2

    Please let me know what needs to done also let me know if you need any further information.

    Thankyou,
    -Sini

    (0) 
      1. Sini Kumar
        Hi Prakash,

        Thankyou for the reply!

        Before I login a customer message, a quick question.Right now we do not have “Microsoft Visual J# .NET Version 1.1 Redistributable Package” installed on our desktop. So just wondering whether this will have any serious impact on the VBA or macros? I know that this is a Prerequisite with SPS 8/ FEP 802.

        Please let me know if you have any information on this.

        Thankyou,
        -Sini

        (0) 
        1. Prakash Darji Post author
          Hey Sini,

          I would make sure you have the J# .NET 1.1 installed BEFORE upgrading to FEP802. In general, this shouldn’t have an impact on the behavious of macros, but it does influence the application handling and events which could call macros. Therefore, I wouldn’t rule it out. I’m pretty sure your issue isn’t related to this, but I would run a clean install based on the steps in this BLOG (every step is critical) and let me know how it goes..

          (0) 
          1. Sini Kumar
            Hi Prakash,

            Thanks again for the quick response.

            Can you please tell how important is it have “Microsoft Visual J# .NET Version 1.1 Redistributable Package” installed and it’s dependencies with the Front End tools? It is important to know because this is going to be a global install.

            Please let me know if you need any further information.

            Thankyou,
            -Sini

            (0) 
    1. Hi.
      I found your post in this blog. I want to know how did you resolve the problem about this message:
      Exception from HRESULT: 0x800A03EC

      I have the same message in Bex Analyzer 7.0 Please give some help.

      Best regards,

      Karim

      (0) 
  7. Mark Janda
    From the Adobe SVG Viewer download area, it states:
    Please note that Adobe has announced that it will discontinue support for Adobe SVG Viewer on January 1, 2007.
    What does this mean to the future of Visual Composer?
    Regards,
    Mark

    (0) 
    1. Prakash Darji Post author
      The documentation I’ve seen on Adobe’s website says January 1st, 2008. SAP is working on exploring SVG options with Adobe and others on this. As more information becomes available, I’ll update this.
      (0) 
        1. Prakash Darji Post author
          I’m no longer working on these topics, so I’m not sure, but I believe that it is no longer required in the latest versions of Visual Composer.
          (0) 
  8. Markus Doehr
    I don’t wanna offend someone here – but isn’t that a really sick thing – all those dependencies? And even the sequence of installing necessary dependencies must be taken care of, otherwise it may or may not work – and you will truely never find out why it does not.

    Of course, it’s nice for developers – and if you have one single machine to do this on, but you will run into serious problems, if you users don’t have local administrator rights, you install MS hotfixes for IE via WSUS and various other issues. Because one is unable to find out, why something is not working, the recommended procedure is to remove everything, reboot and reinstall. Really sick…

    Just my EUR 0.02

    Markus

    (0) 
    1. Prakash Darji Post author
      Hey Markus,

      The title of my BLOG is troubleshooting the frontend install. Keep in mind this is only for troubleshooting. If you go through the install and don’t have problems, great. Most of our customers aren’t having problems. This procedure talks about troubleshooting. Also, this isn’t the only way to do it, but is the simplest way for people who don’t want to “debug”. You can always debug by using windows process explorer and things like that, but again, most people aren’t comfortbale with that. That’s why I am saying they should re-install.

      (0) 
      1. Markus Doehr
        Hi Prakash,

        as I can tell from my own experience people DO have problems with that stuff. It will work if you start doing all that on a clean labor installation – but if you have GUI versions out there already installed, you have MS-Office out there – the installations will get very troublesome just due to the fact, that SAP adds dependencies over dependencies, third party software dependencies, fragments of old software in the registry, if you remove software etc; that whole scenario won’t work e. g. if you install MS-Office 2003, then all the GUI apps and then add SP1. You will need to set registry permission for the users and other things.

        I would REALLY REALLY appreciate, if there won’t be any more additional software packages necessary  but just a plain GUI.

        And the worst thing is, that you need Internet Explorer, which we abandoned completely out of our company. That piece of software in fact IS a *major* security issue and it makes us think whether NW2004s is the way to go or stay on older versions of BI – because those versions work well with Firefox and/or Mozilla.

        Neverless, thank you for this blog, I will certainly look at it next time I’m having problems.


        Markus

        (0) 
  9. Hi,

    I have a problem with the Bex Analyzer that is driving me crazy. Before I continue let me tell you that I have upgraded my complete GUI to the latest patch levels (NW2004s) as described in this excellent blog. I even have also updated my Microsoft Office with the latest patch levels. (2003 SP 2)

    What is my problem ?

    1) I launch the Bex Analyzer and run a query : all ok
    2) Via Tools > Edit Query I jump to the Bex Query Designer to manipulate the query : all ok
    3) Then in the Bex Query Designer I click on execute to display the new result in the Bex Analyzer again but this is where the problems start. The Bex Query Designer is closed (as expected) but my Bex Analyzer (Excel sessios) freezes/blocks completely with the “mouse cursor” making strange movements.

    Please note that I also shut down my virus scanner. After applying loads of patches (SAPgui and Office) the problem remains. Could anyone give me a hint before I have to reinstall my computer ?

    The Bex Analyzer and Query Designer work perfect independend from each other. I also don’t have any erors when checking the sapbexc macros.

    thanks

    Wim

    (0) 
  10. Suhas Bhat
    We are in the process of upgrading to BI 2004s. As part of planning process, we installed new BI2004s front-end tools as per this blog and it works great.  We ran c:\program Files\SAP FrontEnd\BW\sapbexc700.xla and it showed that installation was perfect.

    But then we wanted to remove old BW 3.5 front-end tools (so that our users won’t be confused). We want to keep only one (latest) set of front-end tool. For this we used SAP Front-End Configuration wizard and unistalled SAP BW add-ons (add or remove SAP Front-end components in the component selection wizard) We deselected SAP BW front-end. After unistalling the BW add-on we ran sapbexc700.xla again. This time it gave error – SAPBrowser.SAPBrowserCTrl.1 not regestered. Run-tine error 1004. Application-defined or object error.
    So question is what is the correct way of installing new BI2004s front-end tools and removing BW3.5 front-end tools.
    Suhas Bhat.

    (0) 
    1. Prakash Darji Post author
      I haven’t run that scenario. You could just install initially with only the BI Addon and not the BW Addon and that should work. Otherwise, to troubleshoot your scenario, log a message.
      (0) 
      1. Suhas Bhat
        Hi Prakash,
        Thanks for a quick reply.
        We tried the scenario you have suggested also.
        We installed just BI-Add on without BW-addon installation. Still when we ran
        C:\Program Files\SAP\FrontEnd\Bw\sapbexc700.xla
        we got the same error message mentioned in my first message.
        Thanks,
        Suhas Bhat.
        (0) 
          1. mateen asghar
            I have tried everything in this blog, however, when i run the query designer i still get the old query designer. what is wrong? also i do not see the new xla files in the bw folder. help……..
            (0) 
        1. mateen asghar
          I have tried everything in this blog, however, when i run the query designer i still get the old query designer.  what is wrong?  also i do not see the new xla files in the bw folder.  help……..
          (0) 
  11. Jeff Moser
    It is stated this is a prerequisite before installing BI Add-on.  Note 964495 is noted as a reference on this topic, I was not successful finding this note, is the note number correct?
    (0) 
    1. Prakash Darji Post author
      This note number is correct. The author is editing the note currently and that is why customers can’t see it. The author will release it again shortly.
      (0) 
  12. Matt Seaman
    We are having a problem on some of our user’s installs where the “Chart”, “Filter”, and “Information” buttons are not showing up when a query initially opens in the BEx Analyzer.  The buttons only show up when the user clicks in the area where these buttons normally appear.  Has anyone else encountered this issue?

    We are running front end version SP9, Patch 4, Rev 372. 

    (0) 
  13. Alexey Nevzorov
    Hi,
    I have a problem with the Bex Analyzer…

    TraceInfo:

    BExConnect.Trace3: 0,46887
    BExExcelTraceListener.AddTraceListener: Added a tracelistener for Version: 7005.5.372
    BExConnect.constructor2: 8,28337
    BExTextPool.New1: 0,93774
    BExTextPool.New2: 3,75096
    BExTextPool.New3: 3,75096
    BExTextPool.New2: 7,34563
    BExMenu.CreateSubMenu1: 0.15629
    BExMenu.CreateSubMenu2: 7.97079
    ListSeparator: ,
    GetSystemInformation
    SUNI Const: 0
    CommunicationFactory.GetSystemInformation (Setting Conn 1)): 0
    CommunicationFactory.GetSystemInformation (Setting Conn 2)): 0
    CommunicationFactory.GetSystemInformation (Setting init Propties)): 0
    GetSystemInformation
    CommunicationFactory.GetSystemInformation (Setting Conn 1)): 0.15629
    CommunicationFactory.GetSystemInformation (Setting Conn 2)): 0.15629
    CommunicationFactory.GetSystemInformation (Setting init Propties)): 0.15629
    CommunicationFactory.LogOn: 0.15629
    ——————-1/29/2007 5:07:03 PM——————-
    System.NullReferenceException: Object reference not set to an instance of an object.
       at com.sap.bi.et.analyzer.addin.BExPerformanceCounter.IncreaseLogOn(Int64 iTicks)
       at com.sap.bi.et.analyzer.addin.BExConnect.Logon()
    Object reference not set to an instance of an object.
       at com.sap.bi.et.analyzer.addin.BExPerformanceCounter.IncreaseLogOn(Int64 iTicks)
       at com.sap.bi.et.analyzer.addin.BExConnect.Logon()
    ————————————————————————–

    I am having the following installed on my desktop.
    Microsoft .NET Framework 1.1 SP1
    Microsoft .NET Framework 1.1 hotfix (KB886903)
    Microsoft Office Professional edition 2003
    Windows 2000 service pack 4
    GUI 6.40 Patch 23
    FEP 09p-904

    NW2004s SPS09

    please let me know if you have any information on this.

    Thankyou, tOL

    (0) 
    1. Prakash Darji Post author
      Make sure you have J# 1.1 installed as well. See details in blog above. If you still have issues, it’s most likely a firewall or virus-scanner issue.
      (0) 
      1. Benarji Ganapathi
        Hi Prakash,

            I can’t able to Display the F1 Help or ABAP Syntax Help or Error Long Text. I think this not a probalem from SAP. Do you have any idea how can i get rid of this issue.

        Please refer my thread in SDN. /thread/316117 [original link is broken]

        Thanks in advance.

        Regards,
        Nagesh Ganisetti.

        (0) 
  14. Dieu fr
    Hi,
    I use Excel 2003, and the gui patch 11.
    I faced an error in the Bex “An error occured, the program has to close” while designing a workbook. And this error always appears when I try to open the workbook.
    I had to re-create the wb.
    An idea of the reason why it dumped ?
    A tip to recover the wb ?

    Regards,

    Dieu

    (0) 
    1. Camilla Schiatti
      Hello Dieu,
      do you still have the workbook problem? Because it is exactly the same problem I have; my gui version is 7.1 and the frontend support package is 0.
      Do you have any clue to solve the problem?

      Thanks
      Camilla

      (0) 
  15. Carsten Sappl
    Hello!

    I have currently some trouble with my BI 7.0 Frontend.

    I have installed the SAP GUI 7.10, witch was not working. Therefore I have deinstalled that GUI and reinstalled SAP GUI 6.40. I have also applied Frontend Patch 23, BW Frontend Patch 11 and BI Frontend Patch 11 or 12.

    I haven’t got any trouble with the backend itself, but I don’t have any Progamm Entries under Start – Programmes – Business Explorer.

    In this directory is a sub directory, containing all BW 3.x Tools, but no BI 7.0 Tools are available.

    Can anybody help??

    Regards,
    Carsten

    (0) 
    1. Rajkumar Gentyala
      Hi,

      I installed SAPGUI 7.10 and SP2 on it. I have all the prerequisites fulfilled.

      Installed .NET Framework 2.0
      WindowsInstaller-KB893803-v2-x86.exe

      I have office 2003 for which I installed.

      office2003-KB907417-FullFile-ENU.exe

      I also did Windows update.

      Before the installation of GUI 710 I did ran sapsweep after uninstalling my SAPGUI 640 SP25.

      Then even used a Registry Cleaner tool.

      Successfully installed SAPGUI 710 with SP2 using SetupALL.exe from DVD 50083078_4.ZIP.

      Now using start –> Programs –> Business Explorer I can execute Bex Analyzer of 3.x and 7.0 successfully.

      But I have an issue in RRMX which gives an error:

      Please install Excel as viewer.
      Message no. BRAIN871

      I also have an issue in Report Designer which is like few of the navigations are not clearly visible in the designer tool and my developers cannot really work.

      I searched SAP Notes and most of such issues are addressed in BI 7.0 SP13. Presently we are on SP12.

      I had resolved my RRMX issue also by changing the Global Settings of Bex Analyzer 7.0 but again I cannot use Bex Analyzer 3.x which gives a runtime error.

      Mostly I feel there is an error in ABAP Program RRMX_START_EXCEL. I do not know how this error will be resolved.

      Does any one has an IDEA about this???

      (0) 
      1. Prakash Darji Post author
        Follow these 22 steps:

        1. Uninstall all previous versions of SAPGUI and BI Addons.
        2. Run Sapsweep.
        3. Make sure you are on minimum of Windows XP SP2 (Note: 1013201)
        4. Update to IE 6 SP2 with latest hotfixes and patches:
                – See blog for details: Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
        5. Ensure Excel 2003 or Excel 2007 is installed (Note: 1013201)
                Excel 2007 support is added as described here: https://websmp209.sap-ag.de/~sapidb/011000358700004483762006E
        6. Install .NET Framework 1.1 (Note: 1013207)
        http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3
        7. Install .NET Framework 1.1 SP1 (Note: 1013207)
        http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38
        8. Install .NET Framework 1.1 hotfixes and patches
                – KB886903
        9. Install .NET Framework 2.0 (Note: 1013139)
        http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en
        10. Install .NET Framework 2.0 hotfixes and patches (Note: 1013139)
                – KB917283
                – KB922770
        11. Install .NET Framework 3.0 (Note: 1013139)
        http://www.microsoft.com/downloads/details.aspx?familyid=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en
        12. Install the DHTML Editing Control for Applications Redistributable Package (Windows Vista Only)
        http://www.microsoft.com/downloads/details.aspx?familyid=B769A4B8-48ED-41A1-8095-5A086D1937CB&displaylang=en
        13. Install Microsoft Visual J# .NET 1.1 (Note 964495)
        http://www.microsoft.com/downloads/details.aspx?FamilyId=E3CF70A9-84CA-4FEA-9E7D-7D674D2C7CA1&displaylang=en
        14. Install Microsoft Visual J# .NET 2.0 (Haven’t validated this requirement yet)
        http://www.microsoft.com/downloads/details.aspx?familyid=f72c74b3-ed0e-4af8-ae63-2f0e42501be1&displaylang=en
        15. Install SAPGUI 7.10 Core
             – 50083078_4 – SetupAll.exe
        16. Run SAP Install for BI 7.0 Addon for SAPGUI 7.10
             – SetupAll.exe
             – (This keeps BI Addon at SP0 but updates revisions of files to newer build for frontend…)
        17. Install SAPGUI 7.10 (patch 2) or later
                – gui710_2-10002995.exe
        18. Manually add shortcut for Bex WAD to Business Explorer in Windows Start Menu
        19. Install MSXML Parser 6.0 or later:
                – http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be21-27e85e1857b1&DisplayLang=en
        20. Install Adobe SVG Viewer 3.0
                – http://www.adobe.com/support/downloads/product.jsp?product=46&platform=Windows
        21. Install Adobe Flash Player
                – http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash
        22. Run Frontend Check Tool (Note: 1013202)

        I haven’t had a chance to validate this completely yet, so that is why I haven’t updated this blog…

        Cheers,
        Prakash

        (0) 
  16. Robert Kenna
    Hi Prakash,
    I have two questions in reference to the Frontend Installation.  You make a reference to Ensuring that the BExAnalyzer Application has authority to create dll’s in the user’s temp folder.  How is this done?
    The other question is what would be missing in my install when running the Analyzer it opens Excel,displays the 2 BI 7 toolbars, but does not request login to the SAP server? I have just installed .Net 2, Office 2003, followed by SAPGUI 7.10.
    Thanks, Bob
    (0) 
    1. Prakash Darji Post author
      If you read this blog in detail, you’ll see that .NET 2.0 isn’t required. .NET 1.1 is required and must be installed. .NET 2.0 will NOT work.

      Ensuring BExAnalyzer Application has authority to create DLL’s in user’s temp folder is handled with Windows Authorization, Firewall Controls, and Antivirus protection software. It varies with what firewall, antivirus, and windows auth profile you use…

      (0) 
      1. Robert Kenna
        Thanks for the prompt reply.  I had not realized that going to NET 2.0 would be a problem (your blog was for July 2006).  I removed .Net 2 and the connection now works.
        (0) 
  17. Jacob Lund
    Hi,

    I’ve tried installing GUI 7.10 og BI Add on 7.00, but my toolbars in the new BEx Analyzer didn’t work after that. I’ve found a note: 1025122 that describes a solution if you are running Office 2003. I just found the note, so what I did instead was the following (which also works):

    I uninstalled the GUI 7.10, BI Add on 7.0, .NET 2.0 and installed a 6.40 GUI (plus all the latest frontend patches) and .NET 1.1 (plus servicepack 1 for .NET 1.1). After that everything works.

    Hope this can help somebody :o)

    Best regards,
    -Jacob

    (0) 
    1. Dear jacob,
      i  installed 6.40 and .net framework 1.1 , i am unable to run my frontend in 7.0 , even i ma getting errors with variable , i am getting run time error.

      regards
      suneel.

      (0) 
  18. Michael Chu
    I have some problems in using BEx 7.1: The toolbar is not worked. Before digging into them, I just want to make sure that Windows 2000 is okay for it.
    Do I need any uppdate/patch for my current OS?

    (Due to the installation guide, XP or the above is the OS requirement)

    (0) 
      1. Ivi Torres

        Problem with Bex Analyzer–


        7/30/2007 8:55:42 AM


        <br/>System.AccessViolationException: Intento de leer o escribir en la memoria protegida. A menudo, esto indica que hay otra memoria dañada.<br/>   en Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object o, Type& objType, String name, Object[] args, String[] paramnames, Boolean OptimisticSet, CallType UseCallType)<br/>   en Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)<br/>   en Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)<br/>   en com.sap.bi.et.analyzer.addin.BExExcelApplication.SetNameAddress(String iName, String iAddress)<br/>   en com.sap.bi.et.analyzer.addin.BExItemFilter.RenderData(Boolean iForceRendering)<br/>Intento de leer o escribir en la memoria protegida. A menudo, esto indica que hay otra memoria dañada.<br/>   en Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object o, Type& objType, String name, Object[] args, String[] paramnames, Boolean OptimisticSet, CallType UseCallType)<br/>   en Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)<br/>   en Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)<br/>   en com.sap.bi.et.analyzer.addin.BExExcelApplication.SetNameAddress(String iName, String iAddress)<br/>   en com.sap.bi.et.analyzer.addin.BExItemFilter.RenderData(Boolean iForceRendering)<br/>


        <br/><br/><br/>

        (0) 
  19. Luke Rudnick
    Hello-

    I have tried everything as advised, but we are still getting “Critical Program Error” message when we try to open a Query via Analyzer.

    We have the settings made per the OSS notes and are running Excel 2003 with GUI 6.40 Patch 24.  We also patched our front-end to the latest version.

    When I refer to the trace, I see this:

    System.IO.FileNotFoundException: File or assembly name BExCompression, or one of its dependencies, was not found.
    File name: “BExCompression”

    I can find no reference to this “BExCompression” anywhere.

    Please help!

    (0) 
    1. Witalij Rudnicki
      Hi Luke,
      Did you find a solution to your problem? I am getting exactly the same. I am just curious if this can be caused by lower patch on back-end side, because front-end is on the highest available.

      Thanks,
      Vitaliy

      (0) 
  20. Victor Figueroa
    Hi, we using SAPGui640 in XP and Note 1050605 working good, but in WindowVista using SapGui7.10 not working when try apply note :
    Note 1050605 – No response for the toolbars in BEx Analyzer 2004s

    Any idea ?

    (0) 
  21. R Ram
    Hi
    When I close the WAD in Bex, I am geting the following error.

    ERROR SAVING WORKSPACE.

    ERROR CREATING STORAGE MEDIA.

    When I tried with other user there is no such error occured.

    could you suggest why this happens.
    is it problem with SAP GUI front end installation.

    Thanks
    Raman

    (0) 
  22. Claire Davila
    We have recently upgraded to 7.0 (SP 13).  What we’ve noticed is that the variable screen seems to take a lot longer to navigate (i.e. several seconds after each check or deletion of a value or F4, etc.).  There are quite a few variables (some mandatory, some not) for the queries in question and removing some of the variables has helped a little.  It seems though that SAP has implemented (technically) a new process to build the screen using Dynamic Document functionality.  So, it seems that it’s trying to rebuild the screen each time running CL_DD_FORM_AREA.  Does this sound familiar?

    We have not upgraded to the latest frontend patch yet (i.e. 14 03) so I”m not sure yet if that will help and have not had the chance to test on an upgraded machine.

    Is this just the new way the variable screen functions?  If so, it will be a training issue for us and we’ll have to re-engineer some queries to remove variables and speed up the processing a bit.  Our users rely on a combination of selections normally, to generate their queries.

    (0) 
  23. steve cooper
    We have installed:
    SAP GUI FOR WINDOWS 7.10 Core Win32 (Patch Level 4) running with BI 7.0 ADDON FOR SAP GUI 7.10 (Patch Level 2.01).

    It works on many of our XP machines, but we get on a fairly regular basis the error:
    – BI 7.0 toolbar is disabled &
    – MS VB error “Run-time error ’91’: Object variable or With block variable not set”.

    Do you have any suggestions as to what specific components this error relates to? 

    regards, Steve

    (0) 
    1. Rohit Kamath
      In Excel Macros Security under ‘Trusted Publishers’ tab make sure both the check boxes ‘Trust all installed Add-ins and templates’ & ‘Trust access to Visual Basic Project’ is checked.

      Also use the ‘Detect & Repair’ option under the Help menu to rectify any MS Excel problems.

      Regards,
      Rohit

      (0) 
  24. Laurie Reid
    We are currently on version 7.0 of BI, using the 3.5 toolset.  As we begin to explore moving to the 7.0 toolset, we have installed both sets of tools on a few PCs.  After installing both sets of tools, when we run BEx Analzyer 3.5 we see both the 3.5 add-in toolbar AND the two 7.0 add-in toolbars in Excel 2003 & Excel 2007.  Is this normal?  If not, is there a note to correct this problem?  Thank you!
    (0) 
    1. Rohit Kamath
      Hello Laurie,

      On the 7.0 toolbar click on ‘Global Settings’ button, under the ‘Behaviour’ tab turn off the flag ‘Launch Analyzer whenever Excel Starts’.  Next time when you launch Excel or 3.x Analyzer you should not see the 7.0 toolbars.

      Regards,
      Rohit

      (0) 
  25. Sini Kumar
    Hi Prakash,

    We have installed SP GUI 7.10 (patch 4)- FEP 201 and office 2007.
    Is visual J# 2.0 a pre-requisite for SAP GUI 7.10?
    OSS Note# 1013139 did not mnetion about the Visual J#.
    Can you please let us know if it is required or not? I thought Visual J# is required for all stack >8, is that a true statement?

    Thanks.
    -Sini

    (0) 
  26. Heren Zhou
    Hi,

    Problem by save a new layout. I see the error:

    call FM RSWR_PREEXECUTION_PROXY to ProgId PP5001_PORTAL_PP5 on host degtlun1025 with SSO not authorized: Authentication failed.

    But SSO working if I login at first in BW then go to Portal.

    RFC Connection in BW system for PP5001_PORTAL_PP5 has a phiscal machine name. But my portal has built on a virtual machine name on the same phiscal machine. Unfornutaley I cann’t change the goal system name directly in RFC connection in BW system.

    could someone give me more ideas?

    Thanks in advance!

    Heren Zhou

    (0) 
    1. Donald Voorhees
      Anyone have any further insight on this issue?  This is exactly what se are seeing but all RFC’s are using virtual names and I still see the issue.
      (0) 
  27. rakesh pimple
    Hi Prakesh ,
       In this blog the Installation steps which you have given for SAP GUI 7.10 & BI 7.0 is really helpful. As per the steps I have Installed SAP GUI 7.10 and BI 7.0 Addon without any error but while executing query I am getting followiing error

    com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error while generating data provider:                          

    Please tell me how to solve this problem

    Regards,
    Rakesh

    (0) 
  28. Annie Chan
    Hi Prakash,

    Thanks for this really helpful information. I was able to solve all problems I had and able to access to BW 3.5 and BI systems now.

    My config:
    SAPGUI 7.1
    SAPGUI Patch Level 5
    BW 3.5 Addon Patch Level 2
    BI Addon Patch Level 3.
    Microsoft Excel 2003
    Update for Microsoft Office 2003 (http://support.microsoft.com/kb/907417
    Windows XP SP 2

    Thank you so much!

    Regards,
    Annie

    (0) 
  29. Raf Boudewijns
    right after step:

    5. Launch Microsoft Excel and run Help -> Detect and Repair to remove any references to SAP Addins.

    I received an error in Excel… it asked me for the CD Rom (which I don’t have as it’s a company pc). Basically Excel somehow got corrupted. Meanwhile I have another pc (for other reasons), but I have a colleague with the same issue.
    Any ideas what might be causing this?

    (0) 
  30. Chintada Shankar
    Hi Prakash,

    This blog helped me a lot, for which i wanted to thank you. We had many issues regarding the frontend which were solved with the help of this blog.

    we are working on the Citrix Server, for any issues needs clarification from you.

    Regards
    Shankar Chintada

    (0) 
  31. Tina Nguyen
    Hi All-
    Having issues with 3.5 BEX variable popup in background, not foreground, thus you must minimize everything to find it. I saw a Note for BW 3.0, we are on 7.0.  Have you seen fixes for this in BW 7.0.

    Definitely like the blog, extremely helpful.

    Thanks,
    Brian

    (0) 
  32. Christian Kretz
    Dear collegues,

    unfortunately I also have a problem with bex analyzer 7.10 patch 6 on windows vista excel 2007 SP1, SAP GUI 710 Final Release patch8. If I try to create a new query of open an existing query and try to change key figures excel 2007 crashes:

    Problemsignatur:
      Problemereignisname:     APPCRASH
      Anwendungsname:     EXCEL.EXE
      Anwendungsversion:     12.0.6300.5000
      Anwendungszeitstempel:     47607042
      Fehlermodulname:     StackHash_94ec
      Fehlermodulversion:     6.0.6000.16386
      Fehlermodulzeitstempel:     4549bdc9
      Ausnahmecode:     c0000374
      Ausnahmeoffset:     000af1c9
      Betriebsystemversion:     6.0.6000.2.0.0.256.1
      Gebietsschema-ID:     1031
      Zusatzinformation 1:     94ec
      Zusatzinformation 2:     73562b270918567264515bfa09c7a59b
      Zusatzinformation 3:     9b11
      Zusatzinformation 4:     fbee0a143683dcce7e7355aa7f5cd423

    Lesen Sie unsere Datenschutzrichtlinie:
      http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0407
    The same configuration on bex analyzer 3.5 works fine but bex analyzer 7.1 shows above error.

    Do you have any idea?

    Thanks and regards,
    Christian

    (0) 
  33. Lucien Barnes
    Good day,

    I created a workbook in Excel 2007 and it works, when the user opens the workbook in 2003 it opens but when they try to do anything like save or refresh, it crashes with “a Critical Program Error has occurred ”
    Does anybody know how to resolve this.

    Regards
    Lucien

    (0) 
  34. Jinny Cao
    Hi,

    I have a question in regards to Web Analyzer. In the default 0ANALYSIS_PATTERN template, there is a “New Analysis” pushbutton. Does this button have authorisation linked to it?

    Thanks
    Jinny

    (0) 
  35. Ales Hruby
    Dear collegues,
    I prepared in BEx 7 very nice workbooks with tables and charts in my Office 2003 – all is correctly.
    Unfortunately customer has Excel 2007 and problems appeared:
    1. Charts collect all table also WITH header (header is in chart as other serie) and also after refresh and saving of the workbook…
    2.It is the same also in standard tamplate BEx
    in customer client (query in Analyzer with chart)
    3. Analyzer 7 on Excel 2007 has terrible performance – secunds on 2003, minute on 2007

    Customer has FE 7 and last SP…

    (0) 
  36. Anand Kumar
    Hello Prakash,

    The following links in the blog no more working. Please activate the links.

    Supported Browsers
    Supported OS and Office Versions

    Thanks.

    With regards,

    Anand

    (0) 

Leave a Reply