Microsoft.WindowsAzure.Storage.StorageException: The remote name could not be resolved: 'vmname.table.core.windows.net'

-

Below error in data export log when trying to export data from Dynamics 365

Microsoft.WindowsAzure.Storage.StorageException: The remote name could not be resolved: 'Virtualmachineinstance.table.core.windows.net' ---> System.Net.WebException: The remote name could not be resolved: 'Virtualmachineinstance.table.core.windows.net'



Root cause : Microsoft Azure storage emulator is not running

Solution :  

Navigate to C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator

Right click on AzureStorageEmulator and Run as Administrator


or you can also run from command prompt







Comments

  1. Anonymous19 May 2021 at 01:34

    Brilliant. Thank you

    ReplyDelete
  2. Clay Spenser10 January 2022 at 22:32

    Thank you for sharing such a useful article. I had a great time. This article was fantastic to read. Continue to publish more articles on

    Data Engineering Services

    ReplyDelete

Post a Comment

Popular posts from this blog

AX 2012 DEVOPS Build, Release setup and configuration

-
Image
After the initial setup in  AX 2012 Build process using AZURE DEVOPS Next step is to setup the build template and run the build process to get model and modelstore file which can be deployed to any environments. Goto your AZURE - DEVOPS dashboard by login to  https://visualstudio.microsoft.com/vso/ If you dont have a account, you can register for one free. Azure DEVOPS dashboard Select project for build process setup Select builds Click new pipeline Select Team foundation version control or the one you setup in intial step to move code to azure repo Select build reporsitory It should be the one you selected in initial setup steps Here select TFVC reporsitory Server path is the branch for which you want the build run Local path under - sourcesdirectory click continue for next step Select a build template - empty pipeline and add the build steps as per the AX build process order Now at the final step of build pipeline creation If you haven&
Read more

What is Microsoft Power Platform?

-
Image
In today's world, data is growing immensley and its very important for any individual, organisation or a service to run successfully. With control of data, we can make better decisions and provide great value. Control of data, is crucial not only to an organization’s growth, but also to prevent losses. Microsoft powerplatform  empowers everyday users with the ability to create apps, visualisations and workflows to help them and their colleagues achieve more. You can leverage data by automating common business tasks, building reports, creating workflows and connect apps. Power Platform is comprised of four key products: Power Apps, Power Automate, Power BI and Power Virtual Agents. Power Platform has been designed to be simple to use, even for those with limited technical expertise, to lower the technical threshold and put the power into users hands. This all helps to promote digital transformation as a mind-set throughout an organisation. Gartner recognizes Microsoft as a Magic Qua
Read more

AX 2012 Build process using AZURE DEVOPS

-
Image
Deployment pipeline in AX is always been a challenge. But this has improved a lot over the years with AZURE DEVOPS. This post details how to setup your deployment pipeline using Azure DevOps (Previously VSTS). Using below process, we can build a modelstore for AX 2012 without a local Team foundation server and license cost. Firstly we need a server with windows installed and a working AX environment. Go to  https://visualstudio.microsoft.com/ Click on Azure Devops, enter the required details, select Team foundation version control and create a project. Goto Repos and create a new folder to store the code belongs to your custom model To add code to azure repo, go to AX and enable the version control parameters and check in the model to move all the custom code to Azure. Now under version control tab select Add model to version control, select the correct model and repository folder and click Ok  to move all the custom model objects to Azure r
Read more