Skip to content
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

Start Method not found but Stop works just fine #7389

Closed
Garandorf opened this issue Apr 18, 2018 — with docs.microsoft.com · 9 comments
Closed

Start Method not found but Stop works just fine #7389

Garandorf opened this issue Apr 18, 2018 — with docs.microsoft.com · 9 comments

Comments

Copy link

I've followed through with the runbook tutorial and I can get the IR to stop but not start for some reason. I keep getting the "Module not found error" . The code is exactly the same except for the Start/ Stop module. I've checked and the method exists or at least it appears on the list under the module.
This is the error I get:

Start-AzureRmDataFactoryV2IntegrationRuntime : Method not found: 'Newtonsoft.Json.Serialization.IAttributeProvider
Newtonsoft.Json.Serialization.JsonProperty.get_AttributeProvider()'.
At line:43 char:5

  • Start-AzureRmDataFactoryV2IntegrationRuntime -DataFactoryName $Da ...
    
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : CloseError: (:) [Start-AzureRmDa...egrationRuntime], MissingMethodException
    • FullyQualifiedErrorId : Microsoft.Azure.Commands.DataFactoryV2.StartAzureDataFactoryIntegrationRuntimeCommand

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@Mike-Ubezzi-MSFT
Copy link
Contributor

@Garandorf Thanks for the feedback. We are actively investigating and will get back to you soon.

@pejuan
Copy link

pejuan commented Apr 25, 2018

I get the same error. I'm trying to automate the Start and Stop of an Integration Runtime connection. However, I get the error with the Stop command as well.

@jason-j-MSFT
Copy link
Contributor

@douglaslMS the documented procedure to create a scheduled stop operation for Azure SSIS IR may not be working. I noticed the versions of the 'AzureRM.Profile' and 'AzureRM.profile' modules in Automation are more advanced if you import/update them today, rather than the version at the time document was created:

capture12
capture13

It's possible this problem was introduced with the module updates after this document was created.

@Garandorf and @pejuan could you confirm what module versions you are on?

@jason-j-MSFT
Copy link
Contributor

Oops I said stop is having an issue, but it is the start operation.

@jason-j-MSFT
Copy link
Contributor

The full Powershell line causing the exception is:

Start-AzureRmDataFactoryV2IntegrationRuntime -ResourceGroupName $ResourceGroupName -DataFactoryName $DataFactoryName -Name $AzureSSISName -Force

@pejuan
Copy link

pejuan commented Apr 30, 2018

I checked @jason-j-MSFT
image

My versions are the same you mention may have errors.

@douglaslMS
Copy link
Contributor

@jason-j-MSFT @Garandorf @pejuan This is a known issue, and the team is working on a fix. In the meantime, at present, you can only use AzureRM.DataFactoryV2 0.5.2 and AzureRM.Profile 4.5.0 modules. I have updated the document and I'm waiting for the updated page to be published. (I was going to update this issue later this afternoon after the updated page goes live.)

@jason-j-MSFT
Copy link
Contributor

@douglaslMS thanks for the update!
@Garandorf @pejuan we are closing this issue for now, but feel free to add comments as needed.

@douglaslMS
Copy link
Contributor

@Garandorf @pejuan We have revised the "Import modules" section under here: Create and test an Azure Automation runbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants