Rub time error  7 in business explorer

Hi,
I am trying to create or change the query in BEX Analyzer poppin up with the error
Rub time error  7
Out of memory
An unexpected 'out of memory' error occured in wdbrlog.
1 error(s) are logged.
What could be the problem
Thanks
Priya

hi priya...
chk this similar issue..
BI 7.0 Bex Analyzer Excel Runtime error

Similar Messages

  • Internet Explorer Error after Business Explorer Installation

    Hi guys,
    I just want to know why the Internet Explorer seems to be corrupted (always blank page whichever page you will browse) after Business Explorer installation?
    What will I do to avoid this problem?
    Thanks!!

    Hi ,
    I have updated the GUI for the latest patch , that is 5. and still at sometimes when using query designer "critical Error" msg used to appear.. i have checked the logs but it doesnt give out any clue why this error occurs.. if  ya have any suggestion please let me inform as well..
    Thanks !

  • "404 error" for business explorer

    Hi Expert,
    I installed SAP Business Objects Enterprise 4.0 SP2 for development, test and productive environment and they work fine. Development and Test BOE are installed in a single host instead the productive environment is installed in more hosts, in particular this is the configuration for the productive BOE environment:
    host 1: WAS (Tomcat 6)
    host 2: WAS (Tomcat 6)
    host 3: CMS server 1
    host 4: CMS server 2
    host 5: CMS DB
    After that I installed BOE, I also installed SAP Business Explorer 4.0 in the development, test and productive environment (I installed BE in host 3 and host 4). SAP Business Explorer work fine in development and test system instead is not working in the productive environment. In particular if i go to BI lunch pad (productive environment) and I selected the Business Explorer icon the following error message appear:
    404 Missing Page
    The page you requested is not available on this web server for one of the
    following reasons:
    I checked on Central Management console the status of the Business Explorer servers and they are in status "running".
    I noted that in the development and test system the file explorer.war has been created from the BE installation program in the following folder :
    "D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjectsEnterprise XI 4.0\wdeploy\workdir\tomcat6\application"
    instead in the productive environment the file explorer.war doesn't exist. How can I resolve this critical issue? Must I install some component also in the WAS hosts?
    Thank you for your help.
    Best regards
    gio'

    Looks like you need to do a web tier install on your tomcat server or you could copy the war file over.  How did you deploy your war files when you did your initial install of BOE?  Do you see an explorer folder in your tomcat6\webapps directory?
    -Dave
    Edited by: David Mau on Nov 7, 2011 10:44 AM

  • Business Explorer Error after installation of SAP GUI 7.10

    Hi Experts
    we have installed  SAP GUI 7.10 successfully and there seems to be an error on Business Explorer.. while processing some of the queries in designer it gives out an error message " critical program error occured.The program has to close.Please refer to the trace for further information" this caused  the entire application to close.
    Trace : Error(08.11.07 15:19:10.965): mode completion failed, rc=-1 (error=6 UI ThreadHdl=1436)
    please advise on this
    thanks
    lasitha

    Hi ,
    I have updated the GUI for the latest patch , that is 5. and still at sometimes when using query designer "critical Error" msg used to appear.. i have checked the logs but it doesnt give out any clue why this error occurs.. if  ya have any suggestion please let me inform as well..
    Thanks !

  • SAP GUI 7.10 business explorer gives

    Hi Experts
    we have installed SAP GUI 7.10 , patch 4 , successfully and there seems to be an error on Business Explorer.. while processing some of the queries in designer it gives out an error message " critical program error occured.The program has to close.Please refer to the trace for further information" this caused the entire application to close.
    do i have to upgrade the patch level? or please advise on this.
    thanks..!

    It may help you to know I currently have two OSS messages raised for just this error - I suggest you do the same!
    The combination of software elements that you have may well be the issue, but raising the OSS will help take you through the process of identifying the issue.
    The 710 GUI seems quite flaky still, I'm just hoping it will be robust before we roll it out globally.
    Points if that helps?
    Patrick

  • Publishing and Overwriting a Universe, Updates new measures quickly in Business Explorer / Information Spaces but taking time in dashboard to be updated.

    Hi gurus:
    I have a continuous problem while Publishing and Overwriting a Universe from IDT, new measures UPDATES quickly in Business Explorer / Information Spaces but taking time in dashboard to be updated. it approximately takes half an hour to be updated while accessing universe from dashboards.
    Regards:
    Jawad Khalid

    Hi gurus:
    I have a continuous problem while Publishing and Overwriting a Universe from IDT, new measures UPDATES quickly in Business Explorer / Information Spaces but taking time in dashboard to be updated. it approximately takes half an hour to be updated while accessing universe from dashboards.
    Regards:
    Jawad Khalid

  • Business Content Activation - run time error

    Hi guys,
    We were at plugin 2002.1. We installed PI 2002.2 and PI 2003.1 on top of it.
    After the plug-in upgrade, we are at support pack 9 for SAP-BW and 13 for BI-Content. For aba and basis, we are at 620 and support pack 32.
    As part of the regression testing after the 2003.1 plugin upgrade, we found out that the business content activation abends with the following run time error.
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Looks like it is trying to insert into table RSOLTPSOURCEFIET and the row already is existing. I thought the activation process is supposed to update something if it is already out there.
    If we just select the 'only necessary', the activation goes through ok, but if we select 'before and after in the data flow', we get this abend.
    Any clues???
    Best regards,
    makaleem

    Hi Seow,
    This is how I resolved it. I looked at the ST22 closely and one of the messages indicated that the number range is missing in tran SNRO for an infoObject. I created an entry for that infoobject using SNRO and tried activation and it worked.
    When we created an OSS for SAP to look into it, they recommended the following two things. I tried these two but it did not work. I am mentioning them below just in case they may help you.
    1) Sometimes there is inconsistency in the content cache when trying to activate objects and we have to delete the repository cache. To delete the repository cache, go to RSA1 ---> Business Content -
    > Extras ---> Delete Rep Cache
    2) Execute SAP_DROP_TMPTABLES program for types 1,2,3 and 6.
    If this helps, don't forget to assign points.
    Abdul

  • Business Explorer (BEX) Query open Error

    Hi
    When opening  BEX(Business Explorer) Queries from Excel  ,  it asks for System to choose.
    But business doesn't want to see this option. It should go directly to open query selection for the system it has logged in.
    Say , it has logged in BIQ  , it should go to open the queries selction for BIQ without asking to login to BIQ as user has already logged in BIQ.
    In some other users desktop , when they open Queries from Excel it directly goes to open query selection without prompting for System selection
    We are using  SAP GUI 7.20  patch 4 ,  BEX 3.5 patch 3.
    We also have BEX 7.20 but we will not use it
    We tried to with applying all latest patches but we still get the same error.
    We perfomred a Excel test provided by SAP , that shows gree.
    Business wants to use SAP GUI 7.20 patch 4 and BEX 3.5 patch 3.
    Can any one help on this ?
    Note:  please don't recommed to apply latest patch to  GUI or BEX  or apply patch to System component. . Thats not the solution as the current version works in some other desktops.
    Please let me know if you want to understand more in this scenario.
    Thanks
    Rabi Kumar

    Dear Das,
    In that case you need to call the RRMX transaction from your BW system and  if SSO works , then it leads you directly
    to the Open save dialog.
    For SSO , I would suggest you to please implement the below note:
    Note 1498947 :    RRMX: Logon mechanism for 720 GUI.
    Regards,
    Arvind

  • Business Explorer install error

    Hello all,
    I am currently trying to update our existing Business Explorer 3.5 (patch level 11) to the latest patch version 13 with the sapadmin tool. The installation works fine but when we try to open a query in business explorer excel addin I get the following error:
    <install error> Missing ActiveX component: Business Explorer Open Dialog.
    The version information states that Bex is at patch level 13.
    If I then manually install the patch (no objections that i'm already at patch level 13 here), everything works fine. Any thoughts on this?
    Thanks

    Hey all,
    Good news, i found out what the problem was. One of the dll's needed was not registered:
    wdbfodlg.dll
    I now manually registered this dll in the install script, but it remains strange that it was not included in the normal installation via SMS.
    Greetings,
    Tom Willems

  • Business Explorer 7.0 Installation error.

    Hi friends,
    we have installed Business explorer 7.0 but when we execute the query designer the system gives a error as
    "".NET framework Initialization error"" ""unable to find a version of the runtime to run this application"". even when we execute WAD it gives the same error. I tried reinstalling .NET framework for the suitable version but did not helped.
    Please help me in finding a solution to this error.
    Thanks,
    Nagesh.

    Hi Nagesh,
    Please install the components in the following steps :
    I     Unistall older versions of sap
    II    Uninstall dotnet 1.1 if it exists
    III    Restart
    1    check for MS SP2
    1.1 Install dotnet 2.0
    1.2 Restart
    2    SapGuiSetup
    3    SapBiSetup
    4    bi710sp03_300-10004472
    5    gui710_3-10002995
    6    Hotfix - "office2003-KB907417-FullFile-ENU" or download the same from
    http://www.microsoft.com/downloads/thankyou.aspx?familyId=1b0bfb35-c252-43cc-8a2a-6a64d6ac4670&displayLang=en
    7   Restart
    Hope this resolves your problem
    Cheers.

  • Business Explorer  Analyer Login Error

    All Expert:
        I want to login Business Explorer Analyer 3.X,When I input username and password,after confirm,it display:
      Message Group
    RFC_ERROR_PROGRAM
    Message 
    Ent
    By the way,Web application Desinger is the same problem.
    please answer this question,Thank you very much.

    I update SAP GUI and then it is ok.
    update file name is :gui720_6-10007878.exe.

  • Run time error while logging from a client

    hi all,
    My server is connected to 10 clients. out of that 2 clients are suddenly showing error while logging.
    Microsoft visual studio C++(error window)
    run tme error
    debug
    error c:/program files/sap/sap business one/sapbusiness one.exe
    This is the error window showing. I have uninstalled the client and again installed it but with no results. I found in the path mentioned above there should be the client run file "sap business one.exe", which is not present. I mean the .exe is missing. the file shows "sap business one" only.
    whenever we install the client then i the folder
    c:/program files/sap/sap business one
    there is a .exe file. which is not being installed in this client machine. what is being installed is a
    sap business one (not a .exe)
    when the client icon in the desktop is made to run, the log in screen appears, the list of company and db appears. I have recently upgraded the server to PL 42. so when a company is selected for log in then the client upgrade message also appears. when "ok" is clickd the run time error appears.
    where as all other clients are running well after the upgrade.
    please help with a solution.
    regards,
    Raj
    Edited by: debraj bhattacharyya on Dec 5, 2008 5:37 PM

    I have explored all the areas and I hope the problem is with the exe file only. Because I have tried an option. I copied the entire file SAP Business One (in the C:
    Program Files\sap) from one client which is working to the client where the error was showing. Then the it started working properly.
    But I donot think this will be a permanent solution. Because on reinstaling the client the SAPBusiness One.exe does not appear and to the best of my research i am quite sure that may be the problem.
    Any idea from any one for a perfect reason.
    Regards,
    Raj

  • Anybody knows Business Explorer Analyzer well?

    Hi,experts
    I installed SAP GUI 710 with Business Explorer.
    My actions are Business Explorer->Anylzer->Find-><search my query and select>
    There are three variables in my query, and an error message arised when I selected values for variables.
    The error is generally :
    "Unhandled exception has occurred in a component in your application. If you click continue, the application will ignore this error and attempt to continue.
    Object reference not set to an instatnce of an object"
    The details of this error is :
    "See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an object.
       at com.sap.bi.et.selector.BExSelectorDialog.SelUIDialog.HandleUnhandledException(Exception iException)
       at com.sap.bi.et.selector.BExSelectorDialog.SelUIDialog.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
       at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
       at System.Windows.Forms.Control.WndProcException(Exception e)
       at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow)
       at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
       at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
       at System.Windows.Forms.Control.set_Visible(Boolean value)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
       at System.Windows.Forms.Form.ShowDialog()
       at com.sap.bi.et.selector.BExSelectorDialog.SelUIDialog.GetUserSelection()
       at com.sap.bi.et.selector.BExSelectorDialog.SelUIDialog.ShowSelector()
       at com.sap.bi.et.selector.BExSelectorDialog.SelUICtrlDDBox.InvokeSelector()
       at com.sap.bi.et.selector.BExSelectorDialog.SelUICtrlDDBox.OnInvokeSelector()
       at com.sap.bi.et.selector.BExSelectorDialog.SelUICtrlDDBox.picValueHelp_Click(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    BExAddin
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.461
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExAddin.DLL
    BExCommunication
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.109
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExCommunication.DLL
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Microsoft.VisualBasic
        Assembly Version: 8.0.0.0
        Win32 Version: 8.0.50727.42 (RTM.050727-4200)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    BExControls
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.109
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExControls.DLL
    BExCommon
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.109
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExCommon.DLL
    BExApi
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.461
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExApi.DLL
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System.Xml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    System.Configuration
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    BExControls2
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.108
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExControls2.DLL
    Accessibility
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.42 (RTM.050727-4200)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    BExGeneratedAll
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.108
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExGeneratedAll.DLL
    SAP.Connector
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.0.23
        CodeBase: file:///C:/WINDOWS/assembly/GAC/SAP.Connector/2.0.0.0__50436dca5c7f7d23/SAP.Connector.dll
    System.Web.Services
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.42 (RTM.050727-4200)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
    wy59pywg
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    0shnpga1
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    BExOpenSaveServices
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.100
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExOpenSaveServices.DLL
    BExSharedImageList
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.109
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExSharedImageList.DLL
    office
        Assembly Version: 11.0.0.0
        Win32 Version: 11.0.8161
        CodeBase: file:///C:/WINDOWS/assembly/GAC/office/11.0.0.0__71e9bce111e9429c/office.dll
    stdole
        Assembly Version: 7.0.3300.0
        Win32 Version: 7.00.9466
        CodeBase: file:///C:/WINDOWS/assembly/GAC/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
    mjbzyxwh
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    CustomMarshalers
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.42 (RTM.050727-4200)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
    BExThemes
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.109
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExThemes.DLL
    Interop.SAPLogonCtrl
        Assembly Version: 1.1.0.0
        Win32 Version: 1.1.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/Interop.SAPLogonCtrl.DLL
    SAP.Connector.Rfc
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.0.23
        CodeBase: file:///C:/WINDOWS/assembly/GAC/SAP.Connector.Rfc/2.0.0.0__50436dca5c7f7d23/SAP.Connector.Rfc.dll
    kxd_bgue
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    9zjfbkq6
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    6uc-ceve
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    droojvpq
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    qxea3cmy
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    BExCAControls
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.109
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExCAControls.DLL
    z_vhnx0q
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    mq0gr2hx
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Syncfusion.Tools.Windows
        Assembly Version: 3.202.1.0
        Win32 Version: 3.202.1.0
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Syncfusion.Tools.Windows/3.202.1.0__3d67ed1f87d44c89/Syncfusion.Tools.Windows.dll
    Syncfusion.Shared.Base
        Assembly Version: 3.202.1.0
        Win32 Version: 3.202.1.0
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Syncfusion.Shared.Base/3.202.1.0__3d67ed1f87d44c89/Syncfusion.Shared.Base.dll
    Syncfusion.Core
        Assembly Version: 3.202.1.0
        Win32 Version: 3.202.1.0
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Syncfusion.Core/3.202.1.0__632609b4d040f6b4/Syncfusion.Core.dll
    System.Design
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll
    cighgv5i
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    System.Data.SqlXml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Data.SqlXml/2.0.0.0__b77a5c561934e089/System.Data.SqlXml.dll
    27ptlp0k
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    nowl-pit
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    d44txt7i
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    p_rt5zcn
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    btjzax0k
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ugukkqcw
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    7poxikge
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    uenzzc5h
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    id3lwaln
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    nwbbt9xy
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    cvdicolx
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    BExCompression
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.109
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExCompression.DLL
    yuvgtrc8
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    BExVariableScreen
        Assembly Version: 0.0.0.0
        Win32 Version: 0.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExVariableScreen.DLL
    BExSelectorAPI
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.145
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExSelectorAPI.DLL
    BExSelectorDialog
        Assembly Version: 7100.0.0.0
        Win32 Version: 7100.0.0.145
        CodeBase: file:///C:/Program%20Files/SAP/Business%20Explorer/BI/BExSelectorDialog.DLL
    8pba1gad
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    e0-pe0q3
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    by6vzrc3
        Assembly Version: 7100.0.0.0
        Win32 Version: 2.0.50727.832 (QFE.050727-8300)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Hi,
    Take a look at these screencams.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d002a24a-785c-2a10-4fa6-cc15ef25502a
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90b95f53-7c5c-2a10-f98d-cc78ec4ec12d
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0918b55-bf5f-2a10-b6a9-dbb16f13ae1b
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0068e7b7-cdaf-2a10-5bbe-f10ce464ecbf
    Regards.

  • No update of Business Explorer 3.50 and SCM via Installation Server 6.40

    Dear all
    We use SAP Installation Server 6.40 to deploy SAP Front End 6.40 and updates. For new installations, target systems will get the latest version of SAP GUI 6.40 (PL 27), Business Explorer 3.50 (PL 13) and Supply Chain Management add-on (PL 6).
    On existing installations only SAP GUI will be patched resp. updated. Business Explorer 3.50 and Supply Chain Management add-on will not be patched by Installation Server. We have checked this by local installation of patch (patch level 13, your present patch level 4). What is going wrong? Has anyone a hint how I can solve this problem?
    Thanks
    PK

    Hi. I'm think first you need to chek this :
    Viewing the Log
    Use
    You can check the installation by viewing the log file sapsetup.log. The log file can be found in:
    • C:\WINDOWS\ under Windows XP
    • C:\WINNT\ under Windows 2000
    The most recent log has no number. The older logs are numbered. The higher the number, the older the log. Each time new log is generated, each of the log numbers is incremented by 1.
    Procedure
    1. Run saplogvw.exe from the server, to start the SAPSetup Log Viewer.
    2. Enter the path and filename of the log file.
    3. Choose Finish.
    The log file is displayed. Errors are colored red. Warnings are colored blue.
    Also run this in command line
    sapsetup.exe /check
    Regards.
    Edited by: Sergo Beradze on Apr 2, 2008 9:44 PM

  • Business Explorer crashing excel

    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

    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.

Maybe you are looking for