cancel
Showing results for 
Search instead for 
Did you mean: 

instance is in error into bi4 after having change bw password

Former Member
0 Kudos

Dear all,

I am working on BW 7.01 and bi4.0 sp6

I am working with a sap authentication for connecting to bi4.

I am scheduling an instance on a webi document (based on a bics connection) using a user A.

The instance is executing well.

I am changing the password of the user A in BW.

At the next execution of the instance, the instance is in error, and my user is locked in BW. BI4 has tried to connect to bw several times with a wrong password. That explains the problem: user blocked, instance in error.

How to synchronize the password that I changed in bw in bi4? My workaround is to reschedule manually all my instances to catch the new password.

What I did?: I have searched in sap notes a solution for this problem. I did the same thing on several web sites. Nothing on this topic. I have a walkaround: the user A must be an exploitation user and not a named user and the password of this user must have the option "never expire". So, in this case, I will no have the problem mentioned in this discussion.


Best Regards,

Accepted Solutions (1)

Accepted Solutions (1)

saurabh_sonawane
Active Contributor
0 Kudos

we have to do changes in CMC also if u had change the password in BW same thing

in CMC

  1. Log into SAP BO BI4.0 CMC as Administrator,
  2. Go to Authentication -> SAP
    Setup Entitlement Systems
saurabh_sonawane
Active Contributor
0 Kudos

or check all connection had you use that user name and password while developing a connection

and make sure that your connection is SSO

Former Member
0 Kudos

Dear all


Thanks Saurabh Sonawane for your answer.


I think it is not really the good way to solve my problem.


The answer of sap is the following one:

"If this is the case I can tell you that is the normal behavior because

when running a recurrent schedule, it uses a cached credentials of the

user who created the schedule. However if a user who logged on to the

system , the current session credentials will be used."


So, for SAP, this behavior is a normal behavior.


Br

Answers (0)