Botframework-sdk: [Azure Bot Service] An internal error occured at the server (Can't access bots anymore)

Created on 18 Oct 2017  路  16Comments  路  Source: microsoft/botframework-sdk

Bot Info

  • Deployment Environment: Azure Bot Service

Issue Description

Can't access my bot due message "Error occured on Server"

Reproduction Steps

  1. Login to Azure
  2. Go to resource group
  3. Add a Bot Service
  4. existing subscription (on which multiple working bots were created)
  5. exisiting resourcegroup (on which ...)
  6. using a free app service plan (on which 2 or 3 bots are running)
  7. Click create
  8. Wait to finish
  9. Open
  10. See error zipmi7ay

Expected Behavior

The bot settings to open

Actual Results

a message "An internal error occured at the server"
zipmi7ay
bot service error

Extra info

This happened after I had another issue in Azure Bot Service. Which I contacted @Azure for then they told me to file a bug report about that. When I wanted to that I got this error (this is several days ago).
I created around 5 bots that give this error.

bug

Most helpful comment

Is anyone still experiencing this issue?

All 16 comments

@jochem4207 Thank you for reporting this. The Bot Framework team is actively investigating the issue. I'll report back here once we've determined the root cause.

Same issue. Just created a new BOT on Azure and getting the "internal error" issue.

Any update @EricDahlvang ?

Hello everybody.

I had the same issue with the bot service. My solution was to create the bot service with a new account, without tenants suscriptions. I gave access to the new account to my tenant suscription, with the new account created, create the bot service, it should works. The new account was an outlook account.

Hope it could be usefull for someone.

@jochem4207 @mlimache @petemh

Do you have a guest account in the target tenant for the subscription being used?

Yes. I have a lot of users on that subscription. Just create a new outlook account, gave him a contribuitor role on the Azure subscription and try to create a bot service with the new account. It should works.

@mlimache Thank you for your reply. However, I am attempting to help determine root cause: not find a work-around.

@EricDahlvang good luck, and don't forget to share your information with us.

Hi @EricDahlvang I am a guest in a customer's subscription (they gave me the contributor role) and I am facing the same issue

@sebastinovich do you have another subscriptions in your account? Use a new account, with an only tenant, like the image.
image

It's a temporary solution to continue the develop. The problem is not the role.

@mlimache I appreciate that you've found a temporary solution: but that is not a permanent solution, as it does not address the root cause of the issue.

@sebastinovich

mlimache has a good point. When you attempt to access the bot in your customer's subscription, do you first change the Directory to the subscription for the customer within the Azure portal?

I have two subscriptions here:

image

@EricDahlvang for me i've to switch directories indeed

Is anyone still experiencing this issue?

@EricDahlvang for me its fixed. I will close it, feel free to reopen it as needed. Thank you very much!

Fixed. Thank you!

Was this page helpful?
0 / 5 - 0 ratings