http://www.perlmonks.org?node_id=431053

Smaug has asked for the wisdom of the Perl Monks concerning the following question:

Hello fellow monks,

I have a script which reads it's configuration from an XML file. When running the script the following error is displayed:
"could not find ParserDetails.ini in C:/Perl/site/lib/XML/SAX"
As you would expect, it is correct, the file is not there... I have searched to find help but neither this nor this, have worked for me. Most solutions seem to involve reinstalling, but I've tried that and it did not work.

Is it possible to create this ini file manually?
If so, could somebody post the format so that I can do this?
Thanks in advance, yet again, for your help!!!

  • Comment on could not find ParserDetails.ini in .......

Replies are listed 'Best First'.
Re: could not find ParserDetails.ini in .......
by Animator (Hermit) on Feb 15, 2005 at 10:50 UTC

    I remember that I had the same problem on my home machine... I think I fixed it by creating an emtpy ParserDetails.ini file, but I'm not sure... (I'm currently at work...)

    If I look on the contents of the ParserDetails.ini (located on my server), then I see this:

    [XML::SAX::PurePerl] http://xml.org/sax/features/namespaces = 1

    I don't know wheter or not this would be a correct ParserDetails.ini file for you...

      Try doing:

      perl -MCPAN -e 'install XML::SAX::Expat'

      That should place (non-pure-perl) parsers on the system.

      I was having the same problem and this fixed it for me.
        (Yes - still works in 2014)

        I found that this fix worked for some issues while running Nmap::Scanner as well. Posting this here for future searching...

        This worked for me. thanks.
Re: could not find ParserDetails.ini in .......
by holli (Abbot) on Sep 02, 2005 at 10:12 UTC
      make an empty file called ParserDetails.ini and try again. perl will approve.
Re: could not find ParserDetails.ini in .......
by rpcox (Initiate) on Nov 19, 2019 at 21:29 UTC
    Outdated and I know I'm the last one to the party, but I ran into this error just today.

    For me ParserDetails.ini was present and chock full of details, however, the file mode was 640 and owner/group set to root.

    sudo chmod 644 /path_to/ParserDetails.ini and the warning stopped.