Business Explorer message.
Dear All,
When I am trying to open my BEx query designer. for creation of new queries. I getting a pop up message says.
The standard SAP transport system is active.
SAP GUI connection is not activated for current connection to BI system.
DO you want to reconnect to BI system and activate SAP GUI connection.
Yes No
Tabs are available.
Now we had a individual pacakges for different areas of reporting and would assign the transports if I want to make changes to that particular query in the pacakage for Bex transports.
with this message when I say yes it goes to Query designer and if I make changes to the existing query it should collect in my transport assigned but its asking a transport if I save the query.
Also If a new query is created it must collect in TMP but while i save the new query its asking for the transport.
I am afraid if any other changes for different queries would also collect in my transport.
Can any please advise how would I revert back to individual package system transport assignment.
Thanks again.
No , It will not have adverse effect:
There are just 2 different ways of handling object using Standard and
BW Transport System modes:
1. Standard CTS.
Assignment to a Package and Transport Request is done immediately when you create an object. This is as it is
for any object in the system, for example, a function or a program. System raises a pop-up for Package and
Corresponding Transport Request within this Package. This is fine for some objects, but not very useful
for BW queries which are complex R/3 objects consisting of many single query elements (R3TR ELEM). Any
additions to query definitions will raise the transport pop-up asking for Package/Request confirnation.
2. BW CTS.
Here you initially assign all newly created object to $TMP. This means all those objects are being handled as
temporary objects. Package $TMP requires no request at all and can not use any request. This is done
mainly to avoid confusion from the endusers. Transport of such objects is possible nevertheless from the
Transport Connection. Here you may select an object, collect all required related objects and assign a
corresponding Package and Transport Request. Releasing of this request will deliver the included objects
into the defined target system.
Automatically a Standard BEx Request is required in case when you have already transported objects.
For example, a query is transported from any other system has to be changed. If there is no special transport
request avaiable in this Package, the changes will be registered in the Standard BEx Request.
This is up to you to select this or that CTS mode. Please have a look at the SAP note 992965. It describes some
related errors, but also gives a theoretical overview.
Regards,
Arvind
Similar Messages
-
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
lasithaHi ,
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 ! -
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. -
SAP Business Explorer not working
Dear Moderators,
This is to have some advice regarding the problem in my system for Business Explorer.
I am not able to open SAP Business Explorer's Query Designer, Report Designer and Web Application Designer.
Error Descriptions:
1. SAP BEx Query Designer standalone
SAP BEx Query Designer standalone has encountered a problem and needs to close. We are sorry for the inconvenience.
2. SAP BEx Report Designer
SAP BEx Report Designer has encountered a problem and needs to close. We are sorry for the inconvenience.
3. SAP BEx Web Application Designer
SAP BEx Web Application Designer has encountered a problem and needs to close. We are sorry for the inconvenience.
Please inform SAP about this problem
Please describe in detailed steps how to reproduce this problem.
Attach following traces to your description, too.
4:55:36 PM.504: Info: Web Application Designer Start. Revision: 7100.1.600.466
-EXCEPTION-START- 4:55:36 PM.941: TRACE EXCEPTION startup ---
Exception Name: TypeInitializationException
Exception Message: The type initializer for 'BExUserSettings' threw an exception.
Exception at com.sap.bi.et.Communication.CommunicationFactory.LogOn(IntPtr iWHND, Boolean iWithGUI, Boolean iKeepStatInfo, Boolean& eBackEndError, BExDebugLevel iDebugLevel)
at com.sap.bi.et.wad.man.WADConnectionManager.AssureLoggedOn()
at com.sap.bi.et.wad.BexWebApplicationDesigner.Launch.Main()
Full Stack: at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
at com.sap.bi.et.wad.BexWebApplicationDesigner.Launch.Main()
-EXCEPTION-END----
-CALLING-FROM- 4:55:36 PM.941: TRACE EXCEPTION startup ---
at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
at com.sap.bi.et.wad.BexWebApplicationDesigner.Launch.Main()
Additional Information
WAD revision 7100.1.600.466
Internal Error ID: E-MAIN
Error Message: TypeInitializationException
The type initializer for 'BExUserSettings' threw an exception.
Please do suggest some solution to this issue.
Thank you.
Mitul ModiHi Mitul,
Please apply note 1179647 via tx: SNOTE and also apply the manual corrections from the note.
Thanks,
Michael -
Business Explorer - Internet Explorer
I present you following problem :
since the installation of the module Business Explorer for SAP Gui 7.10 we encounter problems with one of our manufacturers website application through Internet Explorer. It seems that Internet Explorer can't open the module (which is used to list a tree of several components) and so gives us an typical script error message on that specific page.
This problem has been reproduced on several computers and only occurs when the combination of Internet Explorer and Business Explorer is installed. The problem does not occur with other browsers like Firefox.
I wanted to download the latest patch available " bi710sp06p_602-10004472.exe BI AddOn Patch for GUI 7.10 602 Info 34960 21.08.2008" but can't seem to download it (error HTTP 400), even through the Download Manager.
Can anybody help us?
Thanks in advance.
Kind regards!Laurent, it appears our company is also having any issue with IE after upgrading our BI 7.0 Front End tools to PL5 or 500. In reading the notes regarding PL5 and PL6 (600,601,602) have not seen any mention of potential installation issues with PL5.
Our desktop group is researching what IE items might have changed with the BI 7.0 Front End Tools upgrade to PL5 and once I get some info from them, I will open an OSS message on this.
I am also trying to re-create on my laptop so I can see the issue myself.
More to come. -
Business Explorer Installation
Hi Everyone,
I've installed the SAPgui and Business Explorer for BI7 and BW 3.5 on my system. Everything except the BEx Analyzer for BI 7 is working fine. When I try to start the Analyzer, an excel window pops up, but the BEx toolbar with the 'Open, Save, Refresh' buttons does not appear. When I execute RRMX, I get a message 'Business Explorer is not installed. Please install Business Explorer'.
I removed and re-installed BEx but I'm still getting the same error.
This problem is only with the BEx for BI7 component. The 3.5 BEx is working fine. Also the other components like Query Designer, Report Designer are working fine.
Is this a problem with my installation or am I missing some settings to be done for BEx for BI7?
Thanks,
RamOké... than I know what you have to do:
read note 1121263 and implement the zip-file that is named there.
Actually, the bex analyzer is not properly installed because there is a key registration missing in your excel. (believe me: you are not alone... happened already with 3 of my customers...)
once you installed the zip-file, open your analyzer again and the ? is yellow and analyzer will work fine.
Don't forget to install support packages afterwards!
Ciao
Joke -
Canu00B4t run business explorer from APO
Hi,
I can´t run the business explorer from APO (transaction RRMX). I get the error message "Please install Excel as a viewer" (Msg no BRAIN 871). However opening BEx in excel and then opening queries work. Any suggestions how this could be solved? Have checked the add-ins in excel and they are all disabled.
Thanks for any help!
KalleKarl
Welcome to SDN
Please install MS Excel again in your laptop/PC. it seems the version you have right now is not compatable with Business Explorer.
Hope this helps
Thanks
Sat -
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,
Jonhi 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. -
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. -
SAP Business Explorer 7.0 availability
Hello Expert,
We've migrated BW 3.5 query in BW 7.3 SAP System. Dataflow migration was successful but Query Designer 7.3 product version not compatible with BW 3.5 Query. Have found from SAP SCN thread that firstly we need to install BEX tool 7.0 & Validate/run all queries in 7.0.After that all these works fine in BEX 7.3.
While checking BW 3.5 query in BI Business explorer query designer 7.10 getting the following error message.
Please check the attached file ABAP dump -ST22 for the more details.
Status Messages:
Terminate:Unexpected Error:RFC_Error_SYSTEM_FAILURE-Exception Condition "X_MEssage" raised.
Terminate: Query Designer must be restarted:further work not possible
We've tried to install SAPGui version 710,720,730 but unable to find the BI Business Explorer 7.0 version in these SAPGui version & getting the same error message from All these BEx versions(710,720,730)
Can anyone guide us in which SAPGui version we'll find the BI Business explorer query designer 7.0 version
Thanks
SanjeevHi Sanjeev
Can anyone guide us in which SAPGui version we'll find the BI Business explorer uery designer 7.0 version
Kindly refer the SAPGUI & BW Support notes
1932461 - SAP BW 3.5 BEx tools / BW 3.5 frontend add-ons are incompatible with BW7.4
1424366 - BW 7.x Frontend (GUI 720): General Information & Limitations
1425805 - Hardware&Software requirement for BW 7.x Frontend in GUI 720
1424366 BW 7.x Frontend (GUI 720): General Information & Limitations
1640140 - BI 7.x tools in 730 - General Information & Limitations
Kindly refer the SAPGUI version end of support
Regards
Sriram -
BI 7.0 Business explorer / analyzer Can't open queries
Hi, I recently upgrade our 3.0B sandbox to BI 7.0. When I run "start" -> "Programs" -> Business explorer -> analyzer Excel bex tool launches but when I click on the folder to open queries (Offnen open) Nothing comes up. However, if I am logged into the BI 7.0 system and lanuch RRMX excel comes up with the Business explorer tool bar. I re-read the upgrade guide and could not find out if I am supposed to run a conversion program or this is the default behavior.
Thanks in Advance
--- SteveHi PG. When I run transaction RRMX from within SAP gui while logged into BI 7.0, Excel launches and I get the Business Explorer tool bar. I have the options "open" "save" "refresh query" Back" "change query" "goto" "Olap Functions ..." "format" "layout" "tools" "settings" and "help" Under Settings I don't have "Launch Legacy Version from RRMX".
I clicked on help -> about and it showing me finall release 3.5. Shouldn't it read 7.0?
The installation of sap gui with BW add on was done with DVD 50083078 SAP NetWaver 2004s presentation SAP GUI for Windows 7.10 comp 1.
If I click on "Start" "All Programs" "Business Explorer" "Business Explorer (SAP BW 3.x) -> Analyzer (BW 3.x) it's also showing version release 3.5 but the Business explorer tool bar is there. If from the excel menu I click Business Explorer -> Installation check I get the message 12 red signed Files found , 14 yellow signed Files found, please check SAPSETUP.LOG in c:\windows. See note 197460 from more details. I can't find the sapsetup.log anywhere (supposed to be under c:\windows). Note 197460 refers to the check I just ran. The note also mentions Red files have to be manually registered, so it looks like I will either have to find a newer release or have a lot of work to do -
Infoobject - Setting for Business Explore and its performace
Hello BW-fans,
I am not sure, whether I am here at the right topic or this is a question for Bex-Topic. However it's something to do with data modelling so I firstly put the question here.
I have an example: the InfoObject 0CUST_HIE01 is from SAP-Standard referenced on 0CUSTOMER - it's ok. By selection at query execution, depending on the general settings for Business Explore, especial at "Query Execution Filter Val. Selectn", the content of 0CUST_HIE01 will be showed as the content of master data 0CUSTOMER or the content of 0CUST_HIE01 itself. In our data model it's two different values, so the general settings should be correctly "Only value in InfoProvider" or "only posted value for Navigation".
The problem is the perfomance when I select the filter value at query executation. With those two settings like above it'll take very long time, the voluminous data is updated in InfoProvider the slower the performance will be. In my example is showing the content of master data 0CUSTOMER due to setting "Value in master data table" is very quick but wrong and showing the "posted value in InfoProvider" is correct but it takes very long time.
My question is: Is there any method to upgrade the performance for this case?
Many thanks for answers!
Van Anh NguyenHi,
To avoid that goto the maintaince of that characterstic infoobject and in the Tab Page: Business Explorer set property Filter Selection in Query Execution property to Only Values in InfoProvider so that variable will not fetch all the data instead it will display only required data.
Its becoz "This field tells you how the selection of filter values is determined when a query is executed.
When queries are executed, the selection of filter values is usually determined by the data that is selected by the query. This means that only the values for which data has been selected in the current navigation status are displayed.
In many cases, however, it can be useful to include additional values. Therefore you can also choose the settings Only Values in InfoProvider and Values in Master Data Table. If you make this selection, however, you may get the message No data found when you select your filter values."
-Vikram -
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 -
"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 -
How to create a report in business explorer?
Hi All,
how to create a report in business explorer after creating the information spaces then how to operate the exploration view sets please if anyone knows can you explain me step by step...
Thanks...what exactly you want to do tell me
1.in business explorer
or you want to create a webi
or you want to see the data in business explorer
Maybe you are looking for
-
Why does iTunes make a mess out of my TV Shows library?
I'm not really sure where to post this, as it doesn't seem like Apple pays much attention to the official Apple Support Forums, but I'll give it a go nontheless. The thing is, as most Apple TV owners I have to rely on iTunes for handling my media lib
-
XBMC freezes with free Radeon driver and VDPAU (Mesa 3D 9.2)
Hello! I am currently setting up a HTPC with AMD A4-5300 with the integrated Radeon HD 7480D. To avoid the trouble with the fglrx driver, I would like to use the free xf86-video-ati driver. I thought this would be no problem since the update to Mesa
-
Locked my ipod and it says ipod is disabled connect to itunes - have tried everyting - can not rememb er password - can someone please type good instructions for me to get back in - thank
-
TS3694 I have 1015 problem o n my iphone I cant restore it now .can any body help me
I was uptading mu Iphone 3g,after downloading the software Itone start it to iphone and then at the end time it shows 1015 error ,now icant restore my iphone.
-
Database not getting connected from sql developer(Vendor code 20)
Am getting the following error while connecting db from sql dev "network adapter could not establish connection vendor code 20" FYI - database is up and running fine in sqlplus, and am not able to find the service in lnsrctl. As am using OIM db as se