Catalog Service Error

[matthias_prller]

Hello everybody,

On our development system a user with normal privilegs get a Fatal Error "Invalid Assignment Target: [SQL_Query.Param.1]" but a user with development rights doesn't get this error.

I set the rights similar to the productive system where the error doesn't occure.

In the NetWeaver-Logs I see a "Catalog Service Error" right before a lot of "Invalid Assignment Errors". But I don't know which privilege is missing.

Can somebody help me, please?

Note:

Produktive System: MII 12.0 SP7

Development System: MII 12.0 SP8

Thank you.

Regards

Matthias

[matthias_prller]

Hi,

it's a bit embarrassing: After checking the roles a third time a saw that I forgot the "FileSystemReader"-service for the new role.

After I assigned this service to the role it works. But it's a little bit confusing that I need a File System to assign a vallue to a parameter.

But finally it works and that all I need

Jeremy, thank you for your help.

Regards

Matthias

[Former Member]

Hi Matthias,

I had the same issue after the new role was created. Thanks to this thread i was able to resolve the same.

Regards

Suraj

[matthias_prller]

Hello Suraj,

Thank you for your feedback. I'm happy to hear that.

Regards

Matthias

[David]

test post

[Former Member]

Matthias,

it seems that the Catalog Service Error is the reason for the Invalid Assigment Target, because some XML node is not availble where it should be.

Did you call a Transaction or a Query before the assignment where some roles are set in the "Transaction - Security" or "Query - Security" section which a normal user does not have, so the Catalog Error may be raised?

I guess usually the common XMII Users role (which every user should be assigned to) is contained in the Reader Role section.

Michael

[jcgood25]

It does sound like the Query Template has some restrictions on the ReaderRoles settings and the runtime user does not belong to a necessary roles. Before BLS will do the assigment for Param.1 it needs to load the Query Template from the catalog and it looks like this failed because they were unauthorized.

[matthias_prller]

Hello Jeremy and Michael,

the user is not in the XMII User Role but he is in a role which has the same privilegs as the XMII User-Role.

The user is a member of the Reader Role in the Query.

If I delete the assignment of the parameter in the BLS to the Query the transaktion is executed without any errors but uses (of course) the default parameter from the query.

I think this is a strange behaviour, isn't it?

And I created a complete new transaction, SQL-Query and Xacute-Query set the right roles and have the same Catalog Error again.

The query is very simple: select sysdate from dual

If I set the Parameter 1 to "anything" in the BLS I get the error otherwise the BLS is executed well.

I also checked the Roles in the System Security/Services again. There are no differences between the standard XMII Users Role and my custom Role.

Regards

Matthias

[Former Member]

Matthias,

just to make sure: the new role is also set in the Data Access screen, in the "Roles assigned to Server"?

Michael

[matthias_prller]

Micheal,

yes it is. If it isn't set I would get an error even if I don't set the parameter to the query in the BLS.

Regards

Matthias

[jcgood25]

Have you tried linking to something that is not indexed like Param.1 ? Try the same TRX and link to RowCount or something like FilterExpr or the Query property itself (especially if the test query is very simple).

What is the full error syntax you get in the logs?

[matthias_prller]

Hello Jeremy,

I tried it, but same result.

this is the first error in the results:

"Error","2009-10-08","15:34:33:333","Catalog Service Error","/Applications/XMII/Xacute","com.sap.xmii.servlet.Catalog","sap.com/xapps_xmiiear","frds00544","Server 0 2_38032",

2nd:

"Error","2009-10-08","15:34:33:333","[505aca50-b40f-11de-b3c3-fe7a0ab8ca3c][ERROR]: TRANSACTION EXECUTION TERMINATED f6_test/test_berechtigung","/Applications/XMII/Xacute/Runner","com.sap.xmii.xacute.engine.RunnerLog","sap.com/xapps_xmiiear","frds00544","Server 0 2_38032",

3rd:

"Error","2009-10-08","15:34:33:333","[505aca50-b40f-11de-b3c3-fe7a0ab8ca3c][ERROR]: STEP EXCEPTION (Sequence) : Invalid Assignment Target: [test_berechtigung_sql_0.RowCount] f6_test/test_berechtigung","/Applications/XMII/Xacute/Runner","com.sap.xmii.xacute.engine.RunnerLog","sap.com/xapps_xmiiear","frds00544","Server 0 2_38032",

(and 5 more with Invalid Assignment Target)

Regards

Matthias

[jcgood25]

Assuming "f6_test/test_berechtigung" is a valid query template (of type SQL) then is the spelling the proper upper/lower case?

Are you assigning only query properties or are you assigning the query template too?

[jcgood25]

With a properly working TRX with SQL query and link to Param.1, if the QT in the config dialog is invalidated the following is what shows up in the execution logger:

[ERROR]: STEP EXCEPTION () : Invalid Assignment Target: [EmployeeQuery_0.Param.1]
[ERROR]: STEP EXCEPTION (EmployeeQuery_0) : Invalid Assignment Target: [EmployeeQuery_0.Param.1]
[ERROR]: STEP EXCEPTION (Sequence) : Invalid Assignment Target: [EmployeeQuery_0.Param.1]
[ERROR]: TRANSACTION EXECUTION TERMINATED

Perhaps an invalid query template is the source of your problem?

[matthias_prller]

I only assign the property value and don't assign the query template.

f6_test/test_berechtigung is the BLS.

But if the query template is invalid why does it work with developer privilegs but not with user privilegs? And why isn't there an error if I don't assign a parameter?

At the moment I do not know really what else I could check.

I also could reproduce the error with a complete new BLS + SQL-Query + xacute query.

And I'm sure it isn't a spelling error because I insert the SQL-Query with drag & drop.

It has something to do with privilegs and roles but I can't give the user the development rights.

[matthias_prller]

just in case it is somehow helpful. Here is the complete log-file:

Severity,Datum,Zeit,Meldung,Kategorie,Ort,Anwendung,Host,Knoten,
"Error","2009-10-08","15:34:33:333","Catalog Service Error","/Applications/XMII/Xacute","com.sap.xmii.servlet.Catalog","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",
"Error","2009-10-08","15:34:33:333","Execution Exception: Invalid Assignment Target: [test_berechtigung_sql_0.RowCount]","/Applications/XMII","com.sap.xmii.xacute.engine.TransactionEngine","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",
"Error","2009-10-08","15:34:33:333","[505aca50-b40f-11de-b3c3-fe7a0ab8ca3c][ERROR]: STEP EXCEPTION () : Invalid Assignment Target: [test_berechtigung_sql_0.RowCount] f6_test/test_berechtigung","/Applications/XMII/Xacute/Runner","com.sap.xmii.xacute.engine.RunnerLog","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",
"Error","2009-10-08","15:34:33:333","Execution Exception: Invalid Assignment Target: [test_berechtigung_sql_0.RowCount]","/Applications/XMII","com.sap.xmii.xacute.engine.TransactionEngine","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",
"Error","2009-10-08","15:34:33:333","[505aca50-b40f-11de-b3c3-fe7a0ab8ca3c][ERROR]: STEP EXCEPTION (test_berechtigung_sql_0) : Invalid Assignment Target: [test_berechtigung_sql_0.RowCount] f6_test/test_berechtigung","/Applications/XMII/Xacute/Runner","com.sap.xmii.xacute.engine.RunnerLog","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",
"Error","2009-10-08","15:34:33:333","Execution Exception: Invalid Assignment Target: [test_berechtigung_sql_0.RowCount]","/Applications/XMII","com.sap.xmii.xacute.engine.TransactionEngine","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",
"Error","2009-10-08","15:34:33:333","[505aca50-b40f-11de-b3c3-fe7a0ab8ca3c][ERROR]: STEP EXCEPTION (Sequence) : Invalid Assignment Target: [test_berechtigung_sql_0.RowCount] f6_test/test_berechtigung","/Applications/XMII/Xacute/Runner","com.sap.xmii.xacute.engine.RunnerLog","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",
"Error","2009-10-08","15:34:33:333","[505aca50-b40f-11de-b3c3-fe7a0ab8ca3c][ERROR]: TRANSACTION EXECUTION TERMINATED f6_test/test_berechtigung","/Applications/XMII/Xacute/Runner","com.sap.xmii.xacute.engine.RunnerLog","sap.com/xapps~xmii~ear","frds00544","Server 0 2_38032",

[jcgood25]

Try using Defaults/SQLQuery as your query template. It is possible that the baseline security needs are not satisfied by a 'null' query template, and it may not be proceeding for a non 'developer' type user.

[matthias_prller]

Hello Jeremy,

I don't really understand what you mean by "default query" and "null"-query.

I think I use standard queries already. I describe what I did:

1. I created a sql-query with an (oracle) data-server. Named it e.g. test_berechtigung_sql and in the sql-query I wrote the sql-statement (select sysdate from dual)

2. I created a transaction where I put in this sql-query. This transaction is called test_berechtigung

a) if I pass any parameter to the query the "Catalog Service Error" occures

b) if I don't pass any parameters to the query everything works fine

3. I created a Xacute-Query to the transaction (to run the transaction from the browser with a none development user

There are no special tricks, just the normal way as I learned it in the SAP MII training.

And it works on our productive environment. (Perhaps because we didn't install the SP8 on the productive environement?)

I think I will open an OSS message or do you think I made a fatal mistake?

Regards

Matthias

[jcgood25]

Sorry, I misinterpreted your comment "...and don't assign the query template." to mean you had no query template in the configure dialog. That is why I recommended using 'Defaults/SQLQuery' instead of nothing (or null).

I don't have immediate access to a 12.0.7 system (they are 12.0.8 or a newer working build) so I think your idea about logging a ticket with the corresponding details and symptoms is a good path forward. Implementing a temporary solution like adding the needed role to the user (even if it is less than desirable), will provide you with a short term fix until the situation is identified and/or resolved.

Regards,

Jeremy