Windows Azure–Object reference not set to an Instance

I was doing R&D using Windows Azure PowerShell. I used Azure one month Trail account because of heavy usage, the amount $200 has totally out, normally for free account we will get $200 amount of usage for one month. It was not sufficient for me so i created one more trail account.
Scenario: I was worked on HDInsight MapReduce Jobs, i got perfect result while using first trial account. Afterwards, once i created a new account again i pointed the connection to new account and run the same MapReduce jobs but it got failed. I tried many times, spent around 2 to 3 hours for this. The error which i received is “object reference not set to an instance”. Please check the below error screenshot.
Azure_PowerShell
I found that something went wrong while using the second trail account. I just tried to clear the powershell environment but it was not worked then i reinstall the azure power shell again it was helpless.
Finally i checked the powershell, how many accounts pointed with. It has shown two accounts and checked the subscriptions also. Then i removed the old subscription. Now i have one account which is pointed with Azure power shell.
Codes used in PowerShell
-----Check the Available Accounts
> Get-AzureAccount
>Get-AzureSubscription
----Remove the unwanted accounts
>Remove-AzureSubscription
I got it, Now my MapReduce jobs are working.

Comments

Popular posts from this blog

SQL Server–Alter failed for Server

Generate Data Time Dimension Table in SAP HANA

Access HANA view in SQL Console