FitClient: external process terminated before a connection could be established

Question

On executing a simple Fitnesse test, I am getting the error :

"FitClient: external process terminated before a connection could be established."

On the Fitnesse server, the error is:

"software caused connection abort socket write error"

.Net version used - 4.0

The contents on the page :

!define COMMAND_PATTERN {%m -r fitnesse.fitserver.FitServer, dotnet2\fit.dll %p}
!define TEST_RUNNER {dotnet2\Runner.exe}

Has anyone encountered this issue and also can anyone let me know how this can be fixed

Error

System.ArgumentException: String cannot have zero length. at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile) at fitSharp.Machine.Engine.CurrentDomain.LoadAssembly(String assemblyPath) at fitSharp.Machine.Engine.ApplicationUnderTest.Assemblies.AddAssembly(String assemblyName) at fitSharp.Machine.Application.Shell.Execute() at fitSharp.Machine.Application.Shell.Run(IList`1 commandLineArguments)

Answer 1

I've been getting this same message for an absolutely trival test:

!path lib/*.jar

I was running DbFit for the first time.

I turned on verbose logging by including -v in the .bat file as follows:

java -cp "lib\dbfit-docs-3.2.0.jar;lib\fitnesse-20150424-standalone.jar" fitnesseMain.FitNesseMain -v %*

and noticed that there were spaces in the path showing up in the 3rd parameter in the Starting Process parameter list of .jar files. This was causing the initial call to fitnesse to fail, which resulted in the error message.

I fixed this by moving my DbFit installation to a folder without spaces: C:\dbfit. This resolved the issue.

On to the next issue now...

Hope that helps someone.