cancel
Showing results for 
Search instead for 
Did you mean: 

SAP GUI 7.20 Directory for Input History

Former Member
0 Kudos

HI,

I am setting up a remote logon session where users can access the SAP GUI. The problem I am having is that the Directory for Input History is not mapping to the folder. I have applied the following registry setting

Directory for Input History [HKEY_CURRENT_USER\Software\SAP\SAPGUI Front\SAP Frontend Server\LocalData] “DataPath” (REG_SZ) [Default: ”%APPDATA%\SAP\SAP GUI\History”] {valid path with write permission}

But the GUI is still not remembering the history of user inputs. If I manually enter the file path, the history is as normal. However I do not wish to have to manually input this file path for 200 plus users is there anyway this can be automated?

Thanks in advance for nay help!

Kind regards,

Brendon

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

The history path depends on the operating system.

As per note 1442303, the history path should be:

Windows XP:

==========
C:\Documents and Settings\<username>\Application Data\SAP\SAPGUI\History

Windows Vista/7:

=============
C:\Users\<username>\AppData\Roaming\SAP\SAP GUI\History


Remark: the directory for the history database can also be set to
another default with the variable SetSapGuiHistoryDir while
creating installation packages using the "SAP Installation Server
Administration Tool".

The corresponding registry key is

[HKEY_LOCAL_MACHINE\Software\SAP\SAP Shared]"SaphistoryDir" on
32bit operating systems and
[HKEY_LOCAL_MACHINE\Software\Wow6432Node\SAP\SAP
Shared]"SaphistoryDir" on 64bit operating systems

(Type: "Expandable String Value" NOT "String" !!!).

This folder must be writable at everytime for the affected user.

Hope this helps.

Best regards

Olakunle Lemboye

Answers (2)

Answers (2)

jude_bradley
Advisor
Advisor
0 Kudos

Hello Brendon,

Would  you mind recreating the issue again and uploading  a frontend trace?

To do this, start the GUI, use the ALT+F12 key combination, navigate to the Traces -> Session

Traces, and select LocalDB, recreate the issue, and upload the files to the thread.

Best Regards,

Jude

Former Member
0 Kudos

Hi,

If any one is interested the fix was to restrict access to the local disks on the remote desktop to prevent users saving files locally on the server. The Documents folder was then re-directed to the user’s Home Drive. This allowed the history to be saved.