Provider error 80040e14, MSOLAP provider and COM+

Last Post 18 Aug 2005 01:46 PM by manoloarbulu. 0 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
manoloarbulu
New Member
New Member

--
18 Aug 2005 01:46 PM
I made a business layer using VB 6.0 sp 5 and Component Services under win2k sp3, this Dll executes a few MDX querys through a huge OLAP (Analysis Services 2k sp3) cube using ADOMD as well SQL Querys to a SQL 2k SP 3a enterprise edition, this environment works fine in production for several weeks serving about 40,000 MDX querys at day.

Our Presentation Layer has been made in ASP pages, formatting all output in HTML format

But after days working fine, It started to appear an Provider error '80040e14' in all MDX querys, is not an OLAP issue because reestarting the server does not fix the problem, when the COM+ application is restarted is when the problem disappears.

The production server has The Microsoft Debug Diagnostic Tool 1.0 and has made a User Dump file for this Dll warning us about a First Chance Access Violation problem in the Dll, I don't know how to found the problem y how to interpret the Debug File.


Analysis Summary
Type Description Recommendation
Error WARNING - DebugDiag was not able to locate debug symbols for XCHCENTRALNEG.dll, so the information below may be incomplete.



In dllhost__Xchange Central WEB Negocio Com+__PID__1040__Date__08_18_2005__Time_04_49_57PM__875__First Chance Access Violation.dmp the assembly instruction at XCHCENTRALNEG!DllCanUnloadNow+b8e in C:\Program Files\Xchange Perú\CentralWeb\Componentes\XCHCENTRALNEG.dll from Xchange Perú has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 23
Please follow up with the vendor Xchange Perú for C:\Program Files\Xchange Perú\CentralWeb\Componentes\XCHCENTRALNEG.dll

Warning
DebugDiag failed to locate the PEB (Process Environment Block) in dllhost__Xchange Central WEB Negocio Com+__PID__1040__Date__08_18_2005__Time_04_49_57PM__875__First Chance Access Violation.dmp, and as a result, debug analysis for this dump may be incomplete or inaccurate.


Analysis Details
Table Of Contents
dllhost__Xchange Central WEB Negocio Com+__PID__1040__Date__08_18_2005__Time_04_49_57PM__875__First Chance Access Violation.dmp

Faulting Thread

Faulting Module Information




Report for dllhost__Xchange Central WEB Negocio Com+__PID__1040__Date__08_18_2005__Time_04_49_57PM__875__First Chance Access Violation.dmp
Type of Analysis Performed Crash Analysis
Machine Name
Operating System Windows 2000 Service Pack 3
Number Of Processors
Process ID 1040
Process Image C:\WINNT\system32\DLLHOST.EXE
System Up-Time 0 day(s) 00:00:00
Process Up-Time 0 day(s) 00:00:30


Thread 23 - System ID 1156
Entry point comsvcs!STAThread::STAThreadWorker
Create time 8/18/2005 4:49:33 PM
Time spent in user mode 0 Days 0:0:0.15
Time spent in kernel mode 0 Days 0:0:0.31


Function Source
XCHCENTRALNEG!DllCanUnloadNow+b8e
OLEAUT32!DispCallFunc+15d
msvbvm60!BASIC_CLASS_Invoke+259
msvbvm60!BASIC_CLASS_Invoke+52
OLEAUT32!IDispatch_Invoke_Stub+6d
OLEAUT32!IDispatch_RemoteInvoke_Thunk+3c
rpcrt4!NdrStubCall2+604
rpcrt4!CStdStubBuffer_Invoke+c8
OLEAUT32!CStubWrapper::Invoke+9f
OLE32!SyncStubInvoke+61
OLE32!StubInvoke+a8
OLE32!CCtxComChnl::ContextInvoke+bb
OLE32!MTAInvoke+18
OLE32!STAInvoke+56
OLE32!AppInvoke+88
OLE32!ComInvokeWithLockAndIPID+2b5
OLE32!ComInvoke+41
OLE32!ThreadDispatch+21
OLE32!ThreadWndProc+101
USER32!UserCallWinProc+18
USER32!DispatchMessageWorker+2e4
USER32!DispatchMessageW+b
comsvcs!STAMessageWork:: DoWork+15 ..\inc\STAThred.h @ 244
comsvcs!STAThread::STAThreadWorker+423 .\stathred.cpp @ 650
KERNEL32!BaseThreadStart+52


XCHCENTRALNEG!DLLCANUNLOADNOW


Acceptable Use Policy
---