What does "CHPXmlParserCommon Entered" mean?

Hello Experts,

When testing my application in debug mode I have recently begin to get a lot of messages in the immediate window that read:

    CHPXmlParserCommon Entered
    ~CHPXmlParserCommon Entered

When these messages appear, they tend to be repreated consecutively many times.

These message don't "appear" to have an impact on the operation of the application.  Can anyone enlighten me about the source of these messages and what they might mean.  (What I really want is to no longer be troubled by a whole lot of duplicate (and to me, meaningless) lines in the immediate window.

Thanks for any help.

Cheers,
Randy
LVL 12
omegaomegaDeveloperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Christopher KileCommented:
What references do you have in your application?  One of them is generating debug messages.  Have you searched all of your DLLs for CHPXmlParser?  From some of my reading, it may be related to PHP, are you using any?
0
omegaomegaDeveloperAuthor Commented:
Hi, cpkilekofp,

Thanks for the suggestions.  I don't think the references have changed recently and I don't believe I have any references to PHP.

Your suggestion that I search my DLLs for this string was really good.  Unfortunately, in the process I discovered the XP search tool ignores DLLs (even if the fix "Index files with unknown extensions" has been applied.)  (And yes, I have Search Hidden... and Search System... checked.)  I have really hated this so-called search tool since I started using XP, and what little I have heard tells me that it has been made even worse in Vista.  So there was some delay while I finally went off to find a proper search tool.

I found Agent Ransack (http://www.mythicsoft.com/agentransack/) which appears to be a much more useful tool.

It located the offending string in half a dozen DLLs that are all contained in "WINDOWS\System\Spool\Drivers..." and relate to an HP printer.  

That is not too surprising, since the problem has only occurred recently, and my most recent task has been trying to set PrinterProperties.  I thought that I had been successful, but have just today discovered that my application crashes with an AccessViolationException when (using the [Properties] button on the standard Print dialog) I try to open the Properties dialog for that same HP printer.  I can open the Properties dialog for all other printers available without problem.  And I can also open the Properties dialog for the HP printer from other applications, so I'm a bit mystified by this.

Anyway, I suspect that these two problems are related, so thanks again for the suggestion to search the DLLs.  That has given me a starting point.

I'll investigate this a little further before I close this question.  If you have any further suggestions for how to proceed, I'd sure be pleased to hear them.

Cheers,
Randy
0
Christopher KileCommented:
My first suggestion is to ask HP for help by email (I think they'll answer questions for free this way).  Second would be to make sure your drivers are the most recent and up-to-date, and if not make them so.

XP's search problem is well known.  Here's the link to Microsoft's fix for the issue:

http://support.microsoft.com/kb/309173
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
OWASP: Threats Fundamentals

Learn the top ten threats that are present in modern web-application development and how to protect your business from them.

omegaomegaDeveloperAuthor Commented:
Hello, cpkilekofp,

Thanks.  Those are both good suggestions and I'll follow up on them.

Yes, I've been aware of XP's search problems for ages.  The trouble is, I had long ago followed the second work-around in the link, but have only now discovered that .DLLs still seem to be excluded from the search.  That problem doesn't seem to be shared by Agent Ransack, so I'll be using (and recommending) it in the future.

Cheers,
Randy

0
Christopher KileCommented:
Interesting.  On my system (using the last registry fix), DLLs get searc hed.  However, you do have a working solution :)
0
omegaomegaDeveloperAuthor Commented:
Thanks for your help.  Updating drivers solved the "application crashing" problem.  I'm working with HP support on the "CHPXmlParserCommon Entered" problem (but frankly don't think they will have a solution.)  Fortunately this original problem is less critical, since it shouldn't bother the users.  Again, thanks very much.

Cheers,
Randy
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Editors IDEs

From novice to tech pro — start learning today.