RDM Login Timeout\Error when waking the IIS Site

Hello,

As you are using DVLS beta 2022.1.6, could you please the official release 2022.1.9 that is available online for download here?

Here is the page on how to upgrade DVLS.
https://helpserver.devolutions.net/upgrade_rdms.html

And the same for RDM which version 2022.1.12 is available online for download too here.

Once both updated, if from RDM it's still doesn't work, please let me know if you can log on the DVLS web UI.

Let me know if that helps to solve your issue.

Best regards,

Updated to :
DVLS Version : 2022.1.9.0
RDM Version : 2022.1.12.0

Same issue is still occurring. This is not a major issue and is more of just an annoyance as the first user to login each morning is hit with this error as we need to recycle the IIS App pool overnight to retain performance. The first time the DVLS URL is hit after it has been recycled, it will cause the Data source to "wake up" triggering the "Application has started" message in the datasource logs.

We expect this first connection to take longer as the datasource does take time to start up again. When connecting via the Web URL it can take 30-40 seconds to receive a response but we do not receive an error during this time. In previous version of RDM (prior to 2022) the same would happen in RDM as the web UI. RDM would be slower to connect but would eventually connect without any errors being displayed.

You should be able to replicate the issue

1. Set RDM to Offline
2. Log into the DVLS server and Recycle the Application Pool for the DVLS instance
3. Wait 60 seconds for the Refresh to take affect
4. Set RDM to online (RDM will error after about 10 seconds)

Hello,

Thank you for your feedback.

So I presume you already have implemented these settings?
https://kb.devolutions.net/dps_configure_dps_always_available.html
https://kb.devolutions.net/dps_recycle_application_pool_nightly.html

I will ask our QA team to test this behaviour and will get back to you.

Thank you for your patience.

Best regards,

Thanks Erica, yes I have both of those settings implemented. In theory I could write a task to automatically hit the URL after its recycled to wake it up again.

Hi Stephen,

That could be a workaround until we reproduce it and find a solution.

Best regards,

Hi Stephen,

Our QA team still cannot reproduce your issue yet.

They have a question for you. Do you get the same behaviour when you manually restart the IIS Application Pool?

Best regards,

When restarting the App pool the issue appears immediately after the restart (while DVLS is running through the start-up process) but seems to come back promptly after that finishes. I was curious and left everything untouched after a recycle to see what happens after a longer time and it appears that it does come back online but it takes 10 minutes. If you are unable to replicate I suspect that this could be something with our environment.

I have been able to get a work around implemented that runs a Invoke-WebRequest after the nightly recycle. This seems to bring everything back online a lot faster than just leaving it.

Hello,

Thank you for the information and the solution you have provided to bring your DVLS instance up.

The information has been transmitted to our QA team. We will keep you posted.

Thank you for your patience.

Best regards,