Share via

Error: MigrationProvisioningPermanentException: Method not found

Anonymous
2023-03-04T19:55:27+00:00

Hello,

I am currently doing a cutover migration from exchange 2013 to Office 365.

I created the migrationendpoint and checked the Migrationstatus by using: Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress <E-Mail Adress> -Credentials $Credentials

and received:

Result : Success

Message :

SupportsCutover : True

ErrorDetail :

TestedEndpoint : <endpoint>

IsValid : True

Identity :

ObjectState : New

Unfortunately, a few minutes after starting the batch i receive the following error:

Migrierte Daten:

Migrationsrate:

Fehler: MigrationProvisioningPermanentException: Method not found: 'Microsoft.Exchange.Collections.ReadOnlyCollection`1 <Microsoft.Exchange.Data.PropertyDefinition> Microsoft.Exchange.Data.ObjectSchema.get_AllProperties()'. -->

It counts the correct number of mailboxes that should be migrated but seems to not even start somehow.

Is there a chance to find a solution for this issue?

Thanks in advance,

Chris

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

15 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-03-21T12:40:37+00:00

    It seems to be working for me also for the most part. Over the weekend (March 18th / 19th) it was still failing if I tried to resume the entire batch. When I resumed the migration users individually they started to provision and sync. I wrote this script to help automate the whole thing:

    Measure-Command{ 

    $BatchIDs = Get-MigrationBatch | Where-Object {$\_.FailedCount -ge 1 } | Select-Object Identity, Status, BatchGuid 

    foreach($batch in $BatchIDs){ 

        Get-MigrationUser -BatchId $batch.Identity | Where-Object { $\_.Status -eq 'Failed' } | ForEach-Object { Start-MigrationUser -Identity $\_.Identity -Confirm:$false} 

    }

    }

    This got all my batches syncing. I still need to go in and resume the migration users that I stopped manually when I was experiencing this issue but thankfully they're syncing as normal.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-03-17T15:37:38+00:00

    Same here also. let me if you find anything regarding this

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-17T12:30:11+00:00

    I am having the same issue.

    SSL in place and valid

    Endpoint is working fine.

    Pulls through accounts to be migrated, the status stays on 'Provisioning' for about 20 minutes, then get the same error as CGERmn.

    No accounts get created.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-16T22:04:50+00:00

    Have you find any solution for the Problem

    Was this answer helpful?

    0 comments
  5. NoOneCan 7,795 Reputation points Volunteer Moderator
    2023-03-05T06:13:42+00:00

    Was this answer helpful?

    0 comments