Hey RIchard Wardrobe,
It sounds like you're encountering a frustrating issue with your Purview Data Map scan of your on-prem MySQL database. The error message you received, stating that "the given key was not present in the dictionary," suggests that there's a problem with the expected data structure during the scan process.
Here are a few things you can try to resolve this:
- Check Configuration: Ensure that the configuration of the self-hosted integration runtime (SHIR) is correct. Make sure that the SHIR is set up and is properly communicating with your database and the Purview service.
- Authentication: Since MySQL supports Basic Authentication, double-check that the username and password in the credentials used for the scan are correct. Ensure that the credentials you provided have sufficient permissions to access the databases you're trying to scan.
- Update SHIR: Since you're running version 5.51.93651.1 of the SHIR, verify if there's a newer version available. Occasionally, odd issues can be resolved simply by updating to the latest version of the software. You can download the latest version from the Download Center.
- Memory Settings: Make sure that the maximum memory available on your machine for the SHIR is sufficient. It's recommended to have about 1GB of memory for every 1000 tables in the MySQL database.
- Log Examination: While you mentioned you've uploaded logs to Microsoft, if possible, look for any additional error details leading up to the specific error in your environment logs. Specific warnings or messages prior to the error might provide additional context.
- Private Endpoint Configuration: If you are using private endpoints, confirm that network settings and firewall rules permit the necessary access. This includes ensuring that your SHIR can communicate effectively with both the Purview service and your MySQL instance.
- Consult Microsoft Documentation: Given that you followed the documentation at https://dori-uw-1.kuma-moon.com/en-us/purview/register-scan-mysql, make sure to revisit the prerequisites and steps to verify there aren’t any overlooked configurations.
Follow-Up Questions:
To assist you better, could you provide more details on:
- Have there been any recent changes to your network configuration or database permissions that might impact the scan?
- Are only specific tables in your MySQL database causing the issue, or is this happening with all of them?
- Can you confirm if the SHIR service account has the necessary permissions to access your databases?
- Have you run any diagnostic tests from the Purview interface to check connectivity or configuration issues?
I hope this helps you get closer to a resolution! Good luck, and let me know if you have any other questions!
Reference Documentation:
- Connect to and manage MySQL in Microsoft Purview
- Self-hosted integration runtime troubleshooting
- Download the SHIR
- Scan errors related to SQL DB
Feel free to reach out if you have more questions!