Reply
Member
Posts: 69
Registered: ‎02-13-2018
Accepted Solution

April release broke certain DB2 connections: SQLSTATE HY000 SQLCODE =-379

[ Edited ]

Yesterday I updated my PBI Desktop to the April release. Then I started getting errors with my IBM DB2 connections. These erros only appear to occur in desktop. and have not affected the version in Service.

Here is the error message from Edit Queries:

 

DataSource.Error: Microsoft Db2 Client: An internal network library error has occurred. A network level syntax error has occurred. SQLSTATE=HY000 SQLCODE=-379
Details:
    DataSourceKind=DB2
    DataSourcePath=[Server];[DB]
    Message=An internal network library error has occurred. A network level syntax error has occurred. SQLSTATE=HY000 SQLCODE=-379
    ErrorCode=0


Accepted Solutions
Highlighted
Member
Posts: 69
Registered: ‎02-13-2018

Re: April release broke certain DB2 connections: SQLSTATE HY000 SQLCODE =-379

You go to "Edit Queries" and select the "Data source settings" button on the toolbard. From there, select your data source type, and edit its credentials.

scrnsht.PNG

View solution in original post


All Replies
Community Support Team
Posts: 6,614
Registered: ‎05-02-2017

Re: April release broke certain DB2 connections: SQLSTATE HY000 SQLCODE =-379

Hi @jengwt,

 

I would suggest you file a support ticket here.

create ATicket

 

Best Regards,

Dale

Member
Posts: 69
Registered: ‎02-13-2018

Re: April release broke certain DB2 connections: SQLSTATE HY000 SQLCODE =-379

Turns out that what PBI remembered as my creds for the DB2 connection got scrambled, and I was just having a very hard time trying to get it to use the right set.

@v-jiascu-msft How can I force the "login" window for a query to appear? It only seems like it will show up in certain situations, which I can't seem to define. I'm sure there's just some button I'm missing.

 

There were other things that happened, like certain slicers ceasing to work. I had to finagle them a little bit to get them to start working again, but ultimately, I didn't actually changed anything to get them working again. It could have been the appearance of what we have taken to calling "ghost slicers".

 

I am very confident that these issues were caused by the new release; updates in the software that made the existing content of my reports freak out.

Highlighted
Member
Posts: 69
Registered: ‎02-13-2018

Re: April release broke certain DB2 connections: SQLSTATE HY000 SQLCODE =-379

You go to "Edit Queries" and select the "Data source settings" button on the toolbard. From there, select your data source type, and edit its credentials.

scrnsht.PNG