No server-based saplogon.ini entries for BEx Analyzer

[Former Member]

Dear experts,

we are using a server-based saplogon.ini via http-server to connect to the SAP systems. Unfortunately the entries from the server-based saplogon.ini are not shown in BEx analyzer. After every single installation I have to set the connection information manually on every single client. We use SAP GUI 7.20 PL 11, BI Addon 700 (both latest).

Note 1583077 describes the problem very well, but it doesn't solve the problem, because PL 7 is already installed...

Anyone experienced similar issues? Any suggestions?

Kind regards,

Jann

[jude_bradley · Accepted solution]

Hello Jann

Where is the saplogon.ini file located.

Is there more than one saplogon.ini file?

A trace from note http://service.sap.com/sap/support/notes/308929

may throw some light on the issue.

Regards,

Jude

[Former Member · Accepted solution]

Hello Jude

thank you for your answer. The saplogon.ini is located on a http-server within our network (e.g. http://sap.company.lan/SapLogonTree.xml or saplogon.ini).

Furthermore I have an additional saplogon.ini on my client, because as administrator I need more systems than the "normal" user. This is located at C:\Users\<user>\AppData\Roaming\SAP\Common

In the BEx Analyzer only the entries of the local saplogon.ini are visible. The entries of the server-based ini are not shown in BEx, only in the SAP Logon.

I tried to start a trace from note 308929, and here is what it brings to light:

Tue Mar 27 11:43:40 2012 0001  start wdtlog trace file in c:\trace
Tue Mar 27 11:43:40 2012 0001  Version 7200.3.8.105
Tue Mar 27 11:43:40 2012 0001  ---
Tue Mar 27 11:43:40 2012 0001  CWDTLConnection::Logon()  start
Tue Mar 27 11:43:40 2012 0001  CWDTLConnection::Logon()  start loop
Tue Mar 27 11:43:40 2012 0001  CWDTLConnection::Logon()  display dialog
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  current directory C:\Users\<user>\Documents
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  SAPLOGON_INI_FILE not set; use C:\Windows\SAPROUTE.INI
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  current directory C:\Users\<user>\Documents
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  SAPLOGON_INI_FILE not set; use C:\Windows\SAPMSG.INI
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  current directory C:\Users\<user>\Documents
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  SAPLOGON_INI_FILE not set; use C:\Windows\SAPROUTE.INI
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  current directory C:\Users\<user>\Documents
Tue Mar 27 11:43:40 2012 0001  MSConfiguration::MSConfiguration()  SAPLOGON_INI_FILE not set; use C:\Windows\SAPMSG.INI
Tue Mar 27 11:44:13 2012 0001  DpaPersPar::BasicInitialization() - GetSapLogonLocalConfigurationDirectory C:\Users\<user>\AppData\Roaming\SAP\Common\saplogon.ini
Tue Mar 27 11:44:13 2012 0001  DpaPersPar::BasicInitialization() - GetSapLogonServerConfigurationFileName http://sapgui.company.lan/SapLogonTree.xml
Tue Mar 27 11:44:14 2012 0001  DpaPersPar::BasicInitialization() - GetSapLogonIniFilesFromServerConfigurationFile http://sapgui.company.lan/saplogon.ini
Tue Mar 27 11:44:14 2012 0001  GetServerConfigurationFileName() - http://sapgui.company.lan/saplogon.ini doesn't exist 
Tue Mar 27 11:44:29 2012 0001  CCWDTLogonPropertySheet::SetProfileNameAsEnvironmentVar() File exists - SAPLOGON_INI_FILE not set; use C:\Users\<user>\AppData\Roaming\SAP\Common\saplogon.ini
Tue Mar 27 11:44:29 2012 0001  Release Allocate 
Tue Mar 27 11:44:29 2012 0001  Release Allocate - End 
Tue Mar 27 11:44:32 2012 0001  CCrypto::GenerateKey() 
Tue Mar 27 11:44:32 2012 0001  Release Allocate 
Tue Mar 27 11:44:32 2012 0001  Release Allocate - End 
Tue Mar 27 11:44:32 2012 0001  CCrypto::GenerateKey() - Success 
Tue Mar 27 11:44:32 2012 0001  CWDTLConnection::Logon()  RfcOpenEx  USER="USER" CLIENT=001 LANG="DE" PASSWD=":-) secret (-:" SYSNR=00 ASHOST=HOSTNAME ICCE=1 CODEPAGE=1160 GETSSO2=1 PCS=1
Tue Mar 27 11:44:32 2012 0001  ***CWDTLConnection::Logon - GetDefaultFromRegistry() File exists - SAPLOGON_INI_FILE not set; use C:\Users\<user>\AppData\Roaming\SAP\Common\saplogon.ini
Tue Mar 27 11:44:32 2012 0001  CWDTLConnection::Logon()  WDTL_CHECK_PASSWORD_OK
Tue Mar 27 11:44:32 2012 0001  CWDTLConnection::Logon()  RFC_HANDLE_OKAY TRUE
Tue Mar 27 11:44:51 2012 0001  Release Allocate 
Tue Mar 27 11:44:51 2012 0001  Release Allocate - End 

//edit: Of course this is not correct:

Tue Mar 27 11:44:14 2012 0001  GetServerConfigurationFileName() - http://sapgui.company.lan/saplogon.ini doesn't exist 

In the normal SAP Logon the server-based ini works very well!

Any further suggestions?

Message was edited by: Jann Willms

[Former Member · Accepted solution]

I just set up a clear windows installation and only installed office and the SAP GUI including BEx. The entries of the server-based ini are in BEx!

I think the error occurs because I have an additional saplogon.ini on my client. But the problem is, we updated all clients from 7.10 to 7.20, so every client has an additional saplogon.ini file on them... (beacuse server-based ini's were not supported at this time).

[jude_bradley · Accepted solution]

Hello Jann,

Maybe this note can help

http://service.sap.com/sap/support/notes/1409494

Regards,

Jude

[Former Member · Accepted solution]

Hello Jude

The searching order of the saplogon.ini file in SAP GUI for Windows 7.20 can be summarized as follows: 
1. File name from command line parameter /INI_FILE=
2. File name from environment variable SAPLOGON_INI_FILE
3. "saplogon.ini" under "Path of Local Configuration Files" shown in SAP Logon Setting dialog
4. "saplogon.ini" in the SAP GUI installation directory*
5. "saplogon.ini" in the Windows directory*
*Comment: 4) and 5) will be only considered at the first start of SAP  Logon (Pad) 7.20 if no saplogon.ini file is yet existing under "Path of  Local Configuration Files" described in point 3) and the file found will  be copied to the "Path of Local Configuration Files" for next SAP Logon (Pad) start.

As I already suggested, the first step to search for a saplogon.ini is the webserver, because I didn't set a parameter nor an environment variable.

Seems like this is a bug?

[jude_bradley · Accepted solution]

Hello Jan,

Can you test one machine where the C:\Windows\saplogon.ini file is renamed to saplogon.bak

for example, reboot, and test again.

In our WTS server the GUI settings for a remote logon.ini file are in the format shown below:

(sorry it's in German,but you get the idea).

You should also set the environment variable SAPLOGON_INI_FILE to the desired

path where the saplogon.ini file you require resides.

Regards,

Jude

[Former Member · Accepted solution]

Hello Jude

Because I have a server-based and a local saplogon.ini, both fields are filled as you can see on the picture below. Furthermore there is no C:\Windows\saplogon.ini on my client.

When I set the environment variable to the http-server, something is going wrong and only the local saplogon.ini is used. I will try to trace this tomorrow...

Thanks,

Jann

[jude_bradley · Accepted solution]

Actually Jann, Would you mind running the program nwcheckworkstation from the run menu

and advise if there are any errors reported in the GUI check?

[Former Member · Accepted solution]

Sorry Jude, no errors occured.

[jude_bradley · Accepted solution]

Hello Jann,

The note

http://service.sap.com/sap/support/notes/1426178

gives some guide on how to set up the configuration files.

Regards,

Jude

Make sure you are using the most recent patch (11).

[Former Member · Accepted solution]

Hello Jude,

we are using the most recent patch as I stated out in my first post. I set up the server-based saplogon.ini as described in note 1426178. Especially this point makes me think this might be bug:

7. After that your users can start SAP Logon by clicking the installed SAP Logon icon on the desktop.
The folders and entries defined on the server site will be shown  together with the local configuration.

This is in the SAP Logon right, but not in the BEx Analyzer. This issue occurs on different clients. I set up an additoinal (fresh and clean) installation of Windows 7 with Office 2007. On this client the problem doesn't occur. Even if I add another system to the saplogon.ini, BEx shows me all systems (server-based and the manually added one). On my laptop and several other clients this doesnt work.

[Former Member · Accepted solution]

I figured out that the server-based entries on the clean Win7 installation dont work correctly! They are visible in the BEx Analyzer but dont work correctly! When I try to connect to our BI-System the following error appears:

No entry for "SYSNR=00" found in C.\Windows\sapmsg.ini"

If I look up the setting on the "Server" tab, no "Host" is entered! If I enter the hostname manually, everything works fine.

[jude_bradley · Accepted solution]

Hello Jann,

Can you create a message in component BC-FES-AIT-CTR, with the uploaded

trace and a WTS connection please?

I can then get DEV to investigate the issue.

Thanks in advance,

Jude

[jude_bradley · Accepted solution]

Maybe the file is within the specified directioy but the permissions
are wrong. Please. check it.

As the sapmsg.ini is not in the windows directory (C:\WINDOWS\) you can
spezify the path to the sapmsg.ini file via the environment variable
'RFC_LOGON_INI_PATH'.

Regards,
Jude

[Former Member · Accepted solution]

Hello Jude,

I already tried to create sapmsg.ini within C:\Windows\ without succes. I created message 277714 in BC-FES-AIT-CTR for further analysis.

Thanks in advance,

Jann

[jude_bradley · Accepted solution]

Hello Jann

I see Sven has the message.

You should be in good hands,

Jude

[Former Member]

That's what SAP wrote so far:

Dear Customer,

The issue with the server based entries is due to the

message server not available for the R3 systems. Internally

we were not able to reproduce the issue as we have pre-defined

message servers for all the R3 systems. As we were able to

track the root cause of the issue, we are working on it and

will update on it at the earliest.

Thanks for your continued support and co-operation.

Thanks

[Former Member]

For those of you who haven't installed PL 11 yet (and experience the same problem), see the following notes:

http://service.sap.com/sap/support/notes/1636823

http://service.sap.com/sap/support/notes/1671062