Skip to Main Content
Forums

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Unable to connect to essbase DB via smartview

VinnFeb 16 2017 — edited Apr 13 2017

Hi Experts,

When we are trying to connect to the Essbase ASO application. We are getting following.

Error: "Invalid Spreadsheet data.An Application protocol error might exists between server and client processes"

My Smartview Version: 11.1.2.3.000

Essbase : ESB11.1.2.3.504B004

Would request someone to please guide me in resolving this issue.
This post has been answered by Chad_Alexander on Apr 12 2017
Jump to Answer

Comments

JohnGoodwin

You are using an old version of Smart View, I would suggest testing with the latest version to rule out a bug.

Is this only happening for one application, is it ok using the Sample ASO application, also check the essbase app log for errors

Cheers

John

1 person found this helpful
Nauzer A

Check if this is related to the following Bug.It is fixed in 11.1.2.1.103 . if you are using the older version of SV , try with the latest version and check.

12918727 :If you are connected to a non-unique Essbase outline from a multiple-grid worksheet, you may get this error: "Invalid spread sheet data. An application protocol error might exist between server and client processes."

Regards

Nauzer A

1 person found this helpful
krikumar-Oracle

I agree with John and Nauzer.

Same issue for my customer was resolved after they started using the latest of SV.

Vinn


Hi John ,

I am able to connect to the application fine with different reports, only while trying to refresh the data for single report we are getting this issue i.e., also for few users but not for all users

JohnGoodwin

As suggested I think it is worth testing with the latest version of Smart View.

Vinn

Hi John,

I have tested with latest version 11.1.2.5.620 against office 2007 Sp3. Its still popping up the same error.

JohnGoodwin

If you can open other ASO applications then there is something related to that application, probably best raising an SR then

Cord234

Are you trying to connect to this cube with a blank sheet, or is there a POV already built on the sheet you are trying to connect with?  I've seen this error before where a user actually had some old data/pulls hidden on the spreadsheet and also had another grid connected to an old server that was turned off months ago.  Not sure which of the two was the root cause, but after removing the intersections and deleting the extra grid, the sheet was able to connect.

1 person found this helpful
JohnGoodwin

I really hope the OP has tested with a new workbook and this is not related to some dodgy excel file.

Cord234

I hope so too, but you never know.  His post:

1060285 wrote:
I am able to connect to the application fine with different reports, only while trying to refresh the data for single report we are getting this issue i.e., also for few users but not for all users

makes it sound like he's trying with a specific report that probably doesn't like some intersection.  The fact that he's saying it happens for a few users and not all would make me think that it's a combination of security and metadata issues, and not an issue with the application itself.

JohnGoodwin

I totally agree, what annoys me is that none of that information is in the original post.

Maybe I am missing something but if they know it is a certain excel spreadsheet then just recreate it, end of story, no time wasted.

Chad_Alexander
Answer

Have you been able to resolve this issue?

I just had a user come to me today with this same issue.  Our application is fine, the database is fine, but a specific Smart View connected file was producing the error.  I was able to pinpoint a specific member alias/description that had changed and the user had not updated the report to reflect the change.  Once I updated the report for the correct member alias/description, the report refreshed correctly.

Cord234 could be right, that it could be a combination of security and metadata, but it's also possible that certain users have the updated metadata in their report, while other users do not, but I suspect Cord234 is also correct in his statement, "makes it sound like he's trying with a specific report that probably doesn't like some intersection."

If you have not been able to resolve this issue (or for others that may encounter this issue) you should check that all metadata within the report is still valid.  I did this by copy/pasting (as values) all metadata into a new tab and connecting to Smart View.  The line with the bad metadata did not retrieve any data and the valid metadata members disappeared from the line with the invalid metadata, which helped to identify which line in the report had the invalid metadata.

It's possible this may not fully resolve your issue, but this is what worked for me.

Best,

Chad

Marked as Answer by Vinn · Sep 27 2020
1 person found this helpful
Vinn

Hi Chad,

As you said,its right. Issue was resolved

Thanks for response

1 - 13
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 11 2017
Added on Feb 16 2017
#business-intelligence-applications, #epm-system-infrastructure, #performance-management-applications
13 comments
4,236 views