We are facing problems in executing query rule in Appian 6.6.1 environment which

aniketb over 13 years ago

We are facing problems in executing query rule in Appian 6.6.1 environment which is Linux based environment. The error log is as below:-

Caused by: com.appiancorp.suiteapi.common.exceptions.ExpressionException: The passed parameter(s) are incorrect, or the function 'queryruleexec' may be unavailable.
at com.appiancorp.suiteapi.expression.AbstractExpressionEvaluationServiceImpl.evaluate(AbstractExpressionEvaluationServiceImpl.java:101)
at sun.reflect.GeneratedMethodAccessor3104.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.appiancorp.services.ServiceManager$ServiceInvocationHandler.invoke(ServiceManager.java:475)
at $Proxy261.evaluate(Unknown Source)
at com.appiancorp.process.expression.Express...

Discussion posts and replies are publicly visible

0 aniketb over 13 years ago

...ionEvaluator.evaluate(ExpressionEvaluator.java:363)
at com.appiancorp.process.expression.ExpressionEvaluator.evaluateFunction(ExpressionEvaluator.java:180)
... 94 more
Caused by: java.lang.NoSuchMethodException: com.appiancorp.process.expression.ExpressionEvaluationServiceImpl.queryruleexec(com.appiancorp.suiteapi.process.TypedVariable, com.appiancorp.suiteapi.process.TypedVariable, com.appiancorp.suiteapi.process.TypedVariable, com.appiancorp.suiteapi.process.TypedVariable, com.appiancorp.suiteapi.process.TypedVariable, com.appiancorp.suiteapi.process.TypedVariable, com.appiancorp.suiteapi.process.TypedVariable, com.appiancorp.services.ServiceContext)
at java.lang.Class.getMethod(Class.java:1605)
at com.appiancorp.suiteapi.expression.AbstractExpressionEvaluationServiceImpl.evaluate(AbstractExpressionEvaluationServiceImpl.java:95)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 13 years ago

Hi Aniket - have you confirmed primary and secondary datasources as per documentation? Can you also confirm your data store is validated and published and you are able to access the data store from the server you are running these commands?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 tilottamai over 13 years ago

Hi Sathya,
Datasources created as per documentation. Also, I can see CDT specific table created automatically in database after publishing data source.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 13 years ago

Hi, This is what I would suggest. Create a new expression rule and invoke the query rule that you are calling above with the correct parameters passed and check if you are able to retrieve the value. If you are able to do so, check the parameters you are passing to the QR that's throwing this error. Also make sure that you have set the permission for the DS for the role that's executing this if its not run as Admin.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 tilottamai over 13 years ago

We already tried these options

Query Rule with/without parameters
Wrapper expression rule on query rule

Error is not for any specific query rule. For all query rules execution, getting same error.

“The passed parameter(s) are incorrect, or the function 'queryruleexec' may be unavailable”

Running the processes as an Administrator user. And
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 tilottamai over 13 years ago

'Administrator' privileges set for all users for the data store.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bend over 13 years ago

I ran into a similar issue and this article fixed the issue for me. Hope it helps. forum.appian.com/.../4984
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 tilottamai over 13 years ago

We have finally got the problem resolved by adding below line in custom.properties

conf.suite.SCHEME=http
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 13 years ago

Thanks for sharing the solution. This attribute is enabled and set to http by default. Was it modified or changed that caused this issue in the first place?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 tilottamai over 13 years ago

As per detail metnioned in forum.appian.com/.../Required_Configuration,

conf.suite.SCHEME setup was mandatory step.

By default it's commented in custom.property.example
And we need to uncomment explicitly in custom.property. And it was not done in our environment.

Anyway, thanks for your input.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel