Hello. I have an odd problem on my Windows network that I have not been able to solve.
I run AWStats 7.9 to produce reports from my Apache 2.4 web server which is running on Windows 11. This past week I moved all the web data from a local drive which was running out of space to a networked drive on my NAS server. The move went well. A network drive is mapped for the SYSTEM account with a Windows task that runs a login batch file at startup. This works because the Apache web server service starts just fine.
AWStats runs from a batch file on the networked drive. The command line calls PERL from the C: drive. Only PERL is on the local drives. Everything else related to AWStats is on the networked drive including the batch file that runs it, the server logs, and the output directories.
The batch file runs successfully from a Windows task on three of eight Windows computers on the network. It fails at the AWStats command line on the other five.
Of the five that fail, one is Windows 11, the others are Windows 10. This appears to be a Windows problem since the network batch file runs on three machines just fine.
I've pretty much tried everything I can think of to get the five failing machines to run this batch job. All the files on the network have Everyone permissions for now so its not a file permission issue. All 8 computers have the same Local Account name.
How is it even possible that one batch file will run on some machines and fail on others?
What else can i look at to try and solve this problem?
Thanks.
I run AWStats 7.9 to produce reports from my Apache 2.4 web server which is running on Windows 11. This past week I moved all the web data from a local drive which was running out of space to a networked drive on my NAS server. The move went well. A network drive is mapped for the SYSTEM account with a Windows task that runs a login batch file at startup. This works because the Apache web server service starts just fine.
AWStats runs from a batch file on the networked drive. The command line calls PERL from the C: drive. Only PERL is on the local drives. Everything else related to AWStats is on the networked drive including the batch file that runs it, the server logs, and the output directories.
The batch file runs successfully from a Windows task on three of eight Windows computers on the network. It fails at the AWStats command line on the other five.
Of the five that fail, one is Windows 11, the others are Windows 10. This appears to be a Windows problem since the network batch file runs on three machines just fine.
I've pretty much tried everything I can think of to get the five failing machines to run this batch job. All the files on the network have Everyone permissions for now so its not a file permission issue. All 8 computers have the same Local Account name.
How is it even possible that one batch file will run on some machines and fail on others?
What else can i look at to try and solve this problem?
Thanks.