cancel
Showing results for 
Search instead for 
Did you mean: 

fsav.exe return codes

Scholar

fsav.exe return codes

Hello everyone,

 

I'm searching for the return codes of the on-demand scanner fsav.exe. (Where using Client Security 12.x Premium.)

 

I found this here in the community:

https://community.f-secure.com/t5/Business/On-demand-scanner-fsav-exit/ta-p/20254

 

But it seems, that this list is not complete (or false), because I get return codes like 12 and 23 which are not documented in the tobic above and I can't find a documentation where the return codes are described.

 

Can someone help me?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
F-Secure Product Expert

Re: fsav.exe return codes

Hi,

 

You can find fsav.exe return codes documented in the file *\F-Secure\Anti-Virus\readcmd.rtf and this is installed with Client Security.

 

For your concenience, pasting the relevant section below:

 

Return codes

The command-line scanner supports the following return codes. When an error is encountered, the corresponding message will also be printed on screen (stderr).

0

Scanning completed successfully, system is clean

1

Command line scan not allowed in policy (currently unsupported)

2

Scanning aborted by user

3

Error loading F‑Secure Anti‑Virus or one of its program files

4

Gatekeeper couldn’t connect to scanning engines

5

Self-test failed (currently unsupported)

6

Command line syntax error or unknown parameter

7

Execution failed, out of memory

8

Scan path not valid

10

Failed to open one of the report files, scanning successful

11

Encountered encrypted files that can’t be scanned  (currently unsupported)

12

Failed to open some targets, these objects may still be infected

20

Suspicious code found, may be a virus (currently unsupported)

21

One or more viruses found, actions successful, no remaining viruses

22

One or more viruses found, actions successful, renamed viruses remain on disk

23

One or more viruses found, actions unsuccessful or not attempted, system still infected

24

Virus found in memory, scanning aborted (currently unsupported)

Best Regards,
Peter
3 REPLIES 3
Superuser

Re: fsav.exe return codes

Hello,

 

> I get return codes like 12 and 23 which are not documented

 

Maybe the reported single error code value is created according to the bizarre logic usually found in Un*x products, where the numerical value is a composite and you have to find out that 23 is 6+8+9?

 

Yours Sincerely: Tamas Feher, Hungary.

Highlighted
F-Secure Product Expert

Re: fsav.exe return codes

Hi,

 

You can find fsav.exe return codes documented in the file *\F-Secure\Anti-Virus\readcmd.rtf and this is installed with Client Security.

 

For your concenience, pasting the relevant section below:

 

Return codes

The command-line scanner supports the following return codes. When an error is encountered, the corresponding message will also be printed on screen (stderr).

0

Scanning completed successfully, system is clean

1

Command line scan not allowed in policy (currently unsupported)

2

Scanning aborted by user

3

Error loading F‑Secure Anti‑Virus or one of its program files

4

Gatekeeper couldn’t connect to scanning engines

5

Self-test failed (currently unsupported)

6

Command line syntax error or unknown parameter

7

Execution failed, out of memory

8

Scan path not valid

10

Failed to open one of the report files, scanning successful

11

Encountered encrypted files that can’t be scanned  (currently unsupported)

12

Failed to open some targets, these objects may still be infected

20

Suspicious code found, may be a virus (currently unsupported)

21

One or more viruses found, actions successful, no remaining viruses

22

One or more viruses found, actions successful, renamed viruses remain on disk

23

One or more viruses found, actions unsuccessful or not attempted, system still infected

24

Virus found in memory, scanning aborted (currently unsupported)

Best Regards,
Peter
Scholar

Re: fsav.exe return codes

Hi,

thank you very much! ... seems that I'm to stupid to search ...

best regards,
Martin