Forum Discussion
ODBC: ERROR [08001] [IBM][CLI Driver] SQL1309N
I have an issue triying to refresh my Power BI dashboards in the report server.
When I try to refresh them, the following error appears:
ODBC: ERROR [08001] [IBM][CLI Driver] SQL1309N El nombre principal del servidor no es válido. SQLSTATE=08001
Hi ricardo0394 ,
Thank you for reaching out to Microsoft community.You're encountering an error when Power BI Report Server attempts to refresh a dataset connected to an IBM DB2 database via ODBC. The error message "SQL1309N The server principal name is not valid" typically indicates a mismatch between the hostname used in your ODBC connection string and the hostname, common name or subject alternative name defined in the DB2 server's SSL certificate. This is a common issue when SSL is enabled and the driver is attempting to validate the server’s identity as part of the secure connection process.
To resolve this, first ensure that the hostname specified in your connection string exactly matches the hostname defined in the DB2 server's SSL certificate. If you're using an alias, IP address, or a shortened name that does not match the certificate's details, the connection will fail. If matching the certificate is not feasible in your environment, and if it's considered safe by your internal policies, you can bypass this validation by adding ValidateServerCertificate=NO to your ODBC connection string. This disables hostname validation, which is acceptable in some internal environments but should be reviewed by your security team before use in production.
Additionally, make sure your setup includes a properly configured System DSN in the ODBC Administrator. Power BI Report Server uses the gateway to access data sources, so you need to register the same DSN (with the full and correct connection string) in both the gateway and Power BI Desktop to ensure consistency. Any discrepancy between these can result in refresh failures.
Also, confirm that you're using the latest IBM Data Server Client or DB2 ODBC driver. Outdated drivers may not fully support modern SSL configurations or hostname validation mechanisms. Keeping the driver up to date ensures better compatibility and may resolve connection issues without needing to modify security settings.
By aligning the hostname, SSL settings, DSN configuration, and driver version, you can eliminate the principal server name error and ensure smooth refresh operations in Power BI Report Server.
Hopes this helps.
Best Regards,
Chaithra E.
4 Replies
Hi ricardo0394 ,
Thank you for reaching out to Microsoft community.You're encountering an error when Power BI Report Server attempts to refresh a dataset connected to an IBM DB2 database via ODBC. The error message "SQL1309N The server principal name is not valid" typically indicates a mismatch between the hostname used in your ODBC connection string and the hostname, common name or subject alternative name defined in the DB2 server's SSL certificate. This is a common issue when SSL is enabled and the driver is attempting to validate the server’s identity as part of the secure connection process.
To resolve this, first ensure that the hostname specified in your connection string exactly matches the hostname defined in the DB2 server's SSL certificate. If you're using an alias, IP address, or a shortened name that does not match the certificate's details, the connection will fail. If matching the certificate is not feasible in your environment, and if it's considered safe by your internal policies, you can bypass this validation by adding ValidateServerCertificate=NO to your ODBC connection string. This disables hostname validation, which is acceptable in some internal environments but should be reviewed by your security team before use in production.
Additionally, make sure your setup includes a properly configured System DSN in the ODBC Administrator. Power BI Report Server uses the gateway to access data sources, so you need to register the same DSN (with the full and correct connection string) in both the gateway and Power BI Desktop to ensure consistency. Any discrepancy between these can result in refresh failures.
Also, confirm that you're using the latest IBM Data Server Client or DB2 ODBC driver. Outdated drivers may not fully support modern SSL configurations or hostname validation mechanisms. Keeping the driver up to date ensures better compatibility and may resolve connection issues without needing to modify security settings.
By aligning the hostname, SSL settings, DSN configuration, and driver version, you can eliminate the principal server name error and ensure smooth refresh operations in Power BI Report Server.
Hopes this helps.
Best Regards,
Chaithra E.Hi ricardo0394 ,
We would like to confirm if you've successfully resolved this issue or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Chaithra EHi ricardo0394 ,
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Chaithra E.Hi ricardo0394 ,
We wanted to follow up to see if the issue you reported has been fully resolved. If you still have any concerns or need additional support, please don’t hesitate to let us know, we’re here to help.
We truly appreciate your patience and look forward to assisting you further if needed.
Warm regards,
Chaithra E.