DVLS won't start after reboot

Hello,

It's possible that the SQL Server where your Devolutions Server is located may not be up and running by the time the Devolutions Server instance starts. As a result, the Scheduler Service is unable to connect to the database and is returning an error message. To try and resolve this issue, you can configure the service to start "Automatic (Delayed Start)" in the services.msc settings. This may help to ensure that the connection is established successfully.



Best regards,

Thank you for the idea. The "Devolutions Server" service was already at "Delayed Start", but pushing forward, I put the "WWW Publishing Service" at "Delayed Start" which fix the issue I had accessing the Web interface after a reboot.

Still, the Devolutions service won't start after a reboot. Is it possible for you to make it "Depends" on "WWW" service, or "SQL" services?

Hello,

The problem is that you could technically install the Scheduler Service on a different machine so that no IIS could be installed. That said, setting both to Delayed start should fix the issue.

A possible solution would be to put a scheduled task for startup to the machine, with a delay, 15 minutes for example, to start the Devolutions Scheduler service:




Best regards,

So I put MSSQLSERVER in dependencies with this command

sc config DevolutionsSchedulerServiceDVLS depend=MSSQLSERVER

After a reboot, the service start correctly! But now, I receiving a lot of error from "Devolutions Server" with this error.

Error:

InvalidOperationException - Endpoint
Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.GetRepositoryAccessRequests
(Devolutions.Server) contains authorization metadata, but a middleware was not
found that supports authorization. Configure your application startup by adding
app.UseAuthorization() in the application startup code. If there are calls to
app.UseRouting() and app.UseEndpoints(...), the call to app.UseAuthorization()
must go between them. at Microsoft.AspNetCore.Routing.EndpointMiddleware.ThrowMissingAuthMiddlewareException(Endpoint
endpoint) at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext
httpContext) at
Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext
context) at Devolutions.Server.Middleware.LegacyTokenParserMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.OAuth.Middleware.OAuthTokenParserMiddleware.InvokeAsync(HttpContext
httpContext) at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext
context) at
Devolutions.Server.Middleware.ReferrerPolicyMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.Middleware.StrictTransportMiddleware.InvokeAsync(HttpContext
httpContext) at Devolutions.Server.Middleware.XContentTypeOptionsMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.Middleware.XFrameOptionsMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.Middleware.CSPMiddleware.InvokeAsync(HttpContext
httpContext) at Serilog.AspNetCore.RequestLoggingMiddleware.Invoke(HttpContext
httpContext) at
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware
middleware, HttpContext context, Task task) --- Default


Source:

Microsoft.AspNetCore.Routing 

Well, I changed the dependencies to add W3SVC with MSSQLSERVER and reboot, and now everything works fine.

It seems like DVLS need SQL Server AND Web Server to be up before starting...

Here's the command I used

sc config DevolutionsSchedulerServiceDVLS depend=W3SVC/MSSQLSERVER

Hello,

Thank you for sharing this tip with the community!

Best regards,

Hello,

We've incorporated your solution into our knowledge base, creating a new topic: Devolutions Server unavailable after reboot. Thank you for your helpful contribution!

Best regards,