Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Sometimes maybe you could have gotten this message when you tried to login to XSA services on SAP HANA Express, just like that:
hxeadm@me:/usr/sap/HXE/HDB90> xs-admin-login


When you got this message you can't list XSA applications, because this command requires you have succesfully logged with the XSA_ADMIN user.

So, the way I found to fix the problem was looking for the error in the log/trace files. Specifically theses files are usefull:
hxeadm@me:/usr/sap/HXE/HDB90/<myhome>/trace> ll xsuaaserver*

-rw-r--r-- 1 hxeadm sapsys 4611 Mar 16 23:28 xsuaaserver.out
-rw-r--r-- 1 hxeadm sapsys 4871 Mar 16 22:37 xsuaaserver.out.20190316232651
-rw-r----- 1 hxeadm sapsys 78330 Mar 16 23:28 xsuaaserver_0.log
-rw-r----- 1 hxeadm sapsys 0 Feb 8 18:22 xsuaaserver_0.log.lck


Note that I used the command "ll". You can use "ls -l" as well.

When you check these files, you can see this message:
2019-03-16 22:37:23:132]-[Generic]-[error]: FAILED to check/wait for XSA database being up and running. Error during reloadDatabaseHostsFromHdbnsUtil The secure store is still locked: SSFS-1670: Update of the secure storage is locked by user "hxeadm" from host "<myhost>" since "2019-02-23 12:53:34 UTC" (lock management was under application control at the time of lock creation) (RC = 3).

If you are sure that the locking process is already gone you can resolve that problem by executing:
rm /usr/sap/HXE/SYS/global/xsa/security/ssfs/data/SSFS_HXE.LCK


As you can see, SAP HANA Express gives you the answer in this message:
If you are sure that the locking process is already gone you can resolve that problem by executing:
rm /usr/sap/HXE/SYS/global/xsa/security/ssfs/data/SSFS_HXE.LCK


In my case, the problem was I forgot to connect the battery to my laptop, so it shutdown suddendy and that was the reason the process stayed as locked.

When you remove the file, you only have to reebot you computer (or laptop maybe), and that is all. the problem was fixed!.

I hope this tip can help you.
Labels in this area