Starting the application server PE on windows XP

Question

Introduction
I installed JStudio Enterprise 8 with SJS AppServer 8.1
Later uninstalled JStudio Enterprise 8 but the server directory ie C:\Program Files\Sun\jstudio_ent8\Appserv8.1UR2\ remained intact.
The server icon had been removed from the windows startup menu but the server could still be started via the command line
Later installed JStudio Enterprise 8.1 with SJS AppServer 8.2
Installation directories are C:\Program Files\Sun\jstudio_ent81 and C:\Sun\AppServer respectively
After installation I opend a project created using JStudion Enterprise 8 and on trying to run the project I recieved the error below:
[#|2007-02-24T14:30:10.860-0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|
Service [email protected] cannot be started! : com.sun.appserv.server.ServerLifecycleException:
Cannot bind to URL [rmi://localhost:8686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: java.net.SocketTimeoutException: Read timed out]|#]
Please note that the program ( right from the JStudio Ent 8) often complained that spaces had been detected in the class path.
However everything still went on smoothly.
Actions Carried Out
I used asadmin change-master-password --savemasterpassword=true to change password
I used netstat -a to confirm that the port 8080 and other ports as contained in domain.xml were not already in use by the OS
I uninstalled JStudio Ent 8.1 and JDK 5 with JRE, deleted the application files (eg .jstudio folder, .asadmintruststore file etc) I found in user directory
D:\Documents and Settings\user and reinstalled the above mentioned software. Subsequently I tried running a skeletal Enterprise Application but recieved same error.
I used asadmin verify-domain-xml and got the following result:
25-Feb-2007 09:52:30 com.sun.enterprise.config.serverbeans.validation.DomainXMLVerifier invokeConfigValidator
SEVERE /domain[1]/configs[1]: Assertion failed: There is a config element named "default-config"
Despite the above actions and continous trials the server would not start under the JStudioIDE
The server however starts under the command line with the message:
Domain domain1 is ready to receive client requests. Additional services ae being started in background.
However the server would not serve web pages when requested via Internet Explorer. When one eventually tries to stop the server the following message is displayed:
The domain (domain1) isn't running
CLI157 Could not stop domain domain1
Also, I haven't been able to use the admin console for the server and previously for Macromedia ColdFusion Mx v 6.1 Developer
General Info
System web root folder = D:\inetpub\wwwroot\
Java Installed = JDK 5 update 11 with JRE 5 update 11
Product Info
Sun Java System Application Server 8.2 Bundled with JStudio Enterprise Edition 8.1
No patches
System Info
OS Name          Microsoft Windows XP Professional
Version          5.1.2600 Service Pack 2 Build 2600
Processor          x86 Family 6 Model 9 Stepping 5 GenuineIntel ~1495 Mhz
Total Physical Memory     512.00 MB
Available Physical Memory     194.32 MB
Total Virtual Memory     2.00 GB
Available Virtual Memory     1.96 GB
Page File Space     1.22 GB
Page File          D:\pagefile.sys

Answer 1

I take it that you would like to run JSE8.1 with AS8.2. Is that right? Or would you like to run both JSE8 and JSE8.1 simultaneously?
One thing to check for the userdir; the userdir should be different for different ide installs. By default of course this should be the case, but one possibility here is that the userdir could be corrupted.
Can you please try with a fresh userdir and see if things work?
Ref: http://blogs.sun.com/karthikr/entry/jse_directories
Also, can you check the server log files? From within the ide, right-click on the server in runtime tab and select 'view server log'. Or cd to <appserver_dir>/domains/domain1/logs directory and check the server.log to see if there are any error messages that may be of help in diagnosing the problem.