Get Started
Support Home

We’ve launched a new Help Center!

Visit the new Documentation space for Azure DevOps and monday.com or visit the new Customer Support Portal for Azure DevOps and monday.com. If you require any assistance or have any questions, please email support@7pace.com.

Learn more

Internal Server Error

Officially Answered
Follow
New post
Avatar
Stefano

I have installed Timetracker 5.48.5.59244 (Latest) on DevOps Server 2022 on-premises (19.205.33618.1 (Azure DevOps Server 2022.0.)

The extension is installed in the DevOps Extension panel.

Clicking on any of the Timercker tabs I see nothing, but the loading icon and in the Edge console I see this message: 

ms.vss-web.core-content.es6.imjfXc.min.js:1  GET http://devopsserver:8090/ 500 (Internal Server Error)

 

I already followed some hints here but I did not solve the issue. Can you help me to make it working? Thanks.

0

Comments

8 comments

Sort by Date Votes
  • Avatar
    Stefano

    I solved installing asp.net hosting bundle.

    0
    Comment actions Permalink
  • Avatar
    dev

    Hello Stefano,

    Thank you for your feedback. We're glad you were able to solve this one.

    Best regards,

    Apostol

    0
    Comment actions Permalink
  • Avatar
    Lee Sambridge

    Still an issue for me, and I have hosting bundle 6.0.21 on the server 

     

    HTTP Error 500.30 - ASP.NET Core app failed to start

    Common solutions to this issue:

    • The app failed to start
    • The app started but then stopped
    • The app started but threw an exception during startup

    Troubleshooting steps:

    • Check the system event log for error messages
    • Enable logging the application process' stdout messages
    • Attach a debugger to the application process and inspect

    For more information visit: https://go.microsoft.com/fwlink/?LinkID=2028265

    0
    Comment actions Permalink
  • Avatar
    Lee Sambridge

    I got that to go away, with installing your latest package, but now the main settings gives a 500, and the vsix in the work item tab fails with a 500 as well.

     

    Im running the latest dev ops 2020 updates and patches, if that makes a difference, it was working before I upgraded your component.  Is there a way to roll it back?

    0
    Comment actions Permalink
  • Avatar
    Lee Sambridge

    See below for the error from the even log, it appears you have missed somthing here!!

     

    Category: Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer
    EventId: 2
    SpanId: 98530e95e1ab2402
    TraceId: e15e1d517f743709f27b11806d6c93bb
    ParentId: 0000000000000000
    RequestId: 80000004-0006-db00-b63f-84710c7967bb
    RequestPath: /Integration/WorkItemContextMenu

    Connection ID "15780613121686634499", Request ID "80000004-0006-db00-b63f-84710c7967bb": An unhandled exception was thrown by the application.

    Exception: 
    System.InvalidOperationException: The following sections have been defined but have not been rendered by the page at '/Views/Shared/_Layout.cshtml': 'dontShowRateUs'. To ignore an unrendered section call IgnoreSection("sectionName").
       at Microsoft.AspNetCore.Mvc.Razor.RazorPage.EnsureRenderedBodyOrSections()
       at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderLayoutAsync(ViewContext context, ViewBufferTextWriter bodyWriter)
       at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
       at StackExchange.Profiling.Internal.WrappedView.RenderAsync(ViewContext context) in C:\projects\dotnet\src\MiniProfiler.AspNetCore.Mvc\Internal\WrappedView.cs:line 42
       at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable`1 statusCode)
       at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable`1 statusCode)
       at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ActionContext actionContext, IView view, ViewDataDictionary viewData, ITempDataDictionary tempData, String contentType, Nullable`1 statusCode)
       at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync(ActionContext context, ViewResult result)
       at Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync(ActionContext context)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|30_0[TFilter,TFilterAsync](ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
    --- End of stack trace from previous location ---
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
    --- End of stack trace from previous location ---
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
       at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
       at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
       at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
       at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
       at Microsoft.AspNetCore.ResponseCaching.ResponseCachingMiddleware.Invoke(HttpContext httpContext)
       at IdentityServer4.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IEndpointRouter router, IUserSession session, IEventService events)
       at IdentityServer4.Hosting.MutualTlsTokenEndpointMiddleware.Invoke(HttpContext context, IAuthenticationSchemeProvider schemes)
       at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
       at IdentityServer4.Hosting.BaseUrlMiddleware.Invoke(HttpContext context)
       at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
       at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
       at Timetracker.Web.Middleware.HttpMiddleware.BasicAsBearerMiddleware.Invoke(HttpContext context, IBasicToBearerHelper basicToBearerHelper) in C:\a\1\s\TimetrackerOnline\TimetrackerOnline.Web\Middleware\HttpMiddleware\BasicAsBearerMiddleware.cs:line 29
       at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
       at Timetracker.Web.Middleware.HttpMiddleware.HttpHeadersMiddleware.Invoke(HttpContext context) in C:\a\1\s\TimetrackerOnline\TimetrackerOnline.Web\Middleware\HttpMiddleware\HttpHeadersMiddleware.cs:line 77
       at Timetracker.Web.Middleware.HttpMiddleware.HttpExceptionMiddleware.Invoke(HttpContext context) in C:\a\1\s\TimetrackerOnline\TimetrackerOnline.Web\Middleware\HttpMiddleware\HttpExceptionMiddleware.cs:line 30
       at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()

    0
    Comment actions Permalink
  • Avatar
    dev

    Hello Lee,

    Thanks for the information!

    Apparently, the issue is related to our latest release.

    Our developers are currently working on a hotfix.

    Once it's available we'll notify you in this thread.

    Kind regards,

    Apostol

    1
    Comment actions Permalink
  • Avatar
    Lee Sambridge

    I see you have just released a fix, much appreciated, quick turnaround

    0
    Comment actions Permalink
  • Avatar
    dev

    Hello again Lee,

    Please try the 5.49.1 version with a fix.

    Could you please confirm that everything works fine now and you're not experiencing any further issues?

    Bests,

    Apostol

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk