-
Notifications
You must be signed in to change notification settings - Fork 75
Troubleshooting Guide and FAQ List
In some cases, the Azure services we rely on may themselves be down. This is not a problem with the Decision Service itself. Please retry your deployment at a later time; if the problem persists, please open an issue here if one does not already exist. Our Github issues page is also a good source for finding potential solutions to your problem.
Cause: A limitation of certain versions of IE.
Solution: Run IE as administrator and/or check the “Enable DOM Storage” box in IE tools/Internet Options/Advanced/Security/.
Cause: Your Azure subscription does not have the rights to deploy one or more of the Decision Service components in your chosen region. In particular, we make use of the "Classic Cloud Service" resource which by default is not always supported in all regions.
Solution: Retry in a different region, or open an Azure ticket to request additional account privileges. An alternative way to find out which region you have access to is to manually create a new Classic Cloud Service: In Azure portal, click on New -> Cloud service (classic) and select a location. If the location is not supported, you will get a red exclamation mark.
After clicking Deploy To Azure, I get redirected to the Azure portal page but nothing shows up, what to do?
The portal sometimes fails to open our deployment template, simply retrying should fix this.
- Go to the Azure portal at https://portal.azure.com .
- Click on Resource Groups in the left navigation menu.
- Find the resource group under which you deployed, and click on it.
- In the list of resources, find and click on the Management Center named mc-*, where * is the unique string generated during deployment.
- Click on Browse to open the website or copy and paste the URL displayed.
- Go to the Azure portal at https://portal.azure.com .
- Click on Resource Groups in the left navigation menu.
- Find the resource group under which you deployed, and click on it.
- In the list of resources, find and click on the Management Center named mc-*, where * is the unique string generated during deployment.
- In the settings, under General, click on Application Settings.
- Under App settings, you will see the Password.
If you happen to be in the Deployment panel, you can also click on the Management_Center from there, and find the MANAGEMENT CENTER PASSWORD among the Inputs.
- Open the Management Center resource from Azure portal as instructed above.
- Click on Settings to open the settings tab, then click on Deployment Source.
- Click on Sync, this will trigger a pull from github and redeploy of the website.
An uncustomized instance of the Decision Service (DS) includes the following Azure resources:
- Storage Account
- Cloud Service with a standard D1_v2 worker role
- Service Bus with 4 standard Event Hubs
- Two instances of Stream Analytics, each with 1 throughput unit
- 1 Basic Web App service to host the Management Console and expose an HTTP endpoint
There are many ways to get a free subscription on Azure. For non-free subscriptions, an uncustomized deployment costs around $0.20 per hour.