You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-users@xerces.apache.org by George <ge...@trianz.com> on 2014/05/16 15:24:46 UTC

Re: The specified resource type cannot be found in the image file

Its and XMLException which we are getting on call to
XercesDomParser::parse(). I did not have put enough logs and hence do not
know the error code (exception.getCode())

Based on excepetion.GetMessage() value , can someone suggest the root cause?
The error occurs randomly only.

Regards,
George



--
View this message in context: http://apache-xml-project.6118.n7.nabble.com/The-specified-resource-type-cannot-be-found-in-the-image-file-tp41072p41080.html
Sent from the Xerces - C - Users mailing list archive at Nabble.com.

Re: The specified resource type cannot be found in the image file

Posted by George <ge...@trianz.com>.
I was able to resolve the parsing issue by putting the call within critical
session.. The issue was occuring due to "Parse In Progress"  issue. (error
code 39) 

But we still face the error reported in event viewer (occurs very rarely).
Our customer has provided the following win debug logs. Does any one know
why it fails at XMLScanner::commonInit() call.

 # Child-SP          RetAddr           Call Site
00 00000000`0263c988 000007fe`fd7d1430 ntdll!ZwWaitForMultipleObjects+0xa
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for
kernel32.dll - 
01 00000000`0263c990 00000000`77591723
KERNELBASE!WaitForMultipleObjectsEx+0xe8
02 00000000`0263ca90 00000000`7760b5e5
kernel32!WaitForMultipleObjectsEx+0xb3
03 00000000`0263cb20 00000000`7760b767 kernel32!WinExec+0x3b5
04 00000000`0263cbc0 00000000`7760b7bf kernel32!WinExec+0x537
05 00000000`0263cbf0 00000000`7760b9dc kernel32!WinExec+0x58f
06 00000000`0263cc20 00000000`fffa1a57
kernel32!UnhandledExceptionFilter+0x1fc
07 00000000`0263cd00 000007fe`f8a34494 w3wp!WpUnhandledExceptionFilter+0x47
08 00000000`0263cd30 00000000`7760b940
mscoreei!InternalUnhandledExceptionFilter+0x30
09 00000000`0263cd60 00000000`77823398
kernel32!UnhandledExceptionFilter+0x160
0a 00000000`0263ce40 00000000`777a85c8 ntdll! ?? ::FNODOBFM::`string'+0x2365
0b 00000000`0263ce70 00000000`777b9d2d ntdll!_C_specific_handler+0x8c
0c 00000000`0263cee0 00000000`777a91cf
ntdll!RtlpExecuteHandlerForException+0xd
0d 00000000`0263cf10 00000000`777e1248 ntdll!RtlDispatchException+0x45a
0e 00000000`0263d5f0 00000000`12082d6a ntdll!KiUserExceptionDispatch+0x2e
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for
xerces-c_3_1.dll - 
0f 00000000`0263dbb0 00000000`120810bb
xerces_c_3_1!xercesc_3_1::XMLScanner::commonInit+0x1e
10 00000000`0263dc00 00000000`1205b3c4
xerces_c_3_1!xercesc_3_1::XMLScanner::XMLScanner+0x413
11 00000000`0263dc80 00000000`12086969
xerces_c_3_1!xercesc_3_1::IGXMLScanner::IGXMLScanner+0x20
12 00000000`0263dcf0 00000000`1209b0e4
xerces_c_3_1!xercesc_3_1::XMLScannerResolver::getDefaultScanner+0x4d
13 00000000`0263dd40 00000000`1209ada8
xerces_c_3_1!xercesc_3_1::AbstractDOMParser::initialize+0x74
14 00000000`0263dd90 00000000`120aa392
xerces_c_3_1!xercesc_3_1::AbstractDOMParser::AbstractDOMParser+0x100
*** WARNING: Unable to verify checksum for EmbeddedConfigurationClient.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for
EmbeddedConfigurationClient.dll - 
15 00000000`0263de00 00000000`022e5cc3
xerces_c_3_1!xercesc_3_1::XercesDOMParser::XercesDOMParser+0xe
//Our DLL instantiate XercesDomParser

I do not know which line its failing.. 

Regards,
George

Regards,
George



--
View this message in context: http://apache-xml-project.6118.n7.nabble.com/The-specified-resource-type-cannot-be-found-in-the-image-file-tp41072p41159.html
Sent from the Xerces - C - Users mailing list archive at Nabble.com.

Re: The specified resource type cannot be found in the image file

Posted by Alberto Massari <al...@tiscali.it>.
Hi George,
I'm sorry, but it's impossible to find out the location of the code with 
these informations. If you can install a debugger on the client 
computer, you can try enabling just-in-time debugging to see the source 
of the access violation.

Alberto

Il 22/05/14 11:53, George ha scritto:
> Hi Alberto,
>
> Thanks for your reply. Our application is running on IIS 7 and two of our
> DLLs are using Xerces. But when I link statically one of them give linker
> errors. Hence I have not attempted that solution as of now.
>
> The event viewer sent by our client shows the following
>
> Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp:
> 0x4ce7afa2
> Faulting module name: xerces-c_3_1.dll, version: 3.1.0.0, time stamp:
> 0x4b62cc17
> Exception code: 0xc0000005
> Fault offset: 0x0000000000082c1a
> Faulting process id: 0x12fc
> Faulting application start time: 0x01cf6f4221ae486b
> Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
> Faulting module path: <path of xerces dll>\xerces-c_3_1.dll
> Report Id: 5f750277-db35-11e3-b920-0019998d9ab7
>
> I am not sure this crash occurs at the same time when we get an
> XMLException. This error occurs randomly and only with one of the client
> when they integrate our DLLs to their app. on IIS 7.
>
> Do you have any clue for the cause of the crash? Fault offset value is
> consistently same when this error occurs.
>
>
> Regards,
> George
>
>
>
>
> --
> View this message in context: http://apache-xml-project.6118.n7.nabble.com/The-specified-resource-type-cannot-be-found-in-the-image-file-tp41072p41114.html
> Sent from the Xerces - C - Users mailing list archive at Nabble.com.
>


Re: The specified resource type cannot be found in the image file

Posted by George <ge...@trianz.com>.
Hi Alberto,

Thanks for your reply. Our application is running on IIS 7 and two of our
DLLs are using Xerces. But when I link statically one of them give linker
errors. Hence I have not attempted that solution as of now.

The event viewer sent by our client shows the following

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp:
0x4ce7afa2
Faulting module name: xerces-c_3_1.dll, version: 3.1.0.0, time stamp:
0x4b62cc17
Exception code: 0xc0000005
Fault offset: 0x0000000000082c1a
Faulting process id: 0x12fc
Faulting application start time: 0x01cf6f4221ae486b
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: <path of xerces dll>\xerces-c_3_1.dll
Report Id: 5f750277-db35-11e3-b920-0019998d9ab7

I am not sure this crash occurs at the same time when we get an
XMLException. This error occurs randomly and only with one of the client
when they integrate our DLLs to their app. on IIS 7.

Do you have any clue for the cause of the crash? Fault offset value is
consistently same when this error occurs. 


Regards,
George




--
View this message in context: http://apache-xml-project.6118.n7.nabble.com/The-specified-resource-type-cannot-be-found-in-the-image-file-tp41072p41114.html
Sent from the Xerces - C - Users mailing list archive at Nabble.com.

Re: The specified resource type cannot be found in the image file

Posted by Alberto Massari <al...@tiscali.it>.
Hi George,
the web site only links to the latest version; the others are available 
in the archive, e.g. Xerces 3.1.0 is at 
http://archive.apache.org/dist/xml/xerces-c/Xerces-C_3_1_0/
Switching to the static library could fix your problem, if the problem 
is caused by the loading of the error messages from the .rc file, as the 
static version cannot use that method and uses instead the in-memory 
message loader. I would suggest that you first understand what is the 
cause of the behaviour that you are seeing; nonetheless, downloading a 
binary release of 3.1.1 and using the static library that it contains 
should make it disappear

Alberto

Il 19/05/14 09:35, George ha scritto:
> Thanks for the reply.
>
> We are uisng Xerces 3.1.0. I think we are not using a pre-compiled version.
>
> At the same time, I cannot find Xerces 3.1.0 at
> http://xerces.apache.org/mirrors.cgi#source. Why its so?
> (only 3.1.1 is available)
>
> I think I have two options to try.
>
> 1)Upgrade to 3.1.1
> 2)Statically  link to Xerces 3.1 (We are now linked dynamically..)
>
> Please let me know  of any other suggestions to fix the issue.
>
> Regards,
> George
>
>
>
>
> --
> View this message in context: http://apache-xml-project.6118.n7.nabble.com/The-specified-resource-type-cannot-be-found-in-the-image-file-tp41072p41102.html
> Sent from the Xerces - C - Users mailing list archive at Nabble.com.
>


Re: The specified resource type cannot be found in the image file

Posted by George <ge...@trianz.com>.
Thanks for the reply.

We are uisng Xerces 3.1.0. I think we are not using a pre-compiled version.

At the same time, I cannot find Xerces 3.1.0 at
http://xerces.apache.org/mirrors.cgi#source. Why its so?
(only 3.1.1 is available)

I think I have two options to try.

1)Upgrade to 3.1.1
2)Statically  link to Xerces 3.1 (We are now linked dynamically..)

Please let me know  of any other suggestions to fix the issue. 

Regards,
George




--
View this message in context: http://apache-xml-project.6118.n7.nabble.com/The-specified-resource-type-cannot-be-found-in-the-image-file-tp41072p41102.html
Sent from the Xerces - C - Users mailing list archive at Nabble.com.

Re: The specified resource type cannot be found in the image file

Posted by Alberto Massari <al...@tiscali.it>.
The message should come from Windows, when the code tries to retrieve a 
resource from the .RC file, but the resource isn't present. If you are 
sure that the message comes from Xerces, it could be that the .RC file 
isn't aligned with the list of error strings. Which version of Xerces 
are you using, and how did you obtain it? (e.g. did you compile it 
yourself?)

Alberto


Il 16/05/14 15:24, George ha scritto:
> Its and XMLException which we are getting on call to
> XercesDomParser::parse(). I did not have put enough logs and hence do not
> know the error code (exception.getCode())
>
> Based on excepetion.GetMessage() value , can someone suggest the root cause?
> The error occurs randomly only.
>
> Regards,
> George
>
>
>
> --
> View this message in context: http://apache-xml-project.6118.n7.nabble.com/The-specified-resource-type-cannot-be-found-in-the-image-file-tp41072p41080.html
> Sent from the Xerces - C - Users mailing list archive at Nabble.com.
>