Skip to Content
Author's profile photo Mario Panzenboeck

After BIP Upgrade to 4.2 SP5 – SAP User authentication error: CHANGE_NOT_ALLOWED

This blog entry will help you if you are facing the error message “CHANGE_NOT_ALLOWED” while trying to logon to your Business Objects System using SAP authentication.



I upgraded a customer system to BIP 4.2 SP5 and after upgrade the login with SAP user wasn´t possible anymore. The following error message was displayed:


I checked the SAP authentication within CMC which was working fine. The RFC User was not locked and also able to import new BW roles to the Business Objects System.

So what is wrong?



With BIP 4.2 SP5 you are now able to directly change an expired password while logging on to the BI Launchpad for example. That means that SAP changed the way how user authentication works between BIP and BW backend system.


Please refer to the following blog:

SAP BW Change password

We have an option to change BW password in CMC and BI Launch Pad, if the BW password is expired and requires change at next logon.

Consider BusinessObjects system is setup with SAP Authentication and SAP BW password for a given user is expired, in such a case user will have option to change password during next login from CMC and BI Launchpad.

Prior to BI 4.2 SP5, if the user tries to login it would get error message if the password is expired and they need to change BW password from somewhere else say from SAP GUI and then perform login on CMC or BI LAUNCHPAD with the updated password. With BI 4.2 SP5

User will get below option to change BW password, when the password is expired and user tries to login in BI Launchpad or CMC.



In our case the system RFC user had an initial password but was not allowed to change the password. After changing the password from initial to productive in the bw backend system the logon with SAP authentication was working again!


Check the “Password Status” with transaction “su01” in the backend system:



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Nice to be visiting your blog again, it has been months for me. Well, this article that I’ve been waited for so long. I need this article to complete my assignment in the college, and it has the same topic as your article.  spotify craccato

      Author's profile photo Former Member
      Former Member

      Same problem after the upgrade but it doesn't work, still the error we need special set up in SAP BW?

      Author's profile photo Mario Panzenboeck
      Mario Panzenboeck
      Blog Post Author

      Hi, did you check the password status for your background user in BW? It shouldn´t be initial.


      Author's profile photo Gregor Horvath
      Gregor Horvath

      Thank you very much for this thread.

      We’re upgrading to BO4.2 Sp5 and we’re using BW4Hana as BW System.

      Funny thing was, that roles from BW4 got updated. But no users. While checking in SM04 in BW4 we had the following entries:

      “R=3 T=S S=****-****-***** I=cms F=SUSR_USER_CHANGE_PASSWORD_RFC C= U=”

      User check showed, that the technical user still had the initial password. So we changed the user to dialog user, changed his password in BW4 and changed user back to communication user.

      And see, the user and roles get updated properly by now!




      Author's profile photo Mario Panzenboeck
      Mario Panzenboeck
      Blog Post Author

      Glad it solved your problem! 😉