ISCommand ExtractLogs 9.3.1

[BenYoungs]

All,

I am trying to export out IS logs to a geodatabase to collect metrics on our hosted services. Before I went in and tried to parse through the XML in Python, I figured I would try the ISCommand ExtractLogs function.

First I ran:
ISCommand ExtractLogs --Folder=<Log File Folder Path> --Database=<Output DB Folder>

The process runs for a few seconds and finishes with an error:
"Failed to execute Export Log Command. Error: Command Failed : 'Extracting Log File to GDB'

The geodatabase is still created as is a couple megabytes in size, so I try to open it up in Catalog. When I do that, I get the following error message:
"Failed to connect to database. This release of the geodatabase is either invalid or out of data. [Unknown geodatabase release.] Item not found in this collection."

So then I tried the file option to export just a single log to the database using the following command:
ISCommand ExtractLogs --File=<Log File Location> --Database=<Output DB Folder>

This time the process runs without returning an error. The geodatabase is again created yet strangely the same size as the first attempt.

I get the same error as before and can not open the database. I also tried to run the command building a GDB vice an MDB, same results.

My question is, has anyone had any luck with this command? If not, does anyone have any good methods they have used to collect metrics on Image Services? We will be migrating to 10 soon so I'm not sure how much effort I want to put into parsing the logs.

Thanks in advance.

[MarceloBorsoi]

Hi Ben,

I had the same issue while opening the mdb in ArcCatalog. So, I opened it in Microsoft Access and I realized that mdb was empty (only the schema was created).

So I ran the Iscommand again, but with quotes in the path. Example:

ISCommand ExtractLogs --File="C:\Documents and Settings\All Users\Dados de aplicativos\ESRI\Image Server\Logs\ServiceProvider\20110405-ServiceProvider.log" --Database=c:\chamados\testfile1.mdb

I got the same error in ArcCatalog. But when I opened the new mdb in Microsoft Access the LOG was there.

[BenYoungs]

Marcelo,

Thanks for the info. I ended up writing a Python script to write the logs to CSV, and then brought that into Access. I will try the quotes though and see if that works for me.