Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I'm trying to establish a connection from Power BI to Starburst, but I'm encountering the error: There were not enough elements in the enumeration to complete this operation.While configuring the connection, I provided the host, port, and timezone details, and I’m using the Import method to load the data.
Solved! Go to Solution.
Hi @akhil1218 ,
It looks like your ODBC driver is an older version that's why you're only seeing TimeZoneID and not SessionTimeZone. The older driver doesn't support the new timezone parameter, and that’s exactly what causes both the timezone error and the - not enough elements in the enumeration issue in Power BI.
If you uninstall your current driver and install the latest Starburst ODBC version (v3.01.02 or above), you'll see the SessionTimeZone option. After updating your DSN or connection string with something like SessionTimeZone=UTC, the connection should start working normally.
Hi, I’m using Power BI version 2.148 and driver version 3.01.02. When connecting to Starburst, I’m providing the host, port, username, and password, but I’m getting a ‘failed to locate timezone’ error. If I add TimeZoneID=Pacific/Midway; to the connection string, then i'm getting the ‘not enough elements in the enumeration’ error.
Hi @akhil1218 ,
With Starburst ODBC driver v3.01.02+, the errors you’re encountering are expected if the timezone isn’t specified or if the older 'TimeZoneID' parameter is used, since this parameter is no longer supported. The driver now requires - SessionTimeZone to be set. You can update your connection string or DSN to include a valid IANA timezone, for example, SessionTimeZone=UTC or SessionTimeZone=America/Los_Angeles. Making this change should resolve both the Failed to locate timezone and Not enough elements in the enumeration errors.
Nope, it’s still the same. Also, I don’t see the SessionTimeZone parameter, we only have TimeZoneID.
Hi @akhil1218 ,
It looks like your ODBC driver is an older version that's why you're only seeing TimeZoneID and not SessionTimeZone. The older driver doesn't support the new timezone parameter, and that’s exactly what causes both the timezone error and the - not enough elements in the enumeration issue in Power BI.
If you uninstall your current driver and install the latest Starburst ODBC version (v3.01.02 or above), you'll see the SessionTimeZone option. After updating your DSN or connection string with something like SessionTimeZone=UTC, the connection should start working normally.
Hi @akhil1218 ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
Hi @akhil1218 ,
Thanks for sharing the details. The error “There were not enough elements in the enumeration to complete this operation” usually indicates that Power BI didn’t receive all the required connection details from the Starburst connector.
Please try the following steps to resolve this -
Update Power BI Desktop - Make sure you’re using the latest version (Oct 2023 or later is recommended). Install/Update Starburst ODBC Driver - Use the latest Starburst ODBC driver (v2.0.15.1021 or newer). Verify Connection Fields, When connecting from Power BI - Get Data - Starburst, ensure the Host, Port, and Catalog fields are correctly entered. Authentication Mode, If your environment uses Microsoft Entra ID (formerly Azure AD), select Starburst secured by Entra ID instead of the regular connector. If you’re using a connection string, double check it for missing or unsupported parameters. Try DirectQuery, If Import mode continues to fail, test with DirectQuery to confirm the connector works end to end.
Best regards,
Sreeteja
Hi @akhil1218 ,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Hi @akhil1218
That error usually means the connector isn’t getting the full set of connection details it expects, with Starburst, it often happens if the ODBC driver version is outdated or if the connection string is missing required parameters.
I suggest updating to the latest Power BI build and Starburst ODBC driver, and double‑checking the connection string fields, typically resolves it
Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!