Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
GridNode cannot find sn.exe
Options
Previous Topic Next Topic
leechang
#1 Posted : Tuesday, January 21, 2014 12:38:54 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/26/2012(UTC)
Posts: 5
I've been having trouble getting started with distributed processing, and I think I found a bug.
I was getting an error that sn.exe could not be found, and it looks like the server was looking in the wrong spot. The server only has the 8.1A SDK and VS2013. It looks like GridNode is looking for
C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.0 Tools\sn.exe

But the install was at:
C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\sn.exe

I copied sn.exe to the bin directory, and everything started working.

Hope that helps!
Back to top
yanglee
#2 Posted : Tuesday, January 21, 2014 2:09:58 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/25/2012(UTC)
Posts: 89
Location: China

Thanks: 23 times
Was thanked: 19 time(s) in 18 post(s)
I'm not sure if I understand correctly but I guess it's probably not a bug. According to the documentation:

Quote:
Each grid node server needs to have installed any SDKs or frameworks required to build your source tree and execute the code within it. This means you must have the appropriate version of the .NET framework installed, along with any frameworks used by your source code that involve reference files being stored underneath the 'Program Files' or 'Windows' directories. Depending upon your solution, you may or may not need to have Visual Studio installed on each grid node. Typically, a grid node setup should be similar to any team build server.
Back to top
Remco
#3 Posted : Tuesday, January 21, 2014 4:11:49 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,123

Thanks: 957 times
Was thanked: 1286 time(s) in 1193 post(s)
I think the problem here is that the latest version of NCrunch doesn't take consideration of machines that have only v4.5.1 of the .NET framework tools installed, but not v4.0.

This should be an easy fix from the NCrunch side. Your copying of the file is the correct workaround that I would otherwise suggest. Thanks for taking the time to report this.


Cheers,

Remco
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.030 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download