DRM 3.4.0 service not running (3.3.2 works)

Same by me. Did the same tests. Upgrade and fresh installation. Nothing helped except of going back to 3.3.2.

Having the same issue here.

Running Windows 10 21H2. ISsue occures with both DRM 3.4.0 as 3.4.1. Version < 3.4 is running fine. Entered password during setup: Password!1

I am able to reproduce this after de-installation and re-installation.

Here is a full stack-trace:

04-05-22 11:56:07 SEVE com.dell.drm.service.DRMService start                                       Terminating Service due to exception : Catastrophic service failure, Issue with C:\Program Files\Dell\Dell EMC Repository Manager\web/database Initialization..
04-05-22 11:57:04 INFO com.dell.drm.service.DRMService setWorkingFolder                            Set working folder for service : C:\ProgramData\Dell\drm.
04-05-22 11:57:04 INFO com.dell.drm.service.DRMService start                                       Title : Dell EMC Repository Manager Service Implementation : 3.4.0.783
04-05-22 11:57:04 INFO com.dell.drm.service.DRMService start                                       Setting password for database
04-05-22 11:57:07 INFO com.dell.drm.service.DRMService getPort                                     Running on port : 8090.
04-05-22 11:57:07 INFO com.dell.drm.datamanager.HibernateUtil buildSessionFactory                  In build Session Factory method:
04-05-22 11:57:07 INFO com.dell.drm.utilities.LockboxUtility lbFileExist                           Lockbox file exists. 
04-05-22 11:57:07 SEVE com.dell.drm.utilities.LockboxUtility getItemValue                          Exception while retrieving the item from lockbox -> {0}
com.emc.security.lockbox.LockboxException: Failed to read persistent Lockbox store
	at com.emc.security.lockbox.Lockbox.readLockboxUpdateCache(Lockbox.java:1458)
	at com.emc.security.lockbox.Lockbox.open(Lockbox.java:905)
	at com.emc.security.lockbox.Lockbox.open(Lockbox.java:312)
	at com.dell.drm.utilities.LockboxUtility.getItemValue(LockboxUtility.java:147)
	at com.dell.drm.datamanager.HibernateUtil.buildSessionFactory(HibernateUtil.java:60)
	at com.dell.drm.service.DRMService.start(DRMService.java:213)
Caused by: com.emc.security.lockbox.LockboxException: The Lockbox is corrupt and failed to load.
	at com.emc.security.lockbox.LockboxMap.loadMapFromBuffer(LockboxMap.java:335)
	at com.emc.security.lockbox.Lockbox.readLockboxUpdateCache(Lockbox.java:1454)
	... 5 more

04-05-22 11:57:09 SEVE com.dell.drm.datamanager.HibernateUtil buildSessionFactory                  Exception in DB Initialization : {0}
java.lang.NullPointerException
	at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
	at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
	at java.base/java.util.Properties.put(Properties.java:1340)
	at java.base/java.util.Properties.setProperty(Properties.java:228)
	at org.hibernate.cfg.Configuration.setProperty(Configuration.java:212)
	at com.dell.drm.datamanager.HibernateUtil.buildSessionFactory(HibernateUtil.java:91)
	at com.dell.drm.service.DRMService.start(DRMService.java:213)

04-05-22 11:57:09 SEVE com.dell.drm.service.DRMService start

Same issue here, we will open a support case later since we have support on it. I will update this thread if a solution is provided. For now we will use the previous version.

Hi there,

I am Florian from Dell.

Can you all tell me whether you are using a full english OS, including Region settings (format, language for non unicode programs) ? 

Is it Installed on a VM running on an hypervisor Installed on an HPe ?

Installed on Win10 20H2, build 19042.1586, physical machine, HP elitebook with AMD Ryzen.
OS is English US, formats and regional set to Slovenian.
Non-unicode is set to use US English.

Tried with newer 3.4.1.810, problem is still there.

Interesting.

Any luck to set every Region settings in english ? Including Welcome screen and New user account ?

DRM is very language sensitive...

Once the settings got changed, make sure to re install DRM. A repair wont be enough.

Make also sure that DRM folder from Programdata and Programs got deleted too.

Do you have any Dell warranty ?

I cannot do any region/localization change as this is used on my personal laptop and would break localization I use for everything else. Maybe if I can spare some time I will install in a virtual machine set to US English localization/region. Will let you know if this helps. Meanwhile, can this also get involved with Dell 's developers, I am aware this was a known problem, but some previous versions worked on past versions of DRM, it seems problem was just re-introduced. Yes we have quite some Dell EMC servers in warranty, are you suggesting we open a Support case for this?

The localized OS restriction is here since DRM 3.3.X. This is mentionned in the release notes.

If you can open a support case for this I would be glad to be engaged on, as I am from Compute L3 support team and able to escalate further to dev teams.

And especially because the issue you are experiencing can be triggered by something else.

Hello, joining this thread to say I'm experiencing the same issue on an English Windows 11 virtual machine. I can't seem to find a solution, I tried uninstalling and reinstalling a few times as well as trying to manually start the service.

In my opionion this is not a localization problem. I think this is coming from the user prompt in the setup to enter a custom database password. When you compare this to the setups before 3.4.0 there never was such a prompt. According to this i would think that there's a problem with the connection string to the database. Could it be a harcoded connectionstring which would be a security issue in the drm that should be solved with the 3.4.0? Perhaps the implementation of the solution ist not well tested?

Hello.

I can confirm that changing the regional settings to US English worked for me. Now the service is starting with 3.4 version. I used Swedish in Regional Settings. Win 10 Pro English i am running on this installation. Hope Dell can fix this so we can use other language settings.

Hi,

As I said, this issue can be trigger by something else.

But one of the most important thing to be checked is the language settings as DRM does not support localized OS.

Flo

Hey,

thanks for the info. Then we have a workaround but the implementation is a bit difficult. The regional settings ENG US brings many problems with it. Keyboard layout etc. This should be better implemented.

You can send me a kudo

Yes I do agree... English UK or US make it work, using OS in english and Lang. For non unicode programs in english.

However, you can use a Keyboard layout with a different language, we finally notice that DRM is not based on that.