An Unknown Error Has Been Encountered 追蹤

Legacy Poster

My client's situation is that the implementation uses the BarTender .Net SDK (10.1 SR2) within a custom WCF service. All parameters are passed to the WCF service so there is no requirement to connect to databases or like to get data. The WCF service only connects to the BarTender Library to get the necessary templates (note: two templates, first page is different to the rest)
It is the error event handler of the BarTender Task instance that receives a very cryptic error message...
"An unknown error has been encountered. Please unload any unnecessary programs and retry. Otherwise, please check your vender's web page or contact technical support for a newer copy.  Do you want to attempt to save your modified documents?"
Four dump files are created (I suspect this co-relates to the number of Task Engines that are running as we have implemented the WCF service to start four).
Using DebugDiag, the dump file says:
"In bartend_0897.dmp the assembly instruction at mfc90u!ATL::CSimpleStringT::Empty+d,1> in C:\Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90u.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 0"
"Please follow up with the vendor Microsoft Corporation for C:\Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90u.dll"
Thread 0 is:

Thread 0 - System ID 9168

This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

Function ntdll!ZwGetContextThread+12 kernel32!HeapFree+14 KERNELBASE!HeapDestroy+e 0x6bd3ff26



A few questions:


1) Has anyone encountered the "An unknown error has been encountered" error message?

2) Could Seagull confirm if we are running the correct version of MFC? (as the error states version 9.0.30729.6161)


Thanks in advance.





1 意見

Ian Cummings
評論操作 永久連結

I highly recommend that you update BarTender to SR4 as there have been many fixes between SR2 and SR4 which might well be affecting you.


Alas an unknown error can happen when we don't know of an error, and BarTender hits it, but thus we haven't coded a specific exception statement to catch it.