DRM Error:There are currently no applications available for login

Most of you would have faced DRM Error:There are currently no applications available for login error while logging to DRM Web-client. No exception to that, I too faced one such instance in recent times.

In this post, we will see what are things to check in DRM when you encounter this error and how this issue got fixed for me.

Note: This post has been written and associated activities have been demonstrated on DRM version 11.1.2.4.344.

One fine morning, one of our DRM users had reported that he is not able to login to DRM Web Client encountering following error message:

Error: There are currently no applications available for login 

Immediately I opened DRM Web Client to confirm whether it's working with ADMIN credentials or not. Like the user, I too faced the same error even with DRM ADMIN account.

When I checked the DRM Web services status in service panel, they were running perfectly fine.

To cross-check the DRM Web Services status, I connected to DRM Configuration Console (as an Administrator):

In Configuration Console, I noticed that, though DRM Web services were up and running, DRM application was stopped.

I thought why not first validate the database connection here and did the same. 

Database connection was successful.

Its time to start the application.

But starting application did not work. I could see, the application was still in stopped state.

Alright, let's search for some errors now.

Open the Windows Event Viewer and Explore Windows Logs-->Application

I noticed total 3 DRM error messages recorded in Event viewer:

Error-1:

Error-2:

Error-3:

Going through the above DRM Error messages, we come to know that DRM application engine could not be started because of:

DRM-63015: Read/Write engine for Application on DRM Server will not start because another Application is currently using the same repository.

Generally, 'DRM-63015' error message indicates that your DRM schema might be locked because some other DRM application has already connected to it i.e. when two DRM applications try to connect to the same DRM schema at the same time, we face 'DRM-63015' error.

This happens when you have two DRM application servers in your Hyperion environment i.e. two DRM Configuration consoles and the secondary DRM application server has been configured to connect to the same DRM schema as the primary DRM application server and you try to start the DRM application on both the servers at the same time.

Ideally, you need to ensure that only one DRM console has been configured to connect to any given DRM schema.

But, in my Hyperion environment, there is only one DRM Server and only one DRM application. So the above scenario is not applicable at least in my case.

Also when I checked, my DRM Schema was not Locked:

So let's proceed further by trying a few troubleshooting steps.

Do 'iisreset' on DRM application server

As DRM's primary web interface runs through IIS (Microsoft Internet Information Service), there's a chance bouncing IIS will free up whatever rogue session might have been locking things up for you.

To bounce IIS service, open a command prompt on your DRM application server and type "iisreset":

If this workaround works for you, it's well and good, If not, move to the next troubleshooting step (For me it didn't work).

'Apply Updates' in DRM Configuration console

To 'Apply Updates' I followed the following steps: 

1- Opened Windows service panel and stopped DRM Web services. 

2- Checked the DRM Configuration console to ensure DRM services are stopped.

3- Now goto DRM Configuration console and select Application-->Apply Updates

4- Click OK on below message while Applying updates:

5- You will see below CMD window opened. As there were actually no updates to apply so we see the message: No updates were applied. 

Press SPACE key to continue. CMD window will be closed then. 

6- Goto the service panel and start DRM Web services on all the servers. 

7- Check DRM Web services status in DRM Configuration console. Both DRM Web services are up and running fine. Also notice, our DRM application too has been successfully started this time.

8- When I opened DRM web-client, my DRM application was available to login.

9- And application login too was working as expected.

So the issue is fixed for me. :-)

We know that Applying Updates to DRM application refreshes the database connection apart from making any changes like patch upgrade, config changes, etc. in your DRM application, effective. 

But exactly what has caused this issue is still not known. This workaround has fixed this issue for me in one go so it can be used as a temporary fix.

Please note, this DRM error "There are currently no applications available for login" can occur due to many reasons. My case was only one of them. 

You need to check the Windows Event Viewer on your DRM server in order to identify the exact root cause of the problem as Event Viewer will most likely have an error message recorded related to your DRM error.