Sun hardware UE450 server boot cdrom and openboot issues

I am trying to newly install a Sun Ultra Enterprise 450 Server with Solaris 10. boot cdrom does not work. I read the 2 manuals on openboot and tryed a few things. I replaced the cdrom player with the same model: Toshiba XM-5701B 12X.
The cdrom lit up but the system did not boot.
The alias is set to : /pci@1f,4000/scsi@2/cdrom@6,0:f
I set the cdrom text from disk and tryed a few other addresses and added file names found on the cd but nothing helped.
I did not find information that states that the alias is set automatically and also not what to set it to.
Checksum on the CD vol 1 was OK. CD's burned on two CD-Burners showed the same results for some tests.
Boot with diag-switch? set to true showed errors. There are no problems up to the appearance of the ok prompt.
What can I set the cdrom alias to?
Is my system possibly too faulty to start?

This message has 2 posts. The first one was sent unintentionnaly. I sent it again with my completion and could not delete or modify the first one.
The rest is as follows:
Checksum on the CD vol 1 was OK. CD's burned on two CD-Burners showed the same results for some tests.
Boot with diag-switch? set to true showed errors. There are no problems up to the appearance of the ok prompt.
What can I set the cdrom alias to?
Is my system possibly too faulty to start?
The behaviour at the boot prompt varied. Many of the attempts resulted in a dead prompt.All attempts started with the initialization of memory. This is not a test I believe.
Some attempts resulted in "File Args" being displayed. Some others returned the boot prompt after doing nothing.
I would have to go through the procedure again in order to give exact details.
Diagnoses show memory errors. The progress of the memory test was so long that I stoped it. A message said that there was a problem with a certain pin.
test-scsi showed errors in one scsi some times and other times no errors.
What CD-Model would you suggest. Possibly one in an external unit. There are a few available on www.ebay.com.

Similar Messages

Windows 2008 Server boot loop and unable to log on in Safe mode

The Situation: I used msconfig to reboot Windows 2008 Server r2 into safe mode. On rebooting, boot progresses ok and the log in screen appears very quickly, then disappears and the machine reboots. I've tried typing the password very quickly and whether
I get it wrong or just can't get enough typed in time, I don't know, but the reboot loop continues. So, i can't log on and can't change safe boot back to normal.
I know Server 2008 uses bcdedit and no longer has a boot.ini, so I don't know if it is still possible manually to amend a boot file so it starts in normal mode again. Can anyone help me to break out of this boot loop without having to resort to anything
major, such as reinstallation?
Just to make clear, I haven't updated the system and the only change made was with msconfig to require safe boot on restarting.
Thanks

from the safemode try this syntax
Syntax: bcdedit /deletevalue {default} safeboot
http://technet.microsoft.com/en-us/library/cc721886(WS.10).aspx
http://www.virmansec.com/blogs/skhairuddin
How on earth is that a good answer? Sorry for the necrosis here of bringing up a post 9 months later, but I just ran in to this issue again. The OP said that he was STUCK IN A BOOT LOOP having placed himself in SAFEMODE already.
How is he supposed to type this in if he can't log in?
What worked for me was to keep striking F8 like a cobra during boot and telling it to use the Last Known Good Configuration option, after the 4th autoreboot, it let me log in and let me switch it back out of the safe mode and back to the normal boot. Yes,
I am aware this is quite lucky and now I don't have to rebuild all my server set up, and that your mileage may vary here, but, keep trying, you might be lucky.

Sun ONE Web Server 6.1SP5 and Communications Express Error

I post this to the wrong forum i think i am getting this error after running the config-uwc.
Sun ONE Web Server 6.1SP5 B06/23/2005 22:22
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_04] from [Sun Microsystems Inc.]
config: for host 0.0.0.0 trying to GET /, name-trans-passthrough reports: init-passthrough has not been called
info: WEB0100: Loading web module in virtual server [https-proxy1.mrc.ac.za] at [da]
info: WEB0100: Loading web module in virtual server [https-proxy1.mrc.ac.za] at [uwc]
info: WEB0110: Ignoring invalid property [allowLinking] = [true]
info: WEB0100: Loading web module in virtual server [https-proxy1.mrc.ac.za] at [search]
warning: CORE3283: stderr: Exception in thread "Thread-1" java.lang.NoClassDefFoundError: org/mozilla/jss/crypto/KeyGenAlgorithm
warning: CORE3283: stderr: at java.lang.Class.forName0(Native Method)
warning: CORE3283: stderr: at java.lang.Class.forName(Class.java:164)
warning: CORE3283: stderr: at com.iplanet.services.util.Crypt.createInstance(Crypt.java:133)
warning: CORE3283: stderr: at com.iplanet.services.util.Crypt.<clinit>(Crypt.java:103)
warning: CORE3283: stderr: at com.iplanet.services.ldap.LDAPUser.getPasswd(LDAPUser.java:117)
warning: CORE3283: stderr: at com.iplanet.services.ldap.ServerInstance.getPasswd(ServerInstance.java:128)
warning: CORE3283: stderr: at com.sun.identity.security.ServerInstanceAction.run(ServerInstanceAction.java:92)
warning: CORE3283: stderr: at java.security.AccessController.doPrivileged(Native Method)
warning: CORE3283: stderr: at com.iplanet.am.util.AdminUtils.<clinit>(AdminUtils.java:82)
warning: CORE3283: stderr: at com.sun.identity.security.AdminDNAction.run(AdminDNAction.java:86)
warning: CORE3283: stderr: at java.security.AccessController.doPrivileged(Native Method)
warning: CORE3283: stderr: at com.sun.identity.authentication.internal.server.SMSAuthModule.initialize(SMSAuthModule.java:129)
warning: CORE3283: stderr: at com.sun.identity.authentication.internal.LoginContext.login(LoginContext.java:122)
warning: CORE3283: stderr: at com.sun.identity.authentication.internal.AuthLoginThread.run(AuthLoginThread.java:82)

I reran the access manager configuration and deployed it to the web server and now the webserver starts up successfully. I think my problem was that the file I was using initially wasn't properly setup for my enviroment.
Carinus

Sun Java Application Server 9.0 and 9.1 - High CPU PROCENTAGE 100%

Hi,
I have problem with sun java application Server running after few days during watching a logs from web admin suddenly the application server takes 100% cpu and keeps this procentage - I have to manually close the server process.
The server running on Windows Server 2003.
Anyone have any idea to sovle the problem?

Hi Kedar,
Thanks for the reply. Yes, I finally figured it out.
The custom MBeans seem to work well for the most part though I don't know for sure if I'm using them in the way they were really intended.
Basically, I want to run 'services' on my application server for the lifetime of the server. I want these 'services' to maintain things like runtime caching of information over time that is not persisted in a DB but needs to be kept around in active memory to be used at a later time, but only while the application server is up and running.
Another thing I would like to do is have them receive JMS notifications directly, but I seem to be having trouble when subscribing as a consumer within my custom MBean. The topic thread on that is here:
http://forum.java.sun.com/thread.jspa?threadID=5153124&tstart=0

Sun ONE Web Server 6.1 and Beans

Hello,
I am learning JSP and I have a new install of Sun ONE Web Server Enterprise Edition 6.1. I have a some java code (a class) I would like to use in my JSP page via <jsp:useBean...>.
Where do I put my .java (or compiled .class) file?
For example: UserData.class
Thanks,
Michael

Thanks for the reply.
Under my <appdir> I created a WEB-INF and classes directries. I copied my .class file to it but still get the message in the Sun One 6.1 error log:
C:\Sun\WebServer6.1\https-titan\ClassCache\https-titan\default-webapp\_jsps\_apps\_bean1\_SaveName_jsp.java:66: package user does not exist
user = (user.UserData) java.beans.Beans.instantiate(this.getClass().getClassLoader(), "user.UserData");
^
I am so new - what else can you recommend?
Thanks again,
Michael

Sun ONE Web Server 6.1 and p6spy integration

Has anyone successfully integrated p6spy with Sun ONE Web Server on a Windows platform? If so, any help would be greatly appreciated.

Y follow your steps (they seem correct for me too) and I get:
warning: CORE3283: stderr: Warning: Could not set property setStringmatcher due
to InvoicationTargetException
warning: CORE3283: stderr: Warning: Error registering factory [com.p6spy.engine
.logging.P6LogFactory]
warning: CORE3283: stderr: Caused By: java.lang.ClassCastException
warning: CORE3283: stderr: com.p6spy.engine.spy.P6DriverNotFoundError: Error reg
istering factory [com.p6spy.engine.logging.P6LogFactory]
warning: CORE3283: stderr: Caused By: java.lang.ClassCastException
warning: CORE3283: stderr: at com.p6spy.engine.spy.P6SpyDriverCore.initMeth
od(P6SpyDriverCore.java:289)
warning: CORE3283: stderr: at com.p6spy.engine.spy.P6SpyDriver.initMethod(P
6SpyDriver.java:78)
warning: CORE3283: stderr: at com.p6spy.engine.spy.P6SpyDriver.<clinit>(P6S
pyDriver.java:74)
warning: CORE3283: stderr: at java.lang.Class.forName0(Native Method)

Sun ONE Web Server 6.0 AND jre 1.6

I am using Sun ONE Web Server 6.0 Service Pack 11. Can I upgrade my JRE version to 1.6? Currently I am using 1.5. Your response will be much appreciated?

I am using external JRE. I have already installed it.
When I type java -version on /usr/iplanet/servers/bin/https/jre/bin, I am getting Java(TM) SE Runtime Environment (build 1.6.0_16-b01). My question is, will it cause any issues when I run my application? Has sun specified like JRE 1.6 should be used on Sun ONE Web Server 6.1 onwards only?

Server 2012 R2 And Hypervisor Issues

Im having some issues and Supermicro customer support is not being very helpful. Anyone have any thoughts on this.
Please see below:
I have a SC846e1:
MB: X8DTE-F
PR: x5660 (2)
Mem: 32gig Samsung EEC 1333
Raid: adaptec 6805 (slot 4)
OS:Samsung 850pro SSD (2) (direct to the raid card, raid 1)
Files: HGST 3tb NAS (6) (enhanced JBOD) (using StableBit BD to pool)
I am trying to enable Hyper-V on a new build with Server 2012r2. I have added the role and it caused a boot loop which I found to be due to having "execute-disable bit capability" enabled. I disabled this and it booted up but hypervisor will
not start and states that virtualization and
execute-disable must be turned on.
I have reset the bios to "optimal defaults" and have only changed: (did a complete power off to validate change)
numlock: disabled
execute-disabled: disabled (due to boot loop)
IPMI: configured
There is also a mention in the error for hypervisor not starting that states that
vt-d and
trusted execution must be disabled.
VT-D: is confirmed to be disabled
Trusted execution: cannot be found which i believe is TPM which is not showing up in he bios and while looking at the manual and board can only find a TPM header but no jumper to disable it as per the instructions in the manual. (Manual states to disable
TPM with a jumper)
Is TPM what is causing my issue? and causing the boot loop when execute-disabled enabled?
Also checked boot loader and hypervisorlaunchtype: Auto
Any assistance you can provide would be greatly appreciated
Long Story short....I have reformatted and reinstalled with no changes before implementing the role. once the role is implemented and then rebooted it goes into a boot loop that can only be stopped is when BITS is disabled. Supermicro has no idea why it would
be having a boot loop and the VT-D should be enabled. Ive tried it both ways with no effect.

only thing custom is the config. all parts support visualization.
SC846e1:(Supermicro)
MB: X8DTE-F
PR: x5660 (2)
Mem: 32gig Samsung EEC 1333
Raid: adaptec 6805 (slot 4)
As far as cold boots ive pulled the plug and discharged the power no change. almost seams like a driver issue. most up to date driver on the adaptec 6805 but using OS drivers for chipset and nics as they are most recent.
Ive recompiled mofs ive done about all i can think of short of lighting it on fire. :)

My sun java application server not run and give me error

hi master
sir i use
sun java system with studio creator but when i start deployment server
that give me this error
==================
The sun java system application server 8.2 could not start.
more information about the cause is in the server log file .
possible reasons include:
-Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
-Incorrect server configuration (domain.xml to be corrected muanually)
-Corrupted Deployed Application preventing the server to start.(this can be seen in the server.log file. in the case, domain.xml needs to be modified).
==========
this is my server.log file
=======
[#|2007-10-23T09:43:55.144+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T09:58:09.886+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T10:12:34.768+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T11:10:28.081+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T12:58:46.034+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
please how i start my application server
thank's
aamir

Please see the following FAQ:
Why doesn't application server Start.
http://developers.sun.com/jscreator/reference/faqs/technical/depsrvs/index.jsp

Sun ONE Portal Server 6.0 and struts.

Hi all,
Has anyone tried using struts with Portal Server?
Can we use/migrate struts application to Portal Server 6.0?
As far as I know both uses one gateway servlet.
Pelase reply.
Thanks.

Hi,
The problem with integration of struts based
applications is usually the project funding :-)
There is no generic struts provider, only some
custom build pieces...
I guess that is the reason, why "zero effort" proxy
of a struts application via IFrame channel is the
most implemented integration.
Cheers,
Alex :-)

Task Sequence Windows Server 2012 format and partition issue when using MDT2012

Hi all,
Currently I'm working on a task sequence to deploy a Windows Server 2012 image. We've integrated MDT2012 Update 1 in SCCM2012 SP1 and created a default 'Server Task Sequence'. This task sequence deploys the install.wim to a server which has multiple disks
attached.
We've configured multiple format and partition disk steps to create the following partition layout:
Disk 0: 499MB BDEDrive (do not assign drive letter) + 40GB OSDisk
Disk 1: 40GB Programs
Disk 2: 40GB Data
Disk 3: 25GB User
When the task sequence is finished I've noticed the drive letters assigned to the disk are not correct. In some cases the BDEdrive gets drive letter D assigned, sometimes drive letters are assigned starting with E, thus skipping drive
letter D.
The smsts.log files show an error when it's re-assigning drive letters after booting into Windows. Looks like an error in the DiskPartScript.txt.
<![LOG[==============================[ OSDSetupHook.exe ]==============================]LOG]!><time="16:59:40.889-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="osdsetuphook.cpp:186">
<![LOG[Executing task sequence]LOG]!><time="16:59:40.905-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="osdsetuphook.cpp:279">
<![LOG[Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".]LOG]!><time="16:59:40.920-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="basesetuphook.cpp:366">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="16:59:40.936-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="environmentscope.cpp:659">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="16:59:40.936-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="environmentscope.cpp:659">
<![LOG[Debug shell is enabled]LOG]!><time="16:59:43.806-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="basesetuphook.cpp:1440">
<![LOG[Successfully enabled debug command shell support.]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="debugwindow.cpp:156">
<![LOG[Configuring local administrator account]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="basesetuphook.cpp:1462">
<![LOG[Re-assign all drive letters...]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="diskutils.cpp:1941">
<![LOG[Executing command line: "C:\WINDOWS\system32\diskpart.exe" /s "C:\WINDOWS\TEMP\DiskPartScript.txt"]LOG]!><time="16:59:43.900-120" date="05-10-2013" component="OSDSetupHook" context=""
type="1" thread="776" file="commandline.cpp:827">
<![LOG[Process completed with exit code 2147942487]LOG]!><time="16:59:50.249-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="commandline.cpp:1123">
<![LOG[Diskpart.exe STDOUT:
Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: SRV03
Volume 1 is the selected volume.
DiskPart successfully removed the drive letter or mount point.
The volume you selected is not valid or does not exist.
There is no volume selected.
]LOG]!><time="16:59:50.249-120" date="05-10-2013" component="OSDSetupHook" context="" type="3" thread="776" file="diskutils.cpp:1807">
When I take a look at the generated diskpart_script.log file the volume D gets selected twice, which fails the second time because of the first remove drive letter command.
This is the output in the diskpart_script.log file:
select volume D
remove letter=D
select volume D
remove letter=D
select volume E
remove letter=E
select volume F
remove letter=F
select volume H
remove letter=H
select disk 0
select partition 1
assign
select disk 1
select partition 1
assign
select disk 2
select partition 1
assign
select disk 3
select partition 1
assign
It seems this error is caused by the first 'Format and Partition Disk' step before the 'Use Toolkit Package' step which is part of the default Server Task sequence. When I disable this Format and Partition step and create the partition manually
all looks ok showing no errors in the smsts.log file.
I've solved this by replacing the first 'Format and Partition Disk' step by an Powershell command which formats and partitions the disk.
Anyone seen this behavior?

I have a similar problem when I install windows on some clients. Have you found any explanation for the behavior?

SQL Server Database backup and restore issue

Hi
I am trying to take a backup of the database and using restore to create its copy on the same server
Basically I am following this approach
http://stackoverflow.com/questions/3912221/ms-sql-2008-create-a-copy-of-the-database-without-the-data
Using the restore command is giving me the following error
RESTORE DATABASE [TargetDB]
FROM DISK = N'D:\backup.bak' WITH FILE = 1,
MOVE N'OriginalDB' TO N'D:\sql data\TargetDB.mdf',
MOVE N'OriginalDB' TO N'C:\SQL Data\TargetDB_1.ldf',
NOUNLOAD, STATS = 33
Logical file "ORIGINALDB" is not part of database "TARGETDB" . Use RESTOREFILELIST only to list
plz suggest as I checked the syntax is fine too as per
https://technet.microsoft.com/en-us/library/ms190447%28v=sql.105%29.aspx
I am using SQL Server 2012

LogicalName cant be same for mdf and ldf. verify again with FILELISTONLY. Also you have put wrong logical name
MOVE N'OriginalDB' TO N'D:\sql data\TargetDB.mdf'
Please paste the output of
RESTORE FILELISTONLY FROM DISK = 'D:\backup.bak'

Exchange server 2013 send and received issue

Hi Support,
I have install Exchange Server 2013 with server 2012 ( my domain not resisted but mail send & received in local for practice then live ) but few days back some changes in dns and ecp and mail stop sending and receiving. how to verify my exchange server
2013 working fine. Please give the step check perpoes.

dear Pardeep, you said it was working fine then you did some DNS changes..
i would suggest you best troubleshooting step is to go to exrca.com and perform the tests and from there we take it up.
Secondly you can verify your config from the below link.
http://www.techieshelp.com/exchange-2013-step-by-step-configuration/
in DNS you need to make sure you have atleast MX and A record done for your server having email services installed.
for ECP... i would we would take this later lets check the mail sending and receiving first. use the above links
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Airport Not Working on boot Up and Intermittent Issue.. please help...

Hi everyone.
Im having problems with airport at the moment.
Every time I boot up the computer i cant seem to connect to the internet.
Im using a wireless connection and can connect fine through my iphone, xbox etc.
It seem I have to turn airport on and off a few times and it works after about 5 minutes. I cant even login to the router.
Sometimes it will stop working while I am online (the airport in the top right stays black)
This used to work a lot better than this and I am confused as to what the problem may be.

I am having the same issues...

Boot Problems and memory issues on MSI k9a2 plat

I have problems booting after doing a bios flash. Gives me a error of bad checksum. Can't save any settings. I got to flash bios back to 112 so wanna know what is the CORRECT way to reboot/ clear cmos /or do i just restart.
Also my memory do not wanna run in dual channel. Will look for book of PSU to see ratings.
MODS sorry for going onto other people threads but thought due to me having same issues that it better to post there.

Read Moan Guide
You use Phenom CPU?(My guess according to my )
Read here: https://forum-en.msi.com/index.php?topic=113143.msg846972#msg846972

Sun hardware UE450 server boot cdrom and openboot issues

Similar Messages

Maybe you are looking for