If you are unable to create a new account, please email support@bspsoftware.com

 

Error 'sqlPrepareWithOptions' status='-120' opening Analysis Studio report

Started by RubenvdLinden, 27 Jan 2010 08:50:05 AM

Previous topic - Next topic

RubenvdLinden

Today, I trained one of my users to work with Analysis Studio. We created some simple reports on a DMR and he saved them to the Personal Folders. Now when we try to open one of these saved reports, Analysis Studio immediately prompts "An error occurred while performing operation 'sqlPrepareWithOptions' status='-120'"

I have never seen this error before. Any help would be appreciated.

MFGF

Hi,

Is there anything else indicated in the error message or is it just ''sqlPrepareWithOptions' status='-120' ?

MF.
Meep!

RubenvdLinden

Thanks for your response.

It's just the -120 error. I also tried to open the analysis in Report Studio, but it throws the same error. It doesn't even load the package.

MFGF

Hi,

That's very odd.  Usually, after the message you posted, you expect to see further info - UDA-SQL-0107 A general exception has occurred during the operation "prepare" - then a message from the database or query engine detailing what it was not happy about in the SQL query.

Can you copy the entire message and post it up?

Thanks,

Mark.
Meep!

RubenvdLinden

I think I found what you were looking for:

Failure   RQP-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions' status='-120'.UDA-SQL-0458 PREPARE failed because the query requires local processing of the data. The option to allow local processing has not been enabled.UDA-SQL-0535 CAST operation on given datatypes is not supported by the database. This operation requires local processing of the data.


Unfortunately, it doesn't tell which data item is causing the problem and as said the report doesn't open anymore in Analysis Studio, nor in Report Studio.

MFGF

Hi,

Right - thanks for this.  It sounds suspiciously like a modeller has changed the FM package and republished since the report was written.  To fix the issue, they need to go to the properties of the data source in Framework Manager and change the Query Processing property from Database Only to Limited Local.

Regards,

MF.
Meep!

RubenvdLinden