Bot published to Azure getting Internal Server Error RRS feed

  • Question

  • So I've been creating a chatbot using the Bot Framework SDK v4. I've been testing it locally and it works fine with the Bot Emulator.

    I want to be able to host it on Azure and access it remotely but when I publish it and the browser opens up my azurewebsites.net webpage, the page just displays an error saying **An error occurred while starting the application.**

    When I look at the console to inspect the error, there are 2 requests for resources that fail to load:

        Failed to load resource: the server responded with a status of 500 (Internal Server Error) /favicon.ico:1 
        Failed to load resource: the server responded with a status of 500 (Internal Server Error) (index):1

    This is my first time using or publishing something to Azure so I'm not overly familiar with it. As far as I know, there aren't any files in my local directory under those names, and I'm not sure how to rectify the issue.

    And idea's as to whats causing this? I can provide more code if needed.

    More information I've gathered from Application Insights and Kudu.

    When trying to send a message to the bot in Azure using the 'Test Web App​', I'm getting these exceptions thrown:

        System.IO.FileNotFoundException: Could not find file 'D:\home\site\wwwroot\Chatbot.bot'.
         File name: 'D:\home\site\wwwroot\Chatbot.bot'
         at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options)
         at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
         at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize)
         at System.IO.File.OpenText(String path)
         at Microsoft.Bot.Configuration.BotConfiguration.<LoadAsync>d__31.MoveNext()
         --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Microsoft.Bot.Configuration.BotConfiguration.Load(String file, String secret)
         at ChatBotProject.Startup.<>c__DisplayClass6_0.<ConfigureServices>b__0(BotFrameworkOptions options) in C:\Users\Marko\Documents\Project\ChatBotProject\ChatBotProject\Startup.cs:line 47
         at Microsoft.Extensions.Options.ConfigureNamedOptions`1.Configure(String name, TOptions options)
         at Microsoft.Extensions.Options.OptionsFactory`1.Create(String name)
         at Microsoft.Extensions.Options.OptionsManager`1.<>c__DisplayClass5_0.<Get>b__0()
         at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
         at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
         at System.Lazy`1.CreateValue()
         at Microsoft.Extensions.Options.OptionsCache`1.GetOrAdd(String name, Func`1 createOptions)
         at Microsoft.Extensions.Options.OptionsManager`1.Get(String name)
         at Microsoft.Extensions.Options.OptionsManager`1.get_Value()
         at Microsoft.Bot.Builder.Integration.AspNet.Core.ApplicationBuilderExtensions.UseBotFramework(IApplicationBuilder applicationBuilder)
         at ChatBotProject.Startup.Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory) in C:\Users\Marko\Documents\Project\ChatBotProject\ChatBotProject\Startup.cs:line 122
         --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
         at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure(IApplicationBuilder app)
         at Microsoft.AspNetCore.ApplicationInsights.HostingStartup.ApplicationInsightsLoggerStartupFilter.<>c__DisplayClass0_0.<Configure>b__0(IApplicationBuilder builder)
         at Microsoft.ApplicationInsights.AspNetCore.ApplicationInsightsStartupFilter.<>c__DisplayClass0_0.<Configure>b__0(IApplicationBuilder app)
         at Microsoft.AspNetCore.Server.IISIntegration.IISSetupFilter.<>c__DisplayClass3_0.<Configure>b__0(IApplicationBuilder app)
         at Microsoft.AspNetCore.Hosting.Internal.AutoRequestServicesStartupFilter.<>c__DisplayClass0_0.<Configure>b__0(IApplicationBuilder builder)
         at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()

    Furthermore, from checking the logs in Kudu, the html has a description of what the cause might be:

        <h4>Most likely causes:</h4>
            <li>IIS received the request; however, an internal error occurred during the processing of the request. The
                root cause of this error depends on which module handles the request and what was happening in the worker
                process when this error occurred.</li>
            <li>IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS
                permissions are set incorrectly.</li>
            <li>IIS was not able to process configuration for the Web site or application.</li>
            <li>The authenticated user does not have permission to use this DLL.</li>
            <li>The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.</li>

    Any assistance with this would be greatly appreciated

    Sunday, December 2, 2018 11:38 AM

All replies

  • For a specialized assistance on Azure Bot Service issue, you may post your query on SO, for receiving insights from the right set of experts.
    In the interim, to isolate the issue - navigate to your Bot Service app in the Azure portal. In the left navigation, click on Diagnose and solve problems and try the recommendation solution to see if that helps.

    A runtime issue happens when the files in your wwwroot folder are exactly what they should be, but for some reason the site doesn't run correctly. You may checkout the suggestions outlined in Deployment vs runtime issues to help rectify the issue.  

    Monday, December 3, 2018 6:08 PM