Symptom
- When you perform a recovery of your HANA DB, you are facing the following error in backup.log.
2022-05-04T13:58:55+09:00 P0016051 1808d6f3d71 ERROR RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, [110092] Recovery failed in nameserver startup: An error occured while retrieving topology from backup: exception 301102: lss exception: LSS refused connection (reason: Version mismatch)
And in nameserver trace, you also notice the following information.
[16105]{-1}[-1/-1] 2022-05-04 13:58:51.866099 e LssClient LssClientTracer.cpp(00035) : isAvailable [controller]: lss exception: LSS refused connection (reason: Version mismatch)
[16105]{-1}[-1/-1] 2022-05-04 13:58:51.866252 e Crypto LssController.cpp(00051) : LSS call failed: exception 1: no.301102 (Crypto/LocalSecureStoreClient/ExceptionTranslator.hpp:102) TID: 16105
lss exception: LSS refused connection (reason: Version mismatch)
[16105]{-1}[-1/-1] 2022-05-04 13:58:51.866363 e RootKeyManager RootKeyStoreTypeGetter.hpp(00135) : Failed to read usage information from LSS: exception 1: no.301102 (Crypto/LocalSecureStoreClient/ExceptionTranslator.hpp:102) TID: 16105
lss exception: LSS refused connection (reason: Version mismatch)
[16105]{-1}[-1/-1] 2022-05-04 13:58:51.866409 i RootKeyManager RootKeyManager.cpp(00153) : Singleton RootKeyManager serves keys for database ID: 1
[16105]{-1}[-1/-1] 2022-05-04 13:58:51.867392 i RootKeyManager RootKeyManager.cpp(00153) : Singleton RootKeyManager serves keys for database ID: 1
[16118]{-1}[-1/-1] 2022-05-04 13:58:55.390841 e LssClient LssClientTracer.cpp(00035) : isAvailable [controller]: lss exception: LSS refused connection (reason: Version mismatch)
[16118]{-1}[-1/-1] 2022-05-04 13:58:55.390977 e Crypto LssController.cpp(00051) : LSS call failed: exception 1: no.301102 (Crypto/LocalSecureStoreClient/ExceptionTranslator.hpp:102) TID: 16118
lss exception: LSS refused connection (reason: Version mismatch)
[16118]{-1}[-1/-1] 2022-05-04 13:58:55.392750 e Backup BackupMgr_Manager.cpp(06501) : Aborting recovery because of exception 1: no.110092 (Backup/impl/Backup_Recover.cpp:101) TID: 16118
Recovery failed in nameserver startup: An error occured while retrieving topology from backup: exception 301102: lss exception: LSS refused connection (reason: Version mismatch)
exception throw location:
......
[16118]{-1}[-1/-1] 2022-05-04 13:58:55.404512 e Backup BackupMgr_Manager.cpp(06551) : :::: RECOVERY finished with error: [448] recovery could not be completed, [110092] Recovery failed in nameserver startup: An error occured while retrieving topology from backup: exception 301102: lss exception: LSS refused connection (reason: Version mismatch)
::::
[16118]{-1}[-1/-1] 2022-05-04 13:58:56.188064 i DaemonClient Network.cpp(00070) : Message "stop with comment". Daemon pid 16021. Child pid 16051
[16118]{-1}[-1/-1] 2022-05-04 13:58:56.189889 f NameServer TREXNameServer.cpp(03731) : An error occured while retrieving topology from backup: exception 301102: lss exception: LSS refused connection (reason: Version mismatch)
-> stopping instance ...
- When trying to unregister a system replication site, you get the same error:
> hdbnsutil -sr_unregister
unregistering site ...
nameserver <host>:<port> not responding.
unhandled ltt exception: exception 301102: lss exception: LSS refused connection (reason: Version mismatch)
failed. trace file <nameserver trace> may contain more error details.
- You run into same error when trying to uninstall LSS using resident hdblcm
INFO: Output line 8: unhandled ltt exception: exception 301102: lss exception: LSS refused connection (reason: Version mismatch)
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
SAP HANA, platform edition 2.0
Product
Keywords
recovery, LSS, version mismatch, LSS refused connection , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , HAN-DB-SEC , SAP HANA Security & User Management , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.