cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Failed to commit objects to server : Undefined Info Store

miroslav_123
Explorer
0 Likes
7,835

After upgrade of BO from 4.3 sp2 to 4.3 sp4, I got error "Failed to commit objects to server : Undefined Info Store" when I try to create new user or when I try to update current one. Would you please give me any tips to to solve the problem.

View Entire Topic
ayman_salem
Active Contributor
0 Likes

To anyone having this issue:
Make sure your CMS DB supports the AL32UTF8 character set.
Since SP04, the SAP BI development team has added/made some changes to CMS query parameters (the parameter strings are sent in UTF-8 to use the “cached execution plan”), which affects correct writing and reading to/from the Aliases table and others.

To check your CMS DB, run the following SQL command on your database and see the result
(example: Oracle DB)

ayman_salem_0-1727794493862.png

If you get different results, you are having problems adding/modifying groups and users.

Unless SAP changes this in the next patches, there is unfortunately NO workaround to solve this problem. You should migrate your CMS database to a database that has the ALU32UTF8 character set.

 

YvanB
Discoverer
0 Likes

Hi ! Thank you very much for this info.

Can you tell me: once a new schema in UTF-8 is available, what is the best option to create the repository on it ?
You mention a migration, but this is a fresh install and I don't want to burden the new CMS repository with any compatibility issue.

ayman_salem
Active Contributor
0 Likes

@YvanBIf this is a new installation and the database uses AL32UTF8 as the supported character set, then everything should be fine—no action is required.

To create new or migrate an existing repository, use the CMS Database Setup located in the Central Configuration Manager.

ayman_salem_0-1751627287836.png

 





YvanB
Discoverer
0 Likes

Thanks again for your answer.

I meant that I have this issue, but requested a new UTF-8 schema to replace the current one.
Don't you think that migrating the CMS repository could bring new issues ?
I thought about initializing a new CMS repository, but I don't see how it is done.

And do you know if this issue also concerns the Audit repository ?