-
-
Notifications
You must be signed in to change notification settings - Fork 13
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.
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
Error in TypeData "Microsoft.Azure.Commands.Common.Authentication.Abstractions.IAzureContextContainer": The TypeConverter was ignored because it already occurs. #7
Comments
Looks indeed to me like an issue with AzureRM. Have had more issues in the past and for some reason the VS2017 hosted agents still uses v2.1.0 as the default: https://github.com/Microsoft/vsts-image-generation/blob/master/images/win/Vs2017-Server2016-Readme.md#azureazurerm-powershell-modules |
I am getting the same error when deploying in Azure: 2018-08-03T19:42:25.6468821Z ##[command]Import-Module -Name C:\Program Files\WindowsPowerShell\Modules\AzureRM\6.5.0\AzureRM.psd1 -Global |
Are you using an on-prem agent? Or a hosted environment? |
Hosted |
Have you had a chance to look into this? |
Yes, but I cannot reproduce this error. Do you have the error also if you are using a Hosted 2017 environment? |
I believe that it is a 2017 environment. I added some inline powershell comands and here are the results. 2018-08-06T17:32:40.6923183Z ##[section]Starting: Azure PowerShell script: InlineScript |
For these tasks you don't have to install/update the So you can try running the tasks with the inline powershell script disabled. |
You mean my inline powershell script? It will give the same error that I posted 3 days ago. |
You can right click the Azure Powershell task and select |
Here is the output of the task: 2018-08-06T20:33:28.5738274Z ##[section]Starting: Deploy JSON files to alpha-rtrainer-df 2018-08-06T20:33:34.5405927Z ##[section]Finishing: Deploy JSON files to alpha-rtrainer-df |
When I look at my releases the it starts with the statement |
Better. Here is the latest output: 2018-08-06T20:59:28.1081501Z ##[section]Starting: Deploy JSON files to alpha-rtrainer-df |
Looks to me like you have some configuration errors. To get some more insights you can add the variable |
Thank you. I was just looking to see if maybe it was an error on my side. |
Sorry for more noob questions but it is failing at a different place. 2018-08-06T21:27:05.0211090Z ##[debug]Error deploying 'brtBuzzStaging.json' (Json is not valid. Details: 'Newtonsoft.Json.JsonReaderException: Error reading JObject from JsonReader. Current JsonReader item is not an object: String. Path '', line 7, position 182. I have tried this using the cli with the same results. The JSON was successfully run through a JSON validator. |
Any ideas on the previous error? |
I have updated the extension to include previews of the V2 version of different tasks and feel free to test if these are working for you. |
I am facing the exact same error as rtrainer. I also checked the input JSON in the JSON validator and it was successfully validated. |
Can you try the V2 version of the extension? |
I'm also getting the same error, while deployment. I'm not using a Hosted agent, but an on prem one. The powershell and RM versions are also different in both cases:
i'm not exactly sure, whats missing. As there are no multiple versions of AzureRM in on-prem agent. Did anyone figured out the reason behind this behavior? Thanks |
I'm having this same issue. On prem. AzureRM version 6.13.1. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
We're trying to use the Azure Data Factory Deployment task from our on-premises agent, and we receive the following error: ADFOnPremisesError.txt
When we run the same step on the Hosted VS2017 agent, and it works successfully. Here's the output:
ADFHosted2017.txt
One thing we noticed is that on-premises is running Import-Module -Name C:\Program Files\WindowsPowerShell\Modules\AzureRM\5.7.0\AzureRM.psd1 -Global
...and hosted 2017 is running Import-Module -Name C:\Program Files\WindowsPowerShell\Modules\AzureRM*2.1.0*\AzureRM.psd1 -Global
Could the newer version of AzureRM be incompatible?
We've looked at the version of AzureRM that we have installed on our on-prem agent following the guidance here, https://github.com/Azure/azure-powershell/blob/preview/documentation/troubleshoot-module-load.md#potential-reason-1-older-version-stored-in-user-or-global-scope, and we do not have multiple versions on our on-prem agent.
We're able to use our hand-rolled PowerShell scripts to do the deploy, however we like your VSTS extension and would like to switch to it. Our current policy says that we must use the on-prem agent.
Can you think of what may be causing this? Any help is very much appreciated.
Thanks
The text was updated successfully, but these errors were encountered: