Re: WinAdmin needs help w/ File System STDERR and

If indeed the only change is the OS, then I see a couple of places to go look:

You no longer have the proper permissions to write the new log file (which, in fact is what your error messages says!)
Some Process has the log open and has not been properly fitted out with 'close and re-open on my signal' logic.
This being Windows, trying to read a file that someone else has open for writing can be problematic (see the previous bullets)
Your old system was taking advantage of a 'Windows Quirk' (I have been told to stop calling them (adjective) Windows Bugs). That 'quirk' has been patched in the new OS.
And, the ever popular solution -- "Murphy hates you"

If it was me, I'd start with the Permissions issue first.

Good luck, this is likely not to be the first 'OS quirk' issue you are going to run into. (Ask me sometime why I hate upgrading Operating Systems. Preferably sometime when we both have a stein of beer at hand and the night is young....)

----
I Go Back to Sleep, Now.

OGB

Comment on Re: WinAdmin needs help w/ File System STDERR and

Replies are listed 'Best First'.
Re^2: WinAdmin needs help w/ File System STDERR and by ReturnOfTheYeti (Initiate) on Jul 23, 2013 at 18:36 UTC
Can you expand on: "Your old system was taking advantage of a 'Windows Quirk' (I have been told to stop calling them (adjective) Windows Bugs). That 'quirk' has been patched in the new OS. "? I am logged in as USER. I have given USER permission to the directory / file. USER can create/modify/delete files in the directory without issue. USER double clicks on the Perl script and that output is the error. The file the script is writing to is not in use. No other process has it open. So while I believe its a permission error, I am not sure where to look Thanks everyone for the quick reply	[reply]

Replies are listed 'Best First'.

Re^2: WinAdmin needs help w/ File System STDERR and
by ReturnOfTheYeti (Initiate) on Jul 23, 2013 at 18:36 UTC

Can you expand on: "Your old system was taking advantage of a 'Windows Quirk' (I have been told to stop calling them (adjective) Windows Bugs). That 'quirk' has been patched in the new OS. "?

I am logged in as USER. I have given USER permission to the directory / file. USER can create/modify/delete files in the directory without issue. USER double clicks on the Perl script and that output is the error. The file the script is writing to is not in use. No other process has it open.

So while I believe its a permission error, I am not sure where to look

Thanks everyone for the quick reply

[reply]