in reply to read error in XML parsers, Windows XP Service only

By default, services run under the 'local system' account and have restricted priviledges. You should configure the service to run under an account with access to the files in question.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."
  • Comment on Re: read error in XML parsers, Windows XP Service only

Replies are listed 'Best First'.
Re^2: read error in XML parsers, Windows XP Service only
by soliplaya (Beadle) on Apr 20, 2008 at 19:01 UTC
    The service is running under a user-id, not LocalSystem. When I use the same user-id to login into Windows XP, and run the same program in a Command Window, it works flawlessly.

    I also have 3 other programs, which do the same thing using essentially the same code, and which run fine both in a Command window and as a service. They all call the XML parser to parse the same file (a common XML parameter file).

    I also use the same 4 programs on a number of other Windows XP machines, where they all run fine in console mode and as services.

    That's why I'm puzzled.
[reply]

In Section Seekers of Perl Wisdom