Troubleshooting
Scanner
Importing
Importing Scans
I imported the CAB files successfully (I think), but when I view the results in the Reporting Tool the database appears empty. What happened to my scan results?In addition to the XML scan logs, the scanner also produces a single Scan_{GUID}.XML file for each run. This file describes the configuration of the scan run including RunID, folders to scan, and all the other properties set in the offscan.ini configuration file. For an import to be successful, the scan XML file must be present. The file is the first thing generated by a scanner run and can be found in the first CAB file that is produced. So, if you import all the CAB's generated by a scanner run, including the first CAB which has the scan XML file, the import will be successful. If you cannot find that first CAB file or the scan XML file inside it, you have the following options:
- Run the scan again to create a new scan XML file
- Create a dummy scan XML file (the schema is very simple)
Importing Actions
I tried to import the logs generated by the OFC and upon completion the console said that 0 logs were imported.If you are sure the path is correct, try this next idea. The last parameter supplied to
ImportActions.bat tells where to look for the XML log files. It is expecting
domain name\
computer name\
action log files here. If you run either VET or OFC on a machine that is not on a domain, that domain level folder is never created. You can either point the
ImportActions.bat to a folder one level higher, or create a dummy domain folder and copy the logs there. then, you can import successfully.
Reporting Tool
Conversion Issues
I have this issue in some Excel files: "Save format not supported - Excel 2007 does not support saving to this file format." What does that mean?Excel 2007 can open this file format and save the file in a newer format (e.g. xls, xlsx), but it cannot save back to the original file format.
Companion Tools
I'm running OFC and it seems to convert fine but I don't see any logs in the path a designated by ofc.iniWhen running OFC in standalone mode (by designating locations in
Folders To Convert) no action XML logs are produced. The action XML logs are only produced when the OFC is run in
FileList mode (running against an exported list from the Reporting Tool). If you want to capture some information, you can simply redirect the console output to a text file:
ofc.exe > log.txt
OFC and VET fail to do anything when my machine is not on the networkOFC (in
FileList mode) and VET both require network access to work properly
Back to
OMPMv1