Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

Reply
fegat79
Regular Visitor

OLE DB or ODBC error: The container unexpectedly closed with code 0xC0000374.

Hi guys,

I need help with the report that connects to a firebird base by ODBC.

===========================================================

OLE DB or ODBC error: The container unexpectedly closed with code 0xC0000374. PID: 6980.
Resources used: Odbc.DataSource / OdbcFb / 02.00.0156 / Firebird / 06.03.27139 WI-V Firebird 2.5.

===========================================================

 

The connection to the database is OK. I have already tested the x32 and x64 versions (PBI, firebird and ODBC driver) and both give the same error. It can read most of the base tables but has an error in 2. And the base is not corrupted.
Can someone help me please?!
The solutions I found on the intrnet did not apply to me: erase PowerBI cache, install firebird DLL, update firebird and ODBC driver.
I use windows 10 64bit and tested with Powerbi x64 and x32 all give the same error.
PS .: sorry for the writing, I used Google Translate

 

Thanks,

Fernando Alves

 

4 REPLIES 4
fegat79
Regular Visitor

Hello Guys,

 

I solved the problem of my report connected to the firebird database via ODBC ... for some reason, I still don't know which one, powerBI can't read a certain column in 02 tables of the database. I found out by importing column by column until I got the error. So I removed the column by Query and restored the full report. Fortunately, I don't need that column for the report, but I still need to understand why it gives an error.

 

By: Google Translator

 

Thanks

fegat79
Regular Visitor

I did the installation on two other PCs and it gives the same error. Is anyone else having difficulty with recent installations of windows 10 64 and PBI with firebird connection?

vanessafvg
Super User
Super User

have you enabled tracing and looked at what the diagnostics are saying?





If I took the time to answer your question and I came up with a solution, please mark my post as a solution and /or give kudos freely for the effort 🙂 Thank you!

Proud to be a Super User!




Hi Vanessa,
I hadn't enabled it but I did and copied the log below:

========================================
(16/12/2020 16:15:50) Message: O pool de threads Query agora tem o mínimo de 16 threads, o máximo de 16 threads e uma simultaneidade de 16. Sua máscara de afinidade de pool de threads é 0x00000000000000ff. (Type: 1, Category: 289, Event ID: 0x4121000A)
(16/12/2020 16:15:50) Message: O pool de threads Command agora tem o mínimo de 1 threads, o máximo de 16 threads e uma simultaneidade de 16. Sua máscara de afinidade de pool de threads é 0x00000000000000ff. (Type: 1, Category: 289, Event ID: 0x4121000A)
(16/12/2020 16:15:50) Message: O pool de threads Parsing Short agora tem o mínimo de 4 threads, o máximo de 16 threads e uma simultaneidade de 16. Sua máscara de afinidade de pool de threads é 0x00000000000000ff. (Type: 1, Category: 289, Event ID: 0x4121000A)
(16/12/2020 16:15:50) Message: O pool de threads Parsing Long agora tem o mínimo de 4 threads, o máximo de 16 threads e uma simultaneidade de 16. Sua máscara de afinidade de pool de threads é 0x00000000000000ff. (Type: 1, Category: 289, Event ID: 0x4121000A)
(16/12/2020 16:15:50) Message: O pool de threads Processing agora tem o mínimo de 16 threads, o máximo de 64 threads e uma simultaneidade de 16. Sua máscara de afinidade de pool de threads é 0x00000000000000ff. (Type: 1, Category: 289, Event ID: 0x4121000A)
(16/12/2020 16:15:50) Message: O subpool de threads IOProcessing com afinidade 0x00000000000000ff agora tem o mínimo de 1 threads, o máximo de 80 threads e uma simultaneidade de 16. (Type: 1, Category: 289, Event ID: 0x4121000B)
(16/12/2020 16:15:50) Message: O pool de threads Vertipaq agora tem o mínimo de 2 threads, o máximo de 8 threads e uma simultaneidade de -1. Sua máscara de afinidade de pool de threads é 0x00000000000000ff. (Type: 1, Category: 289, Event ID: 0x4121000A)
(16/12/2020 16:15:50) Message: O Agendador usará a fila executável do tipo = NUMA_AWARE (motivo: fallback to default configurações). (Type: 1, Category: 289, Event ID: 0x41210032)
(16/12/2020 16:15:50) Message: O Agendador usa a política Habilitada para NUMA. Nós = 1, Grupos = 1, CPUs = 1, Cores = 8. (Type: 1, Category: 289, Event ID: 0x41210033)
(16/12/2020 16:15:50) Message: DLL 'Microsoft.AnalysisServices.MInterop' carregada com a versão '15.1.63.25'. (Type: 1, Category: 289, Event ID: 0x41210038)
(16/12/2020 16:15:50) Message: Iniciada a transação de recuperação. (Type: 1, Category: 289, Event ID: 0x41210029)
(16/12/2020 16:15:50) Message: Transação de recuperação bem-sucedida (Type: 1, Category: 289, Event ID: 0x4121002A)
(16/12/2020 16:15:50) Message: O arquivo de definição de instantâneo do flight recorder 'C:\Program Files\Microsoft Power BI Desktop\bin\FlightRecorderSnapshotDef.xml' não foi encontrado, ignorando a inicialização da atividade de geração de instantâneos. (Type: 1, Category: 289, Event ID: 0x41210021)
(16/12/2020 16:15:50) Message: O flight recorder foi iniciado. (Type: 1, Category: 289, Event ID: 0x41210005)
(16/12/2020 16:15:51) Message: Informações do Processador: NumberOfNumaNodes = , NumberOfAffinityGroups = 1, NumberOfCPUs = , NumberOfPhysicalCores = 4, NumberOfLogicalCores = , PhysicalMemoryAvailable = 7 GB (Type: 1, Category: 289, Event ID: 0x4121001D)
(16/12/2020 16:15:51) Message: Serviço iniciado. Microsoft SQL Server Analysis Services Enterprise de 64 Bits (x64) RTM 15.1.63.25. (Type: 1, Category: 289, Event ID: 0x41210000)
(16/12/2020 16:15:51) Message: Começando a escutar em TCPIP: Status = ListenToPortSuccess, ComputerName = DESKTOP-08R8HAQ, PhysicalNetBIOSName = DESKTOP-08R8HAQ, ListenOnIP = ::1, Port = 65042, ProtocolType = IP6 (Type: 1, Category: 289, Event ID: 0x4121001C)
(16/12/2020 16:15:51) Message: Começando a escutar em TCPIP: Status = ListenToPortSuccess, ComputerName = DESKTOP-08R8HAQ, PhysicalNetBIOSName = DESKTOP-08R8HAQ, ListenOnIP = 127.0.0.1, Port = 65042, ProtocolType = IP4 (Type: 1, Category: 289, Event ID: 0x4121001C)
(16/12/2020 16:15:51) Message: O arquivo msmdsrv.port.txt foi gravado com a porta = 65042. (Type: 1, Category: 289, Event ID: 0x41210037)
(16/12/2020 16:15:51) Message: As métricas de uso de software estão desabilitadas. (Type: 1, Category: 289, Event ID: 0x4121000E)
(16/12/2020 16:17:45) Message: Erro do OLE DB ou do ODBC : O contêiner foi encerrado inesperadamente com o código 0xC0000374. PID: 388.
Recursos usados: Odbc.DataSource/OdbcFb/02.00.0156/Firebird/06.03.27050 WI-V Firebird 2.5.. (Type: 3, Category: 289, Event ID: 0xC1210003)
===========================================

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

Top Kudoed Authors