I’m using JBoss 4.0.5 GA on Windows 7 with Java version 1.5 (I have to use older java version and a JBoss because I’m working with a legacy system). And when I’m starting the server I get the following error:
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
And I believe this causes many other exceptions:
11:09:26,925 WARN [ServiceController] Problem starting servicejboss.cache:service=TomcatClustering Cache
java.lang.NullPointerException
at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:235)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.FD.down(FD.java:278)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.stack.Protocol.down(Protocol.java:540)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:297)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.UNICAST.down(UNICAST.java:262)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:292)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.pbcast.GMS.down(GMS.java:605)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.FC.down(FC.java:122)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.FRAG2.down(FRAG2.java:146)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.Protocol.passDown(Protocol.java:510)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:217)
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:467)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:331)
at org.jgroups.JChannel.down(JChannel.java:1035)
at org.jgroups.JChannel.connect(JChannel.java:374)
at org.jboss.cache.TreeCache.startService(TreeCache.java:1424)
at org.jboss.cache.aop.PojoCache.startService(PojoCache.java:94)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:619)
I greatly appreciate if anyone could help. At least to figure out where I should look for the solution (e.g. Is this an error related to windows 7 and JBoss clustering incompatability? Is this because of a wrong port configuration? etc.)
Thanks.
asked Oct 16, 2010 at 3:28
2
This problem occurs on some Windows systems that have the IPv6 TCP Stack installed. If both IPv4 and IPv6 are installed on the computer, the Java Virtual Machine (JVM) may have problems closing or opening sockets at the operating system level.
Add the following JVM option: -Djava.net.preferIPv4Stack=true
I’ve seen this happen on Windows 7 and Windows 2008 systems which have both IPv4 and IPv6 stacks installed by default.
Code Lღver
15.5k16 gold badges56 silver badges75 bronze badges
answered Mar 14, 2012 at 16:36
6
You have very likely another process already bound on a port that JBoss is using (8080?) and this prevent JBoss from starting correctly (see this page for a list of ports used by JBoss).
Either find the conflicting process and shut it down:
- use
netstat -a -o -nand look for ports used by JBoss (e.g. 8080) and the correspondingpid - then use
tasklist /FI "PID eq <pid>"to find the process
Or change JBoss defaults ports. There are several ways to do that but the best way is to use the Service Binding Manager (see detailed instructions in Configuring Multiple JBoss Instances On One Machine).
answered Oct 16, 2010 at 21:30
Pascal ThiventPascal Thivent
557k134 gold badges1057 silver badges1119 bronze badges
3
I ran into the same issue on Win7 trying to implement the example here:
http://download.oracle.com/javase/tutorial/networking/sockets/clientServer.html
The default port in the example code is 4444. Using this port I got
«Unrecognized Windows Sockets error: 0: JVM_Bind»
I changed the port to 44444 and tried again. I got a popup from the Windows Firewall service asking me if this application had permission to access the network. Selecting OK I no longer get the error message when I launch my server.
After some experimenting I found that with a port of 5000 or less I would get the JVM_Bind error. Any port of 5001 or above would bind without issue.
answered Aug 18, 2011 at 19:10
efeltonefelton
1713 silver badges9 bronze badges
0
I had similar problem. I used process-xp and kill javaw.exe, then restart the application. It works for me.
answered Feb 25, 2011 at 9:18
It’s problem of JAVA 32/64 bit. try run your jar with 32 bit JVM
answered Jun 6, 2012 at 16:36
I was having this issue with my Tomcat and it turned to be a port conflict with Skype. In my Skype->Options->Advanced->Connection I unchecked the following «Use port 80 and 443 as alternatives for incoming connections». This solved the problem completely.
answered May 3, 2013 at 13:25
Artem KhojoyanArtem Khojoyan
8471 gold badge6 silver badges10 bronze badges
this solved my problem 
Add the following JVM option: -Djava.net.preferIPv4Stack=true
answered May 28, 2013 at 10:24
niknik123niknik123
1791 silver badge7 bronze badges
open command prompt as administrator. Then do a netsh winsock reset
answered Jun 19, 2017 at 18:18
PijushPijush
3974 silver badges3 bronze badges
I had the same issue with Tomcat on Windows 10. Added this to the catalina.bat file near the top:
SET JAVA_OPTS=-Djava.net.preferIPv4Stack=true
Stephen Rauch♦
46.7k31 gold badges109 silver badges131 bronze badges
answered Oct 2, 2017 at 5:54
I know this is an old issue, but I’ve just recently figured out one cause of the issue, as well as the solution. My server socket program worked fine until I put the code into a loop, then I got the error Unrecognized Windows Sockets error: 0: JVM_Bind on every attempt to accept() after the first attempt. I had code like this:
ServerSocket ssock = null;
Socket sock = null;
while (loopCount < loopLimit) {
ssock = new ServerSocket(port);
ssock.setSOLimit(millis);
sock = ssock.accept();
// some code here...
loopCount++;
}
It was only when I put ssock = new ServerSocket(port) and ssock.setSOLimit(millis); above the loop that I eliminated the error.
dandan78
13.1k12 gold badges63 silver badges78 bronze badges
answered Jan 31, 2012 at 19:05
JCoopJCoop
111 silver badge3 bronze badges
I hade to add SystemRoot parameter in java parameters. I dont don’t know why java doesn’t have this parameter. It was working before. With
SystemRoot=C:Windows
it works.
I execute the java as Windows service nssm.
answered Feb 5, 2020 at 9:17
bilginbilgin
1231 silver badge13 bronze badges
I’m not entirely sure if I compacted this well enough, but after class declaration and method calling, it is essentially what my program does.
Server server = new Server(); // Creates a ServerSocket and binds it to a port.
Client client = new Client(server.getSocketAddress());
public Client(SocketAddress bind)
{
try
{
socket = new Socket();
socket.bind(bind); // Problem here
recieve = new Scanner(socket.getInputStream());
send = new Formatter(socket.getOutputStream());
}
catch (IOException e)
{
e.printStackTrace();
}
}Running the above code produces the following exception.
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.Socket.bind(Unknown Source)
at GameObjects.PlayArea$Client.<init>(PlayArea.java:318)
at GameObjects.PlayArea.<init>(PlayArea.java:48)
at MenuStates.GamePlayState.initializePlayArea(GamePlayState.java:90)
at MenuStates.CreateGameState.mouseClicked(CreateGameState.java:106)
at Manager.GameManager.mouseClicked(GameManager.java:428)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Window.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)I don’t even know what this exception is, and I can’t find anything that will really tell me what is going on. Can anyone tell me what is happening here?
I know that this question isn’t directly related to Game Development, but I am using it in a game program, and I posted this question in the Network forum, and they flooded my topic with useless messages, and the only person who actually answered my question was extremely vague about it, even after I asked him to clarify. I am hoping that the good people of this forum will be more helpful.
Ranch Hand
Posts: 82
posted 11 years ago
-
-
Number of slices to send:
Optional ‘thank-you’ note:
-
-
Hello,
I’ve developed a client/server application to send datagram packets and receive them through the UDP protocol using two classes
this is the Server class
this is the Client class
The problem is that when i try to run the server class from the command prompt :
javac Server.java
// this works well but when i try to run it using this command:
java Server
//it throws this exception:
Exception in thread «main» java.net.SocketException: Unrecognized Windows Sockets error: 0: Cannot bind
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:82)
at java.net.DatagramSocket.bind(DatagramSocket.java:368)
at java.net.DatagramSocket.<init>(DatagramSocket.java:210)
at java.net.DatagramSocket.<init>(DatagramSocket.java:261)
at java.net.DatagramSocket.<init>(DatagramSocket.java:234)
at Server.main(Server.java:8)
How can i get rid of this problem?
thanks in advance
I Hear I Forget, I See I Remember, I Do I Understand.
posted 11 years ago
-
-
Number of slices to send:
Optional ‘thank-you’ note:
-
-
I Googled the error and a couple of items suggested that the port is already in use. I noticed that your server loops forever and does not clean up after itself (by calling DatagramSocket.close). Could it be that another instance is already running? Or maybe not cleaning up caused the port to remain open? Or perhaps another application is using that port? Try using another port or rebooting to close the existing port (both easy tests).
I tried running your server and got a different error (Address already in use) when I tried running it a second time but I’m not running on Windows.
Roger Fed
Ranch Hand
Posts: 82
posted 11 years ago
-
-
Number of slices to send:
Optional ‘thank-you’ note:
-
-
Thanks tom , this is already the case
I’ve reboot it and it it works well
I Hear I Forget, I See I Remember, I Do I Understand.
Versions (Unresolved/Resolved/Fixed)
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Test run with:
java version "1.6.0_10-ea"
Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b07)
Java HotSpot(TM) Client VM (build 1.6.0_10-ea-b07, mixed mode)
Steps to reproduce:
1. Install the kernel jre "*windows-i586-p-iftw-k.exe"
2. Make sure run the test from kerneljre's "initial form"
(either immediately(before Kernel has time to finish background downloading)run test after install, or perform step 3 4)
(optinal)3. Kill the background download ( by killing the "java" process )
(optinal)4. Remove all files under ${ProgramFiles}/Java/jre6/lib/bundles/
5. Run following test : java Test
Test should throw BindException, but it threw "java.net.SocketException: Unrecognized Windows Socket
s error: 0: Cannot bin", see the output "output for the first run"
6. Run again: java Test
Test pass this time ( with all needed components alread downloaded/installed after first time run ), and threw expected BindException, see the output "output for the second run"
This test also "pass" with normal jdk/jre. But fail if run from "initial form" kernel jre.
---- Test.java -----
import java.net.*;
import java.io.*;
public class Test {
public static void main(String args[]) throws Exception {
DatagramSocket s1 = new DatagramSocket(null);
s1.bind( new InetSocketAddress(5889) );
DatagramSocket s2 = new DatagramSocket(null);
try {
int port = s1.getLocalPort();
System.out.println("Try to bind again on " + port );
s2.bind( new InetSocketAddress(port) );
System.out.println("Test failed.");
} catch (BindException e) {
System.out.println("Test passed. Got expected BindException");
e.printStackTrace();
}
s2.close();
s1.close();
}
}
---- output for the first run ----
Try to bind again on 5889
Exception in thread "main" java.net.SocketException: Unrecognized Windows Sockets error: 0: Cannot bind
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:82)
at java.net.DatagramSocket.bind(DatagramSocket.java:368)
at Test.main(Test.java:25)
---- output for the second run ----
Try to bind again on 5889
Test passed. Got expected BindException
java.net.BindException: Address already in use: Cannot bind
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:82)
at java.net.DatagramSocket.bind(DatagramSocket.java:368)
at Test.main(Test.java:25)
- Remove From My Forums
-
Question
-
After downloading Fitnesse (http://fitnesse.org/FrontPage.FitNesseDevelopment.DownLoad) and installing it (java -jar fitnesse.jar) at the commandline, as described on the DownloadingAndIsstallingFitNesse page (http://fitnesse.org/FitNesse.UserGuide.DownloadingAndInstallingFitNesse), I get the following error in the commandline (cmd) of Windows 7 with Java 1.6.0_14-b08:
C:DownloadsSoftware>java -jar fitnesse.jar
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at fitnesse.socketservice.SocketService.<init>(SocketService.java:20)
at fitnesse.FitNesse.start(FitNesse.java:67)
at fitnesseMain.FitNesseMain.runFitNesse(FitNesseMain.java:61)
at fitnesseMain.FitNesseMain.updateAndLaunch(FitNesseMain.java:56)
at fitnesseMain.FitNesseMain.launchFitNesse(FitNesseMain.java:44)
at fitnesseMain.FitNesseMain.main(FitNesseMain.java:27)
Answers
-
Hi Bbrecken,
I would like to suggest you uninstall and reinstall Java from the following link:
http://www.java.com/en/download/manual.jsp
Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product’s performance or reliability.
After that, please refer to the following link to set the PATH environment and reinstall Fitnesse.
http://fitnesse.org/FitNesse.UserGuide.FitNesseWontStart
Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
If it still cannot be installed, you’d better contact Fitnesse Support for more information.
Regards,
Arthur Li — MSFT
-
Marked as answer by
Wednesday, March 10, 2010 6:57 AM
-
Marked as answer by