The following error occurs with Power BI when you try to import or query data using a SAS ODBC Driver via SAS/SHARE: 

“(The container unexpectedly ended up with the code 0xC0000374 PID: 19440. Features used: Odbc.DataSource/SASDRV32.DLL//09.04.0000/SAS/…)”

Note that this issue is not isolated to Power BI. The issue also occurs with Microsoft Excel, which indicates that the issue is a Microsoft toolchain ODBC consumer issue rather than a SAS ODBC Driver functional defect.

Workaround

No SAS hot fix is planned for SAS^® 9.4M7 (TS1M7), SAS^® 9.4M8 (TS1M8), or SAS^® 9.4M9 (TS1M9) for this issue, as the issue is treated as external to SAS.

Instead, you should complete one of the following workarounds and open a support case with Microsoft. 

Method 1: Use an Alternative Connector

Instead of using the SAS ODBC driver from Power BI, use an OLE DB approach, as described in the following SAS Communities post: Solved: Reading SAS data sets in Power BI.

This workaround is suitable when you meet the following conditions:

• You want direct connectivity without staging data to intermediate files or databases.
• Your organization already supports OLE DB providers and governance.

Method 2: Export SAS Data to CSV and Then Import CSV into Power BI

Export the SAS tables to CSV and then load those files into Power BI.

This workaround is suitable when you meet the following conditions:

• The data volumes are manageable for file-based interchange.
• You need a quick workaround with minimal changes.

Method 3: Load SAS Tables into a Database so that Power BI Can Read the Tables Consistently

Use SAS/ACCESS^® (that is, SAS/ACCESS^® Interface to ODBC or SAS/ACCESS^® Interface to Microsoft SQL Server) to load SAS tables into the Microsoft SQL Server database. Then, connect Power BI to the database instead of using an ODBC Driver via SAS/SHARE.

This workaround is suitable when you meet the following conditions:

• You have enterprise reporting scenarios with frequent refreshes.
• You prefer governed, scalable storage and robust Power BI connectors.

Method 4: Use a Third-Party Tool

A third-party integration layer (for example, R, CData, and so on), reads SAS data and exposes the SAS data in a way that Power BI consumes more reliably: Solved: SAS Connection to Power BI.

This workaround is suitable when you meet the following conditions:

• You already use one of those tools in your data integration stack.
• You need flexibility beyond the SAS ODBC Driver via SAS/SHARE.

Open a Support Case with Microsoft

To open a support case with Microsoft, collect the following data:

• the Power BI error, including the following:
  • exit code 0xC0000374
  • driver module (SASDRV32.DLL) and the version string
• the Windows Event Viewer application logs around the crash time
• ODBC configuration details
  • DSN
  • 32-bit versus 64-bit driver usage
• SAS Server connectivity details
  • local SAS session versus SAS/SHARE
  • SAS release and maintenance level
• steps to reproduce
  • the involved data set
  • Power BI query
• comparison test
  • Attempt the same DSN from another Microsoft tool (for example, Microsoft Excel) to determine whether the issue occurs outside of Power BI.