Configuring Office 365 PowerShell Throttling causes a 'Failed to retrieve configuration' error.
説明
After configuring the SQL Server, Shared Directories, Notes Server and Active Directory sections in Migrator for Notes to Exchange (MFNE); the Exchange Server section was the configured. The Exchange Server section was setup using Office 365, entered the correct Exchange credentials and Tenant settings. Clicked on Apply to save these settings and MFNE mentioned that the last section had not been entered yet i.e. Office 365 PowerShell Throttling configuration had not been set. By clicking on the Configure button, this launched the Office 365 PowerShell Throttling window and could see it initializing at the bottom of that window. After a short while, the following PowerShell Throttle Settings pop-up message appeared:
Failed to retrieve configuration. Check database settings. See Migration Console log for more error details.
The verbose MFNE log file unfortunately didn't capture anything relating to this issue. From the ThrottleManager.log file, we could confirm the following error message at the same time of the above error message:
11:03:03 ERROR: Failed to initialize NME API. System.Data.EntityException: The underlying provider failed on ConnectionString. ---> System.ArgumentException: The value's length for key 'password' exceeds it's limit of '128'.
The SA password for the SQL section of MFNE used an SQL user password that only contained upper case and lower case characters, as well as numbers. The password length was only eight characters as well, so there should not be an issue.
対策
The issue was resolved by instead of using SQL authentication details, to use Windows Authentication instead. Make sure that the Bulk Import Directory section under the SQL Server section in MFNE also has the same permissions as that Windows Authentication user.
Also make sure when setting up the rest of the MFNE sections, that all prerequisites and supported Operating Systems, Domino and Exchange Servers are also supported as in Chapter 1 and check Chapter 2 for critical considerations of the Preplanning Guide have also been met:
This also includes the AntiVirus setup i.e. prior to running any MNE admin application: any AntiVirus software must be configured to not scan the MNE program files directory or %temp% directory, or may be simply turned off, but may be restored after the program runs. If an AntiVirus scan misinterprets an MNE temporary file as a threat, it will try to "clean" the file, which will generate an error when the MNE program call fails.
