ExportCrawlLog Work Item Rss Feed

Created Issue: Parameter "-mt s" is not working properly [10187]

okoestner — Wed, 10 Feb 2010 08:57:49 GMT

When I try to export the successes using "-mt s " , it exported the same warnings that I got using "-mt w" option.

Commented Issue: Unable to export log messages from File Share content sources. [8811]

lkuhn65 — Fri, 18 Sep 2009 22:08:59 GMT

At line 42 of ExportCrawlLog.vb the code there assumes that the -site parameter refers to a SharePoint site in farm. When desiring to export log messages from a File Share content source, the user needs to pass in a UNC path of the content source, however this path is not valid for use to obtain the SearchContext. might need to add another optional parameter to support this export scenario.
Comments: ** Comment from web user: lkuhn65 **

found a way to get it done. I used the -hostname option to acheive my results
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN>stsadm -o ExportCrawlLog -t d -site "http://XXYXX/" -history -outfile c:\downloads\crawl.csv -s "2009-09-12 07:20:00" -e "2009-09-18 08:00:00" -hostname co-shr-w -mt e
To get the errors on the actual sharepoint site i had to use
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN>stsadm -o ExportCrawlLog -t d -site "http://XXYXX/" -history -outfile c:\downloads\crawl.csv -s "2009-09-12 07:20:00" -e "2009-09-18 08:00:00" -hostname XXYXX -mt e
To get a consolidated error log just exclude the -hostname option. That does the trick

Closed Issue: Unable to export log messages from File Share content sources. [8811]

lkuhn65 — Fri, 18 Sep 2009 22:08:49 GMT

Created Issue: Unable to export log messages from File Share content sources. [8811]

lkuhn65 — Fri, 18 Sep 2009 14:20:48 GMT

At line 42 of ExportCrawlLog.vb that the code there assumes that the -site parameter refers to a SharePoint site in farm. When desiring to export log messages from a File Share content source, the user needs to pass in a UNC path of the content source, however this path is not valid for use to obtain the SearchContext. might need to add another optional parameter to support this export scenario.

Commented Issue: Failure adding assembly ...

exl3074 — Tue, 29 Jul 2008 10:38:47 GMT

Hello, I am trying to deploy the STSADMExportCrawlLog.dll by running the "deploySTSADMExportCrawlLog.cmd" that come with the zip file, but I received the following error message:
***************************
"Failure adding assembly to the cache: Unknown Error"
***************************

Then I tried to run the stsadm command, and received the following error:
***************************
Value cannot be null.
Parameter name: type
***************************

Did I do something wrong?

Thanks,
Eton
Comments: ** Comment from web user: exl3074 **

Larry, it is working now. Thanks for the fix.

Eton

Closed Issue: Failure adding assembly ...

lkuhn65 — Wed, 16 Jul 2008 16:03:53 GMT

Commented Issue: Failure adding assembly ...

lkuhn65 — Wed, 16 Jul 2008 16:03:28 GMT

It looks like I was invoking the wrong/old gacutil.exe, per this blog http://weblogs.asp.net/wenching/archive/2008/05/22/gacutil-missing-in-windows-server-2008-visual-studio-2008-installation.aspx I have fixed the .cmd file now.
Thanks for the feedback!
- Larry

Commented Issue: Failure adding assembly ...

lkuhn65 — Wed, 16 Jul 2008 15:40:08 GMT

Eton,
There may be some problem with that .cmd file and therefore it seems the assembly is not registered right. What you can do instead is use drag/drop approach to add the assembly into the GAC: open windows explorer to view c:\windows\assembly, then drag/drop STSADMExportCrawlLog.dll into there. And then try again to run the command.
- Larry

Created Issue: Failure adding assembly ...

exl3074 — Thu, 10 Jul 2008 22:37:28 GMT