Hello,

I am using psexec to run a batch file on some remote machine on my network, that in turn runs clamscan from a shared drive on my network. This all seems to work fine for a few of the computers on my network, however, the scan fails on other computers.

All computers are running XP Pro SP3. I am using ClamWin 0.96.0.1. The relevant information from the --debug output is below.

LibClamAV debug:
Path converted from [C:\temp] to [\\?\C:\temp]
C:\temp: No such file or directory
LibClamAV debug: Cleaning up phishcheck


The command that I am running from the batch file is (where %1 is the directory supplied via CLI parameter):
U:\AVScan\ClamWin\bin\clamscan.exe --database=U:\AVScan\ClamWin\db --recursive --stdout --debug --bell -i "%1" >c:\clam-results.txt 2>&1


As mentioned, this does not produce an error on all the computers, just certain ones.

Any help anyone can provide is greatly appreciated.

Thanks,

William

looks like you have TEMP or TMP environment variable pointing to c:\temp while directory c:\temp does not exists

I forgot to mention that this also happens when I specify other directories to scan as an argument to the batch file. Although I did find that there was no C:\Temp on the computer I was testing on, so that actually was an error on my part.

Anyway, I found a solution. I'm not entirely sure why, but it didn't like the quotes I had surrounding the %1 in the batch file, or surrounding the path passed as an argument to the batch file through PSExec.

So not actually a ClamWin error, just a weird command line translation quirk, or a misunderstanding of batch files on my part (more likely).

Thanks for the suggestion.

I'm going through a similar struggle. Here's the command-line I used:

clamscan -f "c:\users\myself\clamwin\unins000.exe" --database=c:\users\myself\clamwin\db --verbose --debug

Of course there's no such directory. I checked my environmental variables, there's never anything titled "MZP" before or after running clamwin.

Well, I'm finding that from the command-line, when I try to run clamscan, I get this message no matter what file I'm trying to scan, no matter where:

Path converted from [MZP] to [\\?\C:\Users\Myself\ClamWin\bin\MZP]
WARNING: \\?\C:\Users\Myself\ClamWin\bin\MZP: Can't access file

My directory names are very short and don't approach anything like 100 characters let alone 255 characters, so it's not the 255 character error. That's out the window.

When I try calling clamwin from a batch file from inside of Firefox (using Download statusbar to call the batch file with its own argument %1 [which checks out working fine, the batch file correctly calls for the correct file to scan] and the batch file to pass argument %1 in for the scanned filename) I get even weirder things being converted from, where instead of "MZP", it's "PK???" where the questions marks printed here for simplicity actually stand-in for the lower-ascii characters heart, diamond, and paragraph-symbol as they are appearing in the program's output. So, this problem is really messed-up, with the program even outputting ascii control characters.

I'd like to get this fixed so I can use clamscan appropriately. What the hell is it?