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:

1. Run the scan again to create a new scan XML file
2. 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.ini
When 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 network
OFC (in FileList mode) and VET both require network access to work properly

Databases of More Than One Million Scan Records

I have a large OMPM database of more than a million scan records and am experiencing inconsistent behavior in the reporting tool.
The OMPM reporting tool cannot handle more than one million scan records in an OMPM database. There are two workarounds:

Use a single large database and query the SQL directly. OMPM schema can be found at http://technet.microsoft.com/en-us/library/cc179162.aspx.

Separate the large database into several databases of less than one million records. Here are instructions for how to do this:

Recovering Scan Data
OMPM moves imported scan data into a folder called OMPMImported in the folder storing your scan results after it imports it. For example, if your scan results are in C:\OMPM\SCANDATA, the imported logs would be in C:\OMPM\SCANDATA\OMPMImported.
1. You have two options for how to prepared to import that data again:
a. You can copy all of those files back up into C:\OMPM\SCANDATA and delete the OMPMImported directory
b. You can just re-import directly from C:\OMPM\SCANDATA\OMPMImported
2. We’ll call the directory you’ve chose to import out of SCAN_DIRECTORY for the rest of these steps. In our example, if you chose option 1.a., SCAN_DIRECTORY=C:\OMPM\SCANDATA. If you chose option 1.b., SCAN_DIRECTORY=C:\OMPM\SCANDATA\OMPMImported.

Preparing Scan Data for Multiple Databases
You next need to partition your scan data to allow it to easily be imported into multiple databases.
1. Create a set of folders under SCAN_DIRECTORY for holding subsets of the scan data. You should create at least enough to allow you to put no more than 100 scan CABs in each directory. (Should be at least 4 folders in your case). We’ll call these folders SCAN_DIRECTORY\partition1, SCAN_DIRECTORY\partition2, etc.
2. Copy the 00001-indexed scan CAB file into each partition directory. This file will be named like Scan_machinename{GUID}00001.CAB.
3. Copy no more than 99 additional CABs into each partition directory until you have put them all into a partition.
Note: you can pretty much combine the actions in this section with the “recovering scan data” section to copy less data around, but I kept them separate to illustrate what’s going on

Importing Scan Data
You are now ready to create the databases and import data into them.
1. Open a command prompt
2. Navigate to the Database directory of OMPM (e.g., C:\OMPM\Database)
3. Enter “CreateDB.bat SQL_SERVER ompm1”, where SQL_SERVER is the path to the SQL server you want to host the OMPM database, and ompm1 is the name of the database to create on that server (you can choose a different database name)
4. Enter “ImportScans.bat SQL_SERVER ompm1 SCAN_DIRECTORY\partition1”
5. OMPM will begin importing the scan data in partition 1 to the database you have indicated. It should complete and report success. If not, there are database import errors to troubleshoot.
6. After the import action completes, repeat steps 2-5 for the remaining partitions. Make sure to create a new database each time (you can use the same SQL server each time).
7. Each database should be no more that 1 million records in the omFile table as long as each partition had no more than 100 CABs.

Viewing Scan Reports
You can now use the reporting tool with OMPM and have expected behavior.
1. Open ompm.accdb from OMPM’s Report folder (e.g., C:\OMPM\Report)
2. Ensure you are on the “OMPM Welcome” tab of the report.
3. Enter the name of your SQL server in the “Server” field or select a detected server from the dropdown.
4. Enter the name of a partition database in the “Database” field or select a previous database from the dropdown.
5. Click Connect. The report should open for the partition database you have entered.
6. To view a different partition database, return to the “OMPM Welcome” tab, enter the new database, and click “Connect” again.
7. If you close and reopen the report, it will attempt to automatically connect to the most recent database it was connected to.

---

Back to OMPMv1