Message: "SAP Logon cannot be startet correctly"

[ernaldo_cezar2]

Good morning colleagues,

We were able to set up our sap logon with 2 configuration files (one local and another central).

It works perfectly.

One scenario we tested was if the central files are not available.

The users get the following warning (not error!!!):

SAP Logon cannot be started correctly.

Error when loading server configuration files:

The file <path> may be incorrect or not available.

The cached server configuration files will be used.

I am quite sure the users will not understand this warning and will send us a lot of tickets about the message.

Is there any way to deactivate it?

The user don't need to know if he/she is using the central file or the cached one.

Best Regards,

Ernaldo Cezar

[Matt_Fraser · Accepted solution]

Hi Ernaldo,

The error message is, of course, correct if the central configuration file repository is not available. Would this not be normally available during normal operation? So that obtaining this error would indicate either a network problem or something else?

Or are you trying to provide for two different scenarios, one for workstation users (always on the network) and another for laptop/remote/vpn users who would not normally want to use central configuration files? If this is the case, my suggestion would be to create two different installation packages on your installation server, one for local/always-on clients and the other for remote/vpn clients. In the second one, setup the installation scripts so as to not point the client to the central config, but instead copy the files locally during installation and use those.

Regards,

Matt

[ernaldo_cezar2 · Accepted solution]

Dear Matt,

You are right, with 2 different installations the problem is solved.

But it was exactly what I wanted to avoid, .

For 2 years we have been using the solution with 2 saplogon files, and we have never had problem regarding the availability of the central file.

Thanks anyway,

Ernaldo

[former_member194094]

Hello Ernaldo,

Could you please try the following:

Go to your "Common" folder, create a new folder named "backup" and copy all
files from your common folder into the backup folder.

Delete all files of your Common folder (except the backup folder) and start
SAP Logon again.

Does the error message popup again?

Kind regards,

Eric

[Former Member]

We are rolling out the latest SAPGUI 740 (PL6) and are providing only the location to the central location via a registry entry in the install package. Our central location is on a DFS-R share such that the file is copied to the domain controllers in all of our locations and the user access the one that is closest to them. 

Sporadically (~5%?) our test users get this error as well!  Our "fix" has been to tell the user to close and re-open SAP Logon.

Have you found any other solutions to prevent this from happening?