Welcome to the Mythicsoft Q&A site for:

- Agent Ransack
- FileLocator Lite
- FileLocator Pro

Please feel free to ask any questions on these products or even answer other community member questions.

Useful Links:

- Contact Us
- Help Manuals
- Mythicsoft Home
0 votes

I received the following error when running agent ransack from the command line: "Search was not successful. Failure during CCmdLineSearch::search()".

I was wondering if anyone could lend some help on what could cause this message to trigger? Any help would be appreciated.

asked by (30 points)

1 Answer

0 votes

First try the same search from the GUI. Then save that search and run it from the command line. If it still fails have a look in the logfile and post the last error here.

answered by (66.9k points)

Here is the error message received this morning for this same error.

7/31/2012 2:59:06 AM ERROR: Opening output stream failed.

0x80040c07 (0x20) - :83 - .\CmdLineSearch.cpp

So from that I gather it is having problems opening the file in which it outputs the saved results. The strange thing is I have this running on two seperate computers which saves the output files locally (to the c:) and on one it works with no errors and the other I receive these errors.

Just a little background. I am running Ransack from a service I coded up so that I could run it at certain times and copy out files to a network drive when the searches are finished.

The 0x20 code translates to: "The process cannot access the file because it is being used by another process". Could this be a Anti-virus issue, e.g. are you 'touching' this file prior to Agent Ransack trying to open it for write access?

No, I am not accessing this file in any way prior to Agent Ransack opening it for write access. I just removed the 'Run as Administrator' check box from the computer I get this error on to see if this clears up the problem. I don't have much faith in this fix though.

Does this happen when run from the command prompt or only when run from the service?

If you could try running Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) that can tell you exactly which processes are trying to open the file. ProcMon generates an awful lot of information but you can add a filter to show only information related to your output file.

Actually removing the 'Run as Adminstrator' option made the error go away. I will still take a look at ProcMon to see what is trying to access the file because that flag shouldn't have anything to do with file access. Atleast I wouldn't think.

...