Connection error when using automatic logon option in connection wizard

[Former Member]

Hi,

When using the automatic logon option in the connection wizard there is an error that say that the connection cannot be established. If I use the option to type in my credentials then it works fine.

The user has access privileges in SAP BPC.

Any suggestions?

Kind regards,

Christof

[sorin_radulescu · Accepted solution]

The installation of BPC server was done with a domain user or with a local user?

Your windows user is a domain user or a local user?

I'm asking because it is strange that Windows authentication is not working. It can be or bvecause Windows user is not the same with BPC user. (you can have the same name for user but actually one is local the other one is domain which means different users).

Also I tsuggest to check into application server of test and prod environment f osoft virtual directory has enable Windows Authentication.

Regards

Sorin Radulescu

[Former Member · Accepted solution]

Update:

- The User for Windows and SAP should be the same

Question:

- In IIS the "Integrated Windows Authentication" is turned on our Development environment. However in our Test and Production Environment this is not activated. Could this be a reason for this issue?

[i045436 · Accepted solution]

Hi,

The Osoft directory must have Integrated Windows Authentification checked, otherwise only basic authentification is allowed and you have to specify user and password every time.

Hope this can help you,

Mihaela

[Former Member · Accepted solution]

Hi,

We have tested to turn on this option and reset the IIS to ensure the changes are incorporated on our Test environment. Unfortunately this did resolve the situation. Other suggestions?

Kind regards,

Christof

[Former Member · Accepted solution]

It could be related to BPC security.

When you use Integrated authentication, BPC client will send your current windows session credentials (the one you used to log on your desktop).

This account may be valid in your DEV environment whereas it's not on other environment. Make sure that you log on the appset in the new environment with an administrator account and reprocess the security (modify team / task profiles ... etc).

Once the security is reprocessed in the new environment, retry to log with integrated authentication.

[Former Member · Accepted solution]

Hi,

The resolution was:

- Enable "integrated windows authentication" in IIS on the server

- Restart IIS

- Reinitialize the client via menu in client software: eTools> client options > clear local application information

Kind regards,

Christof

[Former Member]

Hallo,

Are u using citrix to acces the client? Or is BPC installed locally? If the user is using citrix, I suggest you check the login information there...

Hope it helps,

Kristoff

[Former Member]

Hi,

BPC is installed locally.

I have discovered in the mean time that our development environment does work well but our test/production environment does not.

Kind regards,

Christof