This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
NB Build: NetBeans Dev Build 200805130003 Sailfin Build:b32 (https://sailfin.dev.java.net/downloads/downloads.html#Promoted_binary_builds) JDK Build :jdk1.5.0_13 Steps to reproduce: 1.Install NB Dev.You need to have two servers. 2.I have Silfin 1.0(With Http port:4848-Default domain domain1) 3.I have GF2.1(With Http port:4848-default domain domain1). 4.Right click on the services and register sailfin V1 and give platform location for the sailfin.Select Next>Next>Finish. 5.Right click on the services select Sailfin V1.(Registering second server with local domain) 6.Select " Register local domain" in the dialog window "Platform folder location".Select Next. 7.Give the Domain folder location(I have given GF 2.1 default domain domain1 as domain folder location), Select Next. 8.Give user name and password, select Finish. 9.Select OK in the dialog window "Could not create Application server" and you can see the caution message "Could not create Instance" in the dialog window "Domain admin login info" and Select Back>Next. On selecting Back>Next caution message disappears. It would be nice to have the information "Could not create instance" even when the user select Back> Next. NOTE:It happens even on typing the user name and password again,instead of selecting Back>Next.
the j2eeserver layer is the code sending the message... it is because you are trying to register two servers with the same deployment URL. The fix would be to extend the deployment URL to include the path to the domain directory AND the install location for the server bits. can prevent/resolve in the v3 plugin. unlikely to be addressed in the v2 plugin.
NetBeans.org Migration: changing resolution from LATER to WONTFIX