"Internal system error" when scanning Snowflake in Purview

Question

Hello,

I've set up a scan for Snowflake database in Purview following the steps . The scan fails when I run it, though, with the following error message:

Internal system error. Please contact support with correlationId:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx System Error, contact support: (119) System error while attempting to launch datascan process. ActivityId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx )

I'm not sure what is causing this error, and what needs to be done to resolve it. Could you provide some guidance, please?

Additional notes:

• I've verified that all the prerequisites were met
• I've deleted and re-created the scan, but still receive the same error message

Answer 1

Hi @Arjun Rajagopal

Thanks for the question and using MS Q&A platform.

The issue has been mitigated. I received an update from my internal team indicating that if we rerun the scans, they should run successfully. If they do not, please let me know.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Hello,

I've encountered the issue again. Until now, I was able to scan my Snowflake sources, but starting today, I'm getting the "Internal system error" message. Do you have any solution for this?

Answer 3

Hello,

The error is a regression on purview side when interrogating snowflake (as seen on 2024-10-22 in France central deployment).

Purview sends the following request to azure :

show /* JDBC:DatabaseMetaData.getPrimaryKeys() */ primary keys in table "EAF"."DWH"."%"

which is wrongly formated due to the incorrect wildchar

Correct query is

show /* JDBC:DatabaseMetaData.getPrimaryKeys() / primary keys in table "EAF"."DWH".""

Snowflake replies with a correct error message.

"Table 'EAF.DWH."%"' does not exist or not authorized."

This error is not managed on purview side and tirggers an "internal error".

This is a recent behaviour, it worked previously (on 2024-09-24).

This has to be mitigated on microsoft purview side. Please get back to me when correction is released

best regards

Jerome