1 2 Previous Next 15 Replies Latest reply on Jan 24, 2020 2:56 PM by 3333775

    Power BI desktop connection to Essbase failed

    1008730

      On the Power BI desktop connection, select Essbae (beta) and got "Unable to connect to the remote server" error. User has been granted access to the server.

       

      This is the link we use

      http://Essbaseserver:19000/aps/XMLA

       

      Any help will be appreciated!

       

      Error message screen shot attached.

       

      Detailed error message shown as below:

       

      Feedback Type:

      Frown (Error)

       

      Timestamp:

      2019-03-09T19:32:04.0994009Z

       

      Local Time:

      2019-03-09T11:32:04.0994009-08:00

       

      Session ID:

      45d7c37a-915c-4ff6-ad96-92bda4fd7c26

       

      Release:

      February 2019

       

      Product Version:

      1. 2.66.5376.2521 (19.02) (x64)

       

      Error Message:

      Unable to connect to the remote server

       

      Stack Trace:

      1. Microsoft.Mashup.Evaluator.Interface.ErrorException: Unable to connect to the remote server ---> Microsoft.Mashup.Engine1.Library.Web.ResponseException: Unable to connect to the remote server ---> Microsoft.Mashup.Engine1.Library.Web.ResponseException: Unable to connect to the remote server ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.50.0.118:19000

         at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

         at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

         --- End of inner exception stack trace ---

         at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

         at System.Net.HttpWebRequest.GetRequestStream()

         at Microsoft.Mashup.Engine1.Library.Web.Request.GetWebResponse(WebRequest webRequest)

         at Microsoft.Mashup.Engine1.Library.Web.Request.CreateResponse(ResourceCredentialCollection credentials)

         at Microsoft.Mashup.Engine1.Library.Web.Request.GetResponseCore(ResourceCredentialCollection credentials)

         at Microsoft.Mashup.Engine1.Library.Common.RetryPolicy.Execute[TResult](IEngineHost host, Func`1 func)

         at Microsoft.Mashup.Engine1.Library.Web.Request.GetResponse(ResourceCredentialCollection credentials, RetryPolicy retryPolicy, AuthorizationThrowFunction authorizationFunction, Boolean tokenRefreshed)

         --- End of inner exception stack trace ---

         at Microsoft.Mashup.Engine1.Library.Web.Request.GetResponse(ResourceCredentialCollection credentials, RetryPolicy retryPolicy, AuthorizationThrowFunction authorizationFunction, Boolean tokenRefreshed)

         at Microsoft.Mashup.Engine1.Library.Essbase.EssbaseService.ExecuteRequest(String method, String request, String sourceInfo, String catalog, String cube)

         at Microsoft.Mashup.Engine1.Library.Essbase.EssbaseModule.EssbaseServersTableValue.<GetEnumerator>d__6.MoveNext()

         at Microsoft.Mashup.Engine1.Runtime.SkipTakeEnumerator`1.MoveNext()

         at Microsoft.Mashup.Evaluator.SimpleDocumentEvaluator.ValuePreviewValueSource.TableValuePreviewValueSource.SerializeRows(Int32 count)

         at Microsoft.Mashup.Evaluator.SimpleDocumentEvaluator.ValuePreviewValueSource.TableValuePreviewValueSource.get_SmallValue()

         at Microsoft.Mashup.Evaluator.Interface.TracingPreviewValueSource.get_SmallValue()

         at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.<>c__DisplayClass0_0.<RunStub>b__0()

         at Microsoft.Mashup.Evaluator.EvaluationHost.ReportExceptions(IHostTrace trace, IEngineHost engineHost, IMessageChannel channel, Action action)

         --- End of inner exception stack trace ---

         at Microsoft.Mashup.Evaluator.EvaluationHost.<>c__DisplayClass11_0.<TryReportException>b__1()

         at Microsoft.Mashup.Common.SafeExceptions.IgnoreSafeExceptions(IEngineHost host, IHostTrace trace, Action action)

         at Microsoft.Mashup.Evaluator.EvaluationHost.TryReportException(IHostTrace trace, IEngineHost engineHost, IMessageChannel channel, Exception exception)

         at Microsoft.Mashup.Evaluator.EvaluationHost.ReportExceptions(IHostTrace trace, IEngineHost engineHost, IMessageChannel channel, Action action)

         at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.RunStub(IEngineHost engineHost, IMessageChannel channel, Func`1 getPreviewValueSource)

         at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.Service.<>c__DisplayClass11_1`1.<OnBeginGetResult>b__0()

         at Microsoft.Mashup.Evaluator.EvaluationHost.ReportExceptions(IHostTrace trace, IEngineHost engineHost, IMessageChannel channel, Action action)

         at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.Service.OnBeginGetResult[T](IMessageChannel channel, BeginGetResultMessage message, Action`1 action)

         at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.Service.OnBeginGetPreviewValueSource(IMessageChannel channel, BeginGetPreviewValueSourceMessage message)

         at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.ChannelMessenger.OnMessageWithUnknownChannel(IMessageChannel baseChannel, MessageWithUnknownChannel messageWithUnknownChannel)

         at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.EvaluationHost.Run()

         at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass9_0.<CreateAction>b__0(Object o)

         at Microsoft.Mashup.Container.EvaluationContainerMain.SafeRun(String[] args)

         at Microsoft.Mashup.Container.EvaluationContainerMain.Main(String[] args)

         --- End of inner exception stack trace ---

         at Microsoft.Mashup.Evaluator.EvaluationHost.OnException(IEngineHost engineHost, IMessageChannel channel, ExceptionMessage message)

         at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)

         at Microsoft.Mashup.Evaluator.Interface.IMessageChannelExtensions.WaitFor[T](IMessageChannel channel)

         at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.WaitFor(Func`1 condition, Boolean disposing)

         at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.get_SmallValue()

         at Microsoft.Mashup.Evaluator.Interface.TracingPreviewValueSource.get_SmallValue()

         at Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo.SetPreviewValue(EvaluationResult2`1 result, Func`1 getStaleSince, Func`1 getSampled)

       

      Invocation Stack Trace:

         at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()

         at Microsoft.Mashup.Client.UI.Shared.DataImporter.HandleImportEvaluationException(ExceptionResult exceptionView, Query query, String sourceID, String formulaTitle, Boolean isNewQuery, Boolean isFromEditor)

         at Microsoft.Mashup.Client.UI.Shared.DataImporter.OnGetPreviewResult(PreviewResult preview, Query query, String sourceID, String formulaTitle, Nullable`1 explicitImportDestination, Boolean isNewQuery, Boolean isFromEditor)

         at Microsoft.Mashup.Client.UI.Shared.DataImporter.GetPreviewResult(Query query, String sourceID, String formulaTitle, Boolean isNewQuery, Boolean isFromEditor, Nullable`1 explicitImportDestination)

         at Microsoft.Mashup.Client.UI.Shared.DataImporter.<>c__DisplayClass75_1.<OnQuerySettingsResolved>b__0()

         at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

         at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

         at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

         at System.Delegate.DynamicInvokeImpl(Object[] args)

         at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)

         at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)

         at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

         at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

         at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

         at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)

         at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

         at System.Windows.Forms.Control.WndProc(Message& m)

         at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

         at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

         at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

         at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

         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 Microsoft.Mashup.Client.UI.Shared.WebDialogs.WebDialog.<>n__0(IWindowHandle owner)

         at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)

         at Microsoft.PowerBI.Client.Program.<>c__DisplayClass4_0.<Main>b__1()

         at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()

         at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

         at Microsoft.PowerBI.Client.Program.Main(String[] args)

       

       

      OS Version:

      Microsoft Windows NT 10.0.16299.0 (x64 en-US)

       

      CLR Version:

      1. 4.7 or later [Release Number = 461308]

       

      Peak Virtual Memory:

      1. 33.9 GB

       

      Private Memory:

      273 MB

       

      Peak Working Set:

      440 MB

       

      IE Version:

      1. 11.967.16299.0

       

      User ID:

      5ad5707c-0a54-4963-90d2-498fc9f889f6

       

      Workbook Package Info:

      1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

       

      Telemetry Enabled:

      True

       

      Model Default Mode:

      Empty

       

      Snapshot Trace Logs:

      C:\Users\Petia.Belitchenov\Microsoft\Power BI Desktop Store App\FrownSnapShot437919457.zip

       

      Performance Trace Logs:

      C:\Users\Petia.Belitchenov\Microsoft\Power BI Desktop Store App\PerformanceTraces.zip

       

      Disabled Preview Features:

      PBI_shapeMapVisualEnabled

      MIntellisense

      PBI_SpanishLinguisticsEnabled

      PBI_PdfImport

      PBI_ColumnProfiling

      PBI_variationUIChange

      PBI_PythonSupportEnabled

      PBI_showIncrementalRefreshPolicy

      PBI_showManageAggregations

      PBI_FuzzyMatching

      PBI_EnableWebDiagramView

      PBI_improvedFilterExperience

      PBI_qnaLiveConnect

      PBI_keyDrivers

       

      Disabled DirectQuery Options:

      TreatHanaAsRelationalSource

       

      Cloud:

      GlobalCloud

       

      DPI Scale:

      150%

       

      Supported Services:

      Power BI

       

      Formulas:

       

       

      section Section1;

       

      shared Query1 = let

          Source = Essbase.Cubes("http://etcfrea42:19000/aps/XMLA")

      in

          Source;

        • 1. Re: Power BI desktop connection to Essbase failed
          Chad_Alexander

          Are you working in a distributed Hyperion environment?

           

          I was testing this in our environment and was running into similar problems with connecting to PowerBI, however, when I tried testing the connection in a "sandbox" environment, where all Hyperion applications/components are installed on a single server, I was able to connect to PowerBI using the same connection string you identified above, http://EssbaseServer:19000/aps/XMLA.  So from my testing so far, my conclusion is that the Essbase (Beta) PowerBI Connector does not yet work in a distributed Hyperion environment.  We have reached out to Microsoft for guidance/support but have not yet heard anything new.  I believe they are aware of this issue and (hopefully) working on addressing it, but you may want to reach out to Microsoft as well.

           

          Good luck - and please let us know if you make any progress on this topic.

          Chad

          • 3. Re: Power BI desktop connection to Essbase failed
            Vivek Chetiaparath

            You need to use the server were APS is installed not Essbase Server name for the URL. As its a web components most of the environment would have it in the Foundation server (Web App Tier) . Let me know if the connection works after using the correct APS servername in the URL.

             

            Thank you
            Vivek Chetiaparath

            • 4. Re: Power BI desktop connection to Essbase failed
              user12227476

              I am also getting the error "thee client timed out waiting to connect to essbase in power bi" while connecting essbase through Power BI.

               

              does any one solved this timed out issue in Power BI?

              • 5. Re: Power BI desktop connection to Essbase failed
                user12227476

                Does u fixed this issue?

                • 6. Re: Power BI desktop connection to Essbase failed
                  Robert Armstrong

                  As Chad responded, use the workspace server name not the Essbase server name in the URL.

                  • 7. Re: Power BI desktop connection to Essbase failed
                    tomu2010

                    Did anyone get this working in a distributed env.?

                     

                    I did use the correct APS URL (as mentioned in the previous comments) and URL goes in.

                     

                    But then there is no login screen prompt and instead it is thinking the server name mentioned in the URL is the Essbase server (It tries to connect to the port 1423 on that server)

                     

                    Here is error message I am getting.

                     

                    Cannot connect to Essbase Server at “(servername in URL)”. Network Error [10061]:Failed to connect to [(ServerNameINURL):1423]”

                     

                    Any help is appreciated

                    • 8. Re: Power BI desktop connection to Essbase failed
                      Robert Armstrong

                      Sorry for the delayed response, I don't check here very often and not getting notified of responses.

                       

                      My environment is a distributed environment;  we have 3 production Essbase severs running IBM AIX Unix and 4 Windows 2012 servers for all the web apps:

                        server01 is the Workspace/Foundation/Shared services and WebLogic server

                        server02 is the APS and EAS server

                        server03 is the Planning server

                        server04 is the Reporting and Analysis server (FR, IR, WA)

                        AIX1 - AIX3 are the essbase servers

                       

                       

                      our Data Source URL for connecting with power bi is

                        If SSL enabled https://server01:19443/aps/XMLA

                        If SSL IS NOT enabledhttp://server01:19000/aps/XMLA

                       

                      The sever name (server01 in my case) is the Foundation/Shared Services server name and the port number used to connect to Workspace or Shared Services.

                      We did not use the direct APS server URL, we connect to Smart View using the server01 in the URL

                       

                      edited to correct URL (add aps/XMLA)

                      • 9. Re: Power BI desktop connection to Essbase failed
                        Robert Armstrong

                        I am now getting timeout errors connecting.  Using the same URL as I did before, the "PB Navigator" opens with the URL, the APS Server and the 3 Essbase server names, but when expanding the APS server node, getting "The Client timed out waiting to connect to Essbase Agent.  Check your network ...".  Under each Essbase server node the message:  "User access error to the requested resource".

                         

                        In the apsserver.log i get:  (it appears the credentials are not being accepted, we have SSO using kerberos enabled).

                         

                        [2019-08-08T15:17:49.360-05:00] [AnalyticProviderServices0] [ERROR] [] [oracle.EPMOHPS] [tid: 292] [userId: <anonymous>] [ecid: 00ivZS8wWTGFw00Fzzw0w00000^8000YOQ,0:1] [APP: APS#11.1.2.0] EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials.[[

                        EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials.

                        at com.hyperion.css.facade.CSSAPIFacade.authenticateSecurityAgent(CSSAPIFacade.java:166)

                        at com.hyperion.dsf.server.framework.HyperionCss.authenticate(Unknown Source)

                        at com.hyperion.dsf.server.framework.HyperionCss.authenticateUser(Unknown Source)

                        at com.essbase.smartview.provider.SVSession.generateCSSToken(Unknown Source)

                        at com.essbase.smartview.provider.SVSession.<init>(Unknown Source)

                        at com.essbase.webservices.admin.XmlaSVSession.<init>(Unknown Source)

                        at com.essbase.webservices.admin.XmlaSVSession.getXmlaSVSession(Unknown Source)

                        at com.essbase.webservices.admin.XmlaLogin.connectToOlapService(Unknown Source)

                        at com.essbase.webservices.util.ProviderUtil.login(Unknown Source)

                        at com.essbase.webservices.EssbaseXmlForAnalysis.loginNlockSession(Unknown Source)

                        at com.essbase.webservices.EssbaseXmlForAnalysis.doPost(Unknown Source)

                        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

                        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

                        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)

                        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)

                        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)

                        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)

                        at java.security.AccessController.doPrivileged(Native Method)

                        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)

                        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)

                        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)

                        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)

                        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)

                        at java.security.AccessController.doPrivileged(Native Method)

                        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)

                        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)

                        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)

                        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)

                        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)

                        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)

                        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

                        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)

                        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)

                        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)

                        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)

                        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

                        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

                        ]]

                        [2019-08-08T15:17:49.382-05:00] [AnalyticProviderServices0] [ERROR] [] [oracle.EPMOHPS] [tid: 292] [userId: <anonymous>] [ecid: 00ivZS8wWTGFw00Fzzw0w00000^8000YOQ,0:1] [APP: APS#11.1.2.0] [SID: 76B045B5498CFB926593253FFAAD2F] User access error to the requested resource[[

                        com.essbase.api.base.EssException: User access error to the requested resource

                        at com.essbase.smartview.provider.EdsProviderImpl.listApplications(Unknown Source)

                        at com.essbase.webservices.util.ProviderUtil.listApplications(Unknown Source)

                        at com.essbase.webservices.xml.DbsCatalogsXml.printData(Unknown Source)

                        at com.essbase.webservices.xml.DbsCatalogsXml.generateXML(Unknown Source)

                        at com.essbase.webservices.discover.DbsCatalogsProcessor.process(Unknown Source)

                        at com.essbase.webservices.discover.XmlaProcessDiscover.discover(Unknown Source)

                        at com.essbase.webservices.EssbaseXmlForAnalysisHelper.doPost(Unknown Source)

                        at com.essbase.webservices.EssbaseXmlForAnalysis.doPost(Unknown Source)

                        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

                        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

                        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)

                        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)

                        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)

                        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)

                        at java.security.AccessController.doPrivileged(Native Method)

                        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)

                        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)

                        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)

                        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)

                        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)

                        at java.security.AccessController.doPrivileged(Native Method)

                        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)

                        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)

                        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)

                        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)

                        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)

                        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)

                        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)

                        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)

                        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

                        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)

                        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)

                        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)

                        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)

                        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

                        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

                        ]]

                        Something we also enabled since working with PBI was SSL/TLS 1.2 only being allowed.  Other than that and Essbase & APS patches to 11.1.2.4.029

                        • 10. Re: Power BI desktop connection to Essbase failed
                          tomu2010

                          Thanks Bob for taking time to check on this.

                           

                          Do you think the latest PBI desktop update caused it to fail? Just wondering why it stopped working for you

                          • 11. Re: Power BI desktop connection to Essbase failed
                            Robert Armstrong

                            My current guess is yes.

                             

                            Today I was trying to connect and use Fiddler to see if there was a TLS1.2 issue, it seemed to be getting proper SSL/TLS1.2 handshake but was still unable to connect and update.

                             

                            I think I tried too many times as my AD account got locked out, this leads me to believe the login credentials are saved in the data source settings and since my password has changed, it was no longer valid and the number of connect attempts in a row locked me out.

                             

                            Another thing I found was the application and database, Sample Basic, I was using to test was removed from the Essbase server.  So that could have been another issue I did not see before for this existing data source.

                             

                            So now, I have started over and setting up a new PBI report did the following:

                            1) Opened PowerBI Desktop and logged in with my PBI credentials

                            2) Get data

                            3) selected the Essbase connector

                            4) provided the APS / XMLA URL:  https://myserver.domain.com:19443/aps/XMLA

                            (myserver = the Foundation / WebLogic server name)

                            5) selected "Import" (this option was new since the last desktop version.  There are two connection options under the URL, Import and DirectQuery)

                            6) was presented the "Navigator" dialog with the list of APS and Essbase server names, but when I expand the Essbase servers, get the message "User access error to the requested resource"

                             

                            The 'apsserver.log' is showing the message: 

                            "EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials."

                            and "com.essbase.api.base.EssException: User access error to the requested resource"

                             

                            We have SSO enabled but I don't know what PBI is passing as user information.  I asked my admin if there was any configuration needed when the new connector was first available, maybe there is something needed now too since the update. 

                             

                            If i have any new information, will try to post as soon as possible.

                            • 12. Re: Power BI desktop connection to Essbase failed
                              Chad_Alexander

                              I am still getting errors with connecting to Essbase, so PBI is still not working for me, but Robert, you may be able to help clear up your authentication issues if from within Power BI, you go to File->Options & Settings->Data Source Settings, then select your server connection (the APS / XMLA URL:  https://myserver.domain.com:19443/aps/XMLA) then you can edit or clear the permissions for this data source.

                               

                              Did you have to do any special config to get PowerBI to work in your distributed environment?  I was working directly with Microsoft for a period of time and they weren't able to get it work for us yet either....

                               

                              Best,

                              Chad

                              • 13. Re: Power BI desktop connection to Essbase failed
                                4131198

                                For us turned out to be an Essbase config issue

                                 

                                The problem was: The default Essbase server entries in the provider config are wrong as they assume the provider and the Essbase services will both be running on the same host, that is not always the case.

                                 

                                The solution was: Delete the default entries, pointing to the web servers, and manually create an entry pointing to the actual Essbase host

                                • 14. Re: Power BI desktop connection to Essbase failed
                                  Timur

                                  Hello, in our company the servers are also separated, in database and application server. Which config did you changed to make it work?

                                  Thanks in advance and best regards

                                  Timur

                                  1 2 Previous Next