Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

InternalServerError - Bot & QnA Maker #2572

Closed
andrzejsobczak opened this issue Apr 7, 2017 · 10 comments
Closed

InternalServerError - Bot & QnA Maker #2572

andrzejsobczak opened this issue Apr 7, 2017 · 10 comments
Labels
bug Indicates an unexpected problem or an unintended behavior. help wanted investigate

Comments

@andrzejsobczak
Copy link

andrzejsobczak commented Apr 7, 2017 •
edited

I would like to ask for your help in the following situation:

  1. I created a knowledge sharing service from the knowledge base using the QnA Maker (I created question and answer base and it worked very well).

  2. Then, using the standard steps described in the Bot Framework documentation, without the slightest problem I generated a bot (in C#, I used a template to connect it to a previously created knowledge base in the QnA Maker), and the bot worked without any problem. It was visible at https://dev.botframework.com/ (after logging in to my bots), it responded correctly to the questions asked, clicking on “test connection to your bot” gave the answer “Accepted” – so everything was fine.

  3. Since then, I have not made any changes to the automatically generated code. After a few hours, the bot stopped working – i.e. the source code was missing from the Azure portal. Error like the one in the attached screenshot popped up.

image

Currently, at https://dev.botframework.com (after logging in to my bots), clicking on “Test” gives the following answer:

InternalServerError

<title>Runtime Error</title> 
<body bgcolor="white">

        <span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1>

        <h2> <i>Runtime Error</i> </h2></span>

        <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">

        <b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
        <br><br>

        <b>Details:</b> To enable the details of this specific error message to be viewable on remote machines, please create a &lt;customErrors&gt; tag within a &quot;web.config&quot; configuration file located in the root directory of the current web application. This &lt;customErrors&gt; tag should then have its &quot;mode&quot; attribute set to &quot;Off&quot;.<br><br>

        <table width=100% bgcolor="#ffffcc">
           <tr>
              <td>
                  <code><pre>

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

              </td>
           </tr>
        </table>

        <br>

        <b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the &quot;defaultRedirect&quot; attribute of the application&#39;s &lt;customErrors&gt; configuration tag to point to a custom error page URL.<br><br>

        <table width=100% bgcolor="#ffffcc">
           <tr>
              <td>
                  <code><pre>

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>





  1. Thinking that something magically broke – I removed everything and repeated the whole step 2 (I generated a new bot by connecting it to the service shared by QnA Maker), and the situation in step 3 repeated.

I am working on the standard Azure settings, I did not change anything in the code and it breaks itself (?). I will be grateful for help.

PS. I am using paid Azure subscription.

Best Regards,
Andrzej
@EricDahlvang
Copy link
Member

Hey andrzejsobczak,

I apologize for not responding sooner. Your situation sounds frustrating.

The developers believe its a bug on our side. They've been actively investigating and intend on releasing a fix as soon as possible. Thank you for your patience thus far.

We will leave this issue open until the fix is released.

Peace,
Eric

@EricDahlvang EricDahlvang added the bug Indicates an unexpected problem or an unintended behavior. label Apr 8, 2017
@EricDahlvang
Copy link
Member

EricDahlvang commented Apr 8, 2017 •
edited

The issue is currently being addressed.

@EricDahlvang
Copy link
Member

Thank you for reporting this.

I'm closing the issue because its been addressed. If something like this happens again, please re-open it.

@stevengum
Copy link
Member

Due to similarities between issues, reopening this and referencing issue #2577.

@stevengum stevengum reopened this Apr 9, 2017
@nwhitmont nwhitmont added the C# label Apr 11, 2017
@expatiating expatiating mentioned this issue Apr 13, 2017
Closed
@DonSchenck
Copy link

Any news/updates?

@EricDahlvang
Copy link
Member

Hey DonSchenck,

The issue has been addressed, but the fix involves a two part roll-out to production. One piece was released last night, and newly created bots will no longer have this issue. However, there's another part to the fix that is scheduled to be released this morning. Once that is released, and verified, I'll close this issue.

Thanks for your patience.

@DonSchenck
Copy link

Terrific news! Thanks!

@EricDahlvang
Copy link
Member

Thank you for reporting this. I'm closing it now since the issue has been resolved. If you have any other problems, please re-open this one, or create a new issue.

@andrzejsobczak
Copy link
Author

The nightmare has returned. After about a week of correct work again InternalServerError appeared:
InternalServerError

<title>Runtime Error</title>

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

@andrzejsobczak andrzejsobczak mentioned this issue Apr 18, 2017
Closed
@nwhitmont
Copy link
Contributor

relates to #2603

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Indicates an unexpected problem or an unintended behavior. help wanted investigate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nwhitmont @DonSchenck @EricDahlvang @stevengum @andrzejsobczak