Running on local Win10 box?

Jul 21, 2015 at 10:01 AM
What exactly are the prerequisites for running this tool? It seems it only works on a SharePoint server, is that correct? I'm trying to run it on my local win10 box (no SharePoint installation apart from CSOM SDK), but it won't start (at all). Is that normal / expected behaviour?
Coordinator
Jul 25, 2015 at 9:18 AM
Hi,
The tool runs on any machine with .Net v4.0 framework installed. No SharePoint or CSOM required as it is using REST for communication.

Does the tool start on your machine at all? And remember to fill in login information after you start it pointing to your environment. Then try to enter * in the query box and see if you get results when searching.
Jul 25, 2015 at 9:59 AM
Hello,

nope the tool doesn't run at all. When I click the .exe, nothing happens.

Faulting application name: SearchQueryTool.exe, version: 2.4.0.0, time stamp: 0x5590ebf0
Faulting module name: ntdll.dll, version: 10.0.10240.16392, time stamp: 0x55a864a2
Exception code: 0xc00000fd
Fault offset: 0x000000000002f0d2
Faulting process id: 0x1da0
Faulting application start time: 0x01d0c6bfe6c47e02
Faulting application path: G:\Libraries\Downloads\SearchQueryToolv2.4\SearchQueryTool.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ea375f0e-b852-429e-88ed-04e6ee6992df
Faulting package full name:
Faulting package-relative application ID:

I downloaded the sources to run from visual studio, seems to break on the InitializeComponents call with the following error;

The program '[11596] SearchQueryTool.vshost.exe' has exited with code -1073741571 (0xc00000fd) 'Stack overflow'.
Coordinator
Jul 25, 2015 at 11:42 AM
I'll test it locally on Win10 and see.

Coordinator
Jul 25, 2015 at 12:36 PM
Did a compile just now on win10,using vs2013 and no issues.

Jul 30, 2015 at 8:06 AM
Ok. So we've got "it works on my machine" covered, but for me it's still not working :P I don't have any issues with other software, still might be OS related as I'm on the fast ring, don't know.
Coordinator
Jul 30, 2015 at 10:07 AM
If you have the code, can you set a breakpoint in initialize and start in debug mode in visual studio and see which line it fails at?

Jul 30, 2015 at 7:27 PM
I wanted to, but it suddenly started working. I did receive some updates yesterday so maybe it was a Windows thing after all. Anyways, it seems to be fine now or at least I'm unable to reproduce the problem at this time. Thanks for listening :)
Coordinator
Jul 30, 2015 at 8:19 PM
Great stuff :)