Why is my data catalog import failing?

Question

Hello,
I am trying to use the Azure Data Catalog import tool to import postgresql source system metadata into my data catalog. I have had lots of trouble and the latest issue is just failures with no error reporting. I reduced the request to a single table for simplicity. Attached is the failure screenshot and the error reporting output corresponding to the action.

I found a thread in a forum from 5 years ago asking for help. It had the location of the error logging. Which i will put here for the next poor soul that needs help with this tool.

"Error Logging is located at %appdata%\AzureDataCatalogErrorEventLogProd.log file on the PC where you ran the registration tool. This will include the details of the last execution, including any errors. "

Can anyone help me understand why I can’t import this data? The logs don't show me anything glaring, personally. Pls help.

Answer 1

The screenshot is the same no matter what I set as the command timeout(I have not been setting it, typically). The screenshot is the same no matter what table or view i try to bring in. The failure occurs in less the 3 seconds for one table.

There is no error handling. It doesnt show me what has happened at all. I found Timeout in the log by doing a text search. It looks like a method inside the tool is timing out, but maybe thats just ambiguous.

The error is consistent. I found a similar timeout this morning running the same request:

{"PreciseTimeStamp":"2021-05-18T14:23:56.5342424Z","EventName":"FailedExtraction","EventId":1,"ActivityId":"332a5ef6-7f1d-4b9e-9e76-2f0cd520c217","RelatedActivityId":"00000000-0000-0000-0000-000000000000","Payload":["Microsoft.PostgreSql","1.0","Microsoft.Data.Mashup.InternalMashupException","We're sorry, an error f13a83c8f3b5","Settings":4,"ConstructionException":null},"Keywords":263882790666240,"Opcode":0,"Task":65533,"Tags":0,"Message":"FailedExtraction","Channel":0,"Version":3,"Level":2,"SessionId":"11922815-7718-4332-bb5f-a9ebca941e1e"}

Answer 2

A ticket was created with Microsoft, and I wanted to share with the community the response:

Based on the recent log file, I was able to locate the code that was causing the issue and reached out to product team for help. They responded that the underlying code which is causing the issue is old and out of support and Data catalog is not planning to update it as the product itself is in Sustaining mode (soon to be deprecated). Hence it would not be possible to fix the issue for you.
They suggested to try the new Azure Purview in order to connect and gather Postgre metadata.

For those who are experiencing this same Postgres metadata import issue, you're out of luck. Azure Data Catalog is no longer supported. You'll need to work around it, or look at other services such as Purview.