Forum Discussion
DataSource.Error: ERROR [08S01] [Microsoft][Netezza] (1001) Communication link with server failed.
When trying to connect to some tables in a Netezza Data Warehouse I get the following error:
DataSource.Error: ERROR [08S01] [Microsoft][Netezza] (1001) Communication link with server failed.
This doesn't happen with all the tables just a couple. I'm using the Jan. version of Desktop. Version: 2.54.4970.761 64-bit (January, 2018) Any thoughts on what may be the issue? Let me know if I need to provide more details. Thanks in advance for your help.
6 Replies
Hi 4Eric,
After research, an error may occur when the communication link between the driver and the data source to which the driver was connected failed before the function completed processing. Without using Power BI, if you can connect the Netezza Data Warehouse correctly? Work with network and Database administrators to see if there were any system problems during the database action.
Best Regards,
AngeliaI have spoken to our DBA and there was no issues. I can click this one table to try and bring it into Power BI and I get this error. I can then immediately select a different table and it will work just fine. Could there be a size limit thing going on or is the size of the table taking to long to load and causing this error. This issue will happen whether I select import or direct query. Last question would it help to update Power BI drivers, if so where can I find them?
Hi we are connecting to our Netezza data source using the Power BI inbuilt IBM Netezza connector and get the same issue.
Some entities are fine, however 1 or 2 do this in the Power Query editor as illustrated.
No rhyme nor reason. I have not found any other posts or a solution. Anyone found anything outr since these last posts please?
We face the exact same issue. Seemingly random, which of cource is frustrating. Some tables just does not work. They produce "ERROR [08S01] ... ". Also talked with our DBA's, they can't find any apparent differences between table that work and do not. Same database and schema.
Obviously this is an old issue but the problem persists using the "2.97.861.0 64-bit (september 2021)" release of Power BI.
Please note that the problematic tables work fine when using the generic ODBC connector toghether with an IBM supplied ODBC driver. This workaround works but also suggests that there should not be an issue with the built in driver.
I would appriciate if Microsoft points this out to Magnitude/Simba that assume supplies the built in ODBC driver.
Thanks!In PowerBI Desktop, click "File->Options and settings->Data source settings”, next double click on the "IBM Netezza" in the list, choose “Edit Permissions..”
uncheck the encryption connection and setting the privacy level as "None".
Click “OK” button, it worked 😊
