We have SAPGUI for Windows 7.40 PL 8 (Gui version: 7400.3.8.8954) running in Windows 10 (64 bit). When user remain within the same ERP Client\Instance; everything is OK. But when they launch additional SAPGUI session for a separate ERP Client\Instance and then start to switch SAPGUI session between them; the SAPGUI crash starts happening intermittently. No ST22 error found; content of error log as below:
(Error)(13.02.17 15:03:33.039): CSapHistoryDb::CreateDB: Microsoft JET Database Engine Database already exists. Error : Loading local DB failed in frontend.
Suspect that it's due to the History data feature of SAPGUI. We try "Clear History", renaming the underlying file and even deleting the file; all doesn't help. Understand that this issue was previously found in 740 PL4; but unsure how this is resolved
In my case, I went to the SAP GUI History directory (found in SAP GUI Options >> Local Data >> History, field "Directory for Input History"), and deleted the Microsoft Access related file in this directory (*.mdb; *.ldb).
Restarting SAP GUI and opening a session created new DB files and the history started working again.
Regards,
Daniel Leal
Thanks for the suggestion Daniel; that is NOT the source of our issue.
After several trials & errors, we finally managed to nail down the issue. The problem is because of an older version of Microsoft Jet Engine (rel 14.0.4760) that's OK for windows 7; but is NOT compatible with SAPGUI for Windows 10. After we upgrade the user Jet Engine to 14.0.7159., the issue is resolved.