2BizBox® Manual

2.5 FAQ

2.5.1 How to deal with "Unable to create connection" 

Some users may experience failed login and encounter the prompt:  "Unable to create connection, the server program is running or port is occupied." There may be several reasons for this, check carefully below for the correct one.

• The connection is too fast. When logging in, it will take several minutes to enter the system, because the time that 2BizBox Server startup takes is longer than 2BizBox Client start up takes, so wait for at least one minute to login. It should be successful.    
• Server port conflict. This occurs a lot. A lot of software, like Skype, MSN, Thunder, SQL SERVER, IIS, etc. may occupy the 2BizBox port. If you cannot confirm which software takes up the port, go to Windows Start - Run - Execute cmd, and then in the DOS command window, execute:  nestat-ano | findstr ":  2BizBox software port \>"

Check exactly which process is taking up the 2BizBox port. When discovered, note the PID process number. Then, in the Task Manager, click “View" -> "Select Columns, “check the PID (process identifier), find the corresponding process, directly delete it, and then try to restart the server. If system prompts:  ‘netstat’ is not recognized as an internal or external command, operable program or batch file

 First, take a look if there is "netstat.exe" or not. Then look if there is "C:  \ windows \ system32;" under “My Computer" - "Properties" - "environment variable.”

• Insufficient physical memory. Carefully observe the black window of the server; if there is no rolling log, but a prompt like the Java virtual machine error unable to start appears, it is likely that the physical memory is insufficient. Check your PC's memory, then try to login with at least 1G of memory.
• 2BizBox server fails to start or closes when startup finishes. Keep the 2BizBox server running while logging in and using 2BizBox Client.  

2.5.2 Environment variable settings note

This problem is common for servers installed by GHOST. If the image below appears, a new variable “systemroot” must be created under “My Computer""environment variable" first. If the operating system is 2000, the systemroot value is C:  \ WINNT. If the operating system is from XP to Win7, then the value is C:  \ windows; also add this information after the path: % systemroot% system32; % systemroot%. Finally, restart the server.