Startup of commerce server 3.5 generates errors.

I get the errors below when I start commerce server 3.5. What could be wrong?
Joseph.
bash-2.03$ StartCommerce.sh
using CLASSPATH of /opt/wl6/WebLogicCommerce3.5/lib/weblogic601sp1_ef.jar:/opt/wl6/WebLogicCommerce3.5/lib/jdom.jar:/opt/wl6/WebLogicCommerce3.5/lib/mail.jar:/opt/wl6/WebLogicCommerce3.5/classes:/opt/wl6/WebLogicCommerce3.5/lib/wlcsparsers.jar:/opt/wl6/WebLogicCommerce3.5/license:/opt/wl6/WebLogicCommerce3.5/eval/Taxware/common/classes:/opt/wl6/jdk130/lib/tools.jar:/opt/wl6/wlserver6.0sp1/lib/weblogic_sp.jar:/opt/wl6/wlserver6.0sp1/lib/weblogic.jar:/opt/wl6/wlserver6.0sp1/lib/xmlx.jar:/opt/wl6/wlserver6.0sp1/ext/weblogic-tags.jar:/opt/wl6/wlserver6.0sp1/samples/eval/cloudscape/lib/cloudscape.jar:/opt/wl6/wlserver6.0sp1/samples/eval/cloudscape/lib/tools.jar:/opt/wl6/wlserver6.0sp1/samples/eval/cloudscape/lib/client.jar
using LD_LIBRARY_PATH of /opt/wl6/WebLogicCommerce3.5/eval/Taxware/solaris/lib:/opt/wl6/WebLogicCommerce3.5/eval/CyberCash/solaris/lib:/opt/wl6/wlserver6.0sp1/lib/solaris
using the "server" virtual machine
## Note: Server initialization may take several minutes.
## Please be patient.
<May 1, 2001 3:33:52 PM EDT> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:password
Starting WebLogic Server ....
<May 1, 2001 3:34:08 PM EDT> <Notice> <Management> <Loading configuration file
./config/wlcsDomain/config.xml ...>
log file: /opt/wl6/WebLogicCommerce3.5/./config/wlcsDomain/logs/weblogic.log
<May 1, 2001 3:34:14 PM EDT> <Info> <Logging> <Only log messages of severity "Error"
or worse will be displayed in this window. This can be changed at Admin Console>
wlcsDomain> Servers> wlcsServer> Logging> General> Stdout severity threshold>
=============== Initializing Logger ======================
/opt/wl6/WebLogicCommerce3.5/tmp_ejbsundevweb7501/document/com/beasys/commerce/axiom/document/fast/SPIFastDocumentManagerImplImpl.java:12:
Superclass java.lang.Object of class com.beasys.commerce.axiom.document.fast.SPIFastDocumentManagerImplImpl
not found.
extends SPIFastDocumentManagerImpl
^
/opt/wl6/WebLogicCommerce3.5/tmp_ejbsundevweb7501/document/com/beasys/commerce/foundation/property/SchemaImplImpl.java:12:
Superclass java.lang.Object of class com.beasys.commerce.foundation.property.SchemaImplImpl
not found.
extends SchemaImpl
^
/opt/wl6/WebLogicCommerce3.5/tmp_ejbsundevweb7501/document/com/beasys/commerce/axiom/document/fast/SPIFastDocumentManagerImplHomeImpl.java:12:
Superclass java.lang.Object of class com.beasys.commerce.axiom.document.fast.SPIFastDocumentManagerImplHomeImpl
not found.
extends weblogic.ejb20.internal.StatelessEJBHome
^
/opt/wl6/WebLogicCommerce3.5/tmp_ejbsundevweb7501/document/com/beasys/commerce/foundation/property/SchemaImplHomeImpl.java:12:
Superclass java.lang.Object of class com.beasys.commerce.foundation.property.SchemaImplHomeImpl
not found.
extends weblogic.ejb20.internal.EntityEJBHome
^
/opt/wl6/WebLogicCommerce3.5/tmp_ejbsundevweb7501/document/com/beasys/commerce/axiom/document/DocumentImplEOImpl.java:12:
Superclass java.lang.Object of class com.beasys.commerce.axiom.document.DocumentImplEOImpl
not found.
extends weblogic.ejb20.internal.EntityEJBObject
^
/opt/wl6/WebLogicCommerce3.5/tmp_ejbsundevweb7501/document/com/beasys/commerce/axiom/document/DocumentImplImpl.java:12:
Superclass java.lang.Object of class com.beasys.commerce.axiom.document.DocumentImplImpl
not found.
extends DocumentImpl

Similar Messages

DR Server not started generating errors

Dear All
i want to start dr server
but it generating error
SQL*Plus: Release 10.2.0.2.0 - Production on Wed Oct 22 09:58:18 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1526726656 bytes
Fixed Size                  2053752 bytes
Variable Size             771754376 bytes
Database Buffers          738197504 bytes
Redo Buffers               14721024 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> shutdown
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 1526726656 bytes
Fixed Size                  2053752 bytes
Variable Size             771754376 bytes
Database Buffers          738197504 bytes
Redo Buffers               14721024 bytes
Database mounted.
SQL> select OPEN_RESETLOGS from v$database;
OPEN_RESETL
REQUIRED
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'G:\ORACLE\PRD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'
SQL>
Please tell how can i resolve that issue........ i want to up DR Immediatly
regards

Hi
execute the below commands in mount mode
SQL>recover database;
then
SQL> alter database open resetlogs;
Raj

Commerce server 3.2 tag library error

I have installed the following components on Solaris 2.7:-
- Java1.3
- WebLogic5.1
- SP6
- Commerce Server 3.2
The commerce server seems to start fine except the following exception
when the Create User button is clicked from the Admin screen. Any help
is appreciated.
Leo
6th Dimension-
Tue Jan 02 11:14:15 PST 2001: <WebAppServletContext-tools> *.jsp:
init
Tue Jan 02 11:14:15 PST 2001: <WebAppServletContext-tools>
FlowManager: init
Tue Jan 02 11:14:26 PST 2001:<E> <WebAppServletContext-tools> Servlet
failed with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
'wl': For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:201)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
at
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
at
weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:181)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:141)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:448)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
Tue Jan 02 11:14:26 PST 2001: <ServletContext-General> servletimages:
init

To be more specific, I put the jar file in the $WEBLOGIC_HOME/lib directory.
-Brad.
"Brad Christiansen" <[email protected]> wrote:
>
I was getting the same exception until I put the weblogic-510-tags.jar file (found in the SP6 zip file) in a directory referenced by the WEBLOGIC_CLASSPATH environment variable.
-Brad.
Leo Fu <[email protected]> wrote:
I have installed the following components on Solaris 2.7:-
- Java1.3
- WebLogic5.1
- SP6
- Commerce Server 3.2
The commerce server seems to start fine except the following exception
when the Create User button is clicked from the Admin screen. Any help
is appreciated.
Leo
6th Dimension-
Tue Jan 02 11:14:15 PST 2001: <WebAppServletContext-tools> *.jsp:
init
Tue Jan 02 11:14:15 PST 2001: <WebAppServletContext-tools>
FlowManager: init
Tue Jan 02 11:14:26 PST 2001:<E> <WebAppServletContext-tools> Servlet
failed with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
'wl': For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:201)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
at
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
at
weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:181)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:141)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:448)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
Tue Jan 02 11:14:26 PST 2001: <ServletContext-General> servletimages:
init

SP3 install causes error in WL Commerce Server

Hi Support,
After we installed SP3 for our Weblogic Server and Commerce Server, our
Example portal failed at the login step with the following error on html
page:
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from
fulfilling the request.
and error messages in weblogic log:
Sat May 20 17:46:41 EDT 2000: <WebLogicServer> WebLogic Server
started
Sat May 20 17:46:58 EDT 2000: <ServletContext-General> WmDemo_Rob:
init
Sat May 20 17:46:58 EDT 2000: <ServletContext-General> *.jsp: init
Sat May 20 17:46:59 EDT 2000: <ServletContext-General> file: init
Sat May 20 17:55:53 EDT 2000: <ServletContext-General> Generated java
file:
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_rob\repository\_userlogin.java
Sat May 20 17:55:59 EDT 2000:<E> <ServletContext-General> Compilation of
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_rob\repository\_userlogin.java
failed:
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_rob\repository\_userlogin.java:512:
No variable NEEDS_CREDENTIALS defined in class
weblogic.servlet.security.ServletAuthentication.
if (authenticated ==
weblogic.servlet.security.ServletAuthentication.NEEDS_CREDENTIALS //[
/portals/WmDev_Rob/Repository/_userlogin.jsp; Line: 79]
^
Note:
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_rob\repository\_userlogin.java
uses or overrides a deprecated API. Recompile with "-deprecation" for
details.
1 error, 1 warning
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[C:/JDK12~1.2/bin/javac.exe,
-classpath,
C:\JDK12~1.2\jre\lib\rt.jar;C:\JDK12~1.2\jre\lib\i18n.jar;C:\JDK12~1.2\jre\classes;C:\JDK12~1.2\jre\lib\rt.jar;D:\WEBLOG~1\lib\Weblogic510sp3boot.jar;D:\weblogic\classes\boot;D:\WEBLOG~1\lib\Weblogic510sp3.jar;D:\WEBLOG~1\lib\Weblogic_RDBMS.jar;D:\weblogic\license;D:\weblogic\lib\rmi-iiop12.jar;D:\weblogic\classes;D:\weblogic\lib\weblogicaux.jar;D:\WEBLOG~1\license;D:\WEBLOG~1\lib\collections.zip;D:\WEBLOG~1\lib\foundation-bmp-deploy.jar;D:\WEBLOG~1\lib\axiom-bmp-deploy.jar;D:\WEBLOG~1\lib\ebusiness-bmp-deploy.jar;D:\WEBLOG~1\lib\examples-bmp-deploy.jar;D:\WEBLOG~1\lib\Helper-bmp.jar;D:\Oracle\Ora81\jdbc\lib\classes111.zip;D:\WEBLOG~1\lib\wljsp.jar;D:\WEBLOG~1\lib\um_tags.jar;D:\WEBLOG~1\lib\esjsp.jar;D:\WEBLOG~1\lib\rules.jar;D:\WEBLOG~1\lib\jrulesserviceprovider.jar;D:\WEBLOG~1\lib\esportal.jar;D:\WEBLOG~1\lib\pt_admin.jar;D:\WEBLOG~1\lib\foundation.jar;D:\WEBLOG~1\lib\axiom.jar;D:\WEBLOG~1\lib\bridge.jar;D:\WEBLOG~1\classes;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25661.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25662.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25663.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25664.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25665.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25666.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25667.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25668.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25669.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25670.jar;D:\weblogic\lib\persistence\WebLogic_RDBMS.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25671.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25672.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25673.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25674.jar;D:\WebLogicCommerce\lib\wljsp.jar;D:\WebLogicCommerce\lib\esportal.jar;D:\WebLogicCommerce\lib\esjsp.jar;D:\WebLogicCommerce\lib\um_tags.jar;%WEBLOGIC_HOME%\myserver\servletclasses;D:\WebLogicCommerce\server\classfiles,
-d, D:\WebLogicCommerce\server\classfiles,
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_rob\repository\_userlogin.java])
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.io.IOException.<init>(IOException.java, Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:96)
at jsp.portals.wmdev_rob.repository.header._jspService(header.java:229)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
Sat May 20 17:56:00 EDT 2000:<E> <ServletContext-General> Servlet failed
with Exception
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[C:/JDK12~1.2/bin/javac.exe,
-classpath,
C:\JDK12~1.2\jre\lib\rt.jar;C:\JDK12~1.2\jre\lib\i18n.jar;C:\JDK12~1.2\jre\classes;C:\JDK12~1.2\jre\lib\rt.jar;D:\WEBLOG~1\lib\Weblogic510sp3boot.jar;D:\weblogic\classes\boot;D:\WEBLOG~1\lib\Weblogic510sp3.jar;D:\WEBLOG~1\lib\Weblogic_RDBMS.jar;D:\weblogic\license;D:\weblogic\lib\rmi-iiop12.jar;D:\weblogic\classes;D:\weblogic\lib\weblogicaux.jar;D:\WEBLOG~1\license;D:\WEBLOG~1\lib\collections.zip;D:\WEBLOG~1\lib\foundation-bmp-deploy.jar;D:\WEBLOG~1\lib\axiom-bmp-deploy.jar;D:\WEBLOG~1\lib\ebusiness-bmp-deploy.jar;D:\WEBLOG~1\lib\examples-bmp-deploy.jar;D:\WEBLOG~1\lib\Helper-bmp.jar;D:\Oracle\Ora81\jdbc\lib\classes111.zip;D:\WEBLOG~1\lib\wljsp.jar;D:\WEBLOG~1\lib\um_tags.jar;D:\WEBLOG~1\lib\esjsp.jar;D:\WEBLOG~1\lib\rules.jar;D:\WEBLOG~1\lib\jrulesserviceprovider.jar;D:\WEBLOG~1\lib\esportal.jar;D:\WEBLOG~1\lib\pt_admin.jar;D:\WEBLOG~1\lib\foundation.jar;D:\WEBLOG~1\lib\axiom.jar;D:\WEBLOG~1\lib\bridge.jar;D:\WEBLOG~1\classes;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25661.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25662.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25663.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25664.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25665.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25666.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25667.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25668.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25669.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25670.jar;D:\weblogic\lib\persistence\WebLogic_RDBMS.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25671.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25672.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25673.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25674.jar;D:\WebLogicCommerce\lib\wljsp.jar;D:\WebLogicCommerce\lib\esportal.jar;D:\WebLogicCommerce\lib\esjsp.jar;D:\WebLogicCommerce\lib\um_tags.jar;%WEBLOGIC_HOME%\myserver\servletclasses;D:\WebLogicCommerce\server\classfiles,
-d, D:\WebLogicCommerce\server\classfiles,
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_rob\repository\_userlogin.java])
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.io.IOException.<init>(IOException.java, Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:96)
at jsp.portals.wmdev_rob.repository.header._jspService(header.java:229)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
Sat May 20 17:56:01 EDT 2000: <ServletContext-General> servletimages:
init
Sat May 20 18:30:56 EDT 2000: <ServletContext-General> WmDemo_Wen:
init
Sat May 20 18:30:57 EDT 2000: <ServletContext-General> Generated java
file:
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_wen\repository\_userlogin.java
Sat May 20 18:31:04 EDT 2000:<E> <ServletContext-General> Compilation of
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_wen\repository\_userlogin.java
failed:
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_wen\repository\_userlogin.java:512:
No variable NEEDS_CREDENTIALS defined in class
weblogic.servlet.security.ServletAuthentication.
if (authenticated ==
weblogic.servlet.security.ServletAuthentication.NEEDS_CREDENTIALS //[
/portals/WmDev_Wen/Repository/_userlogin.jsp; Line: 79]
^
Note:
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_wen\repository\_userlogin.java
uses or overrides a deprecated API. Recompile with "-deprecation" for
details.
1 error, 1 warning
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[C:/JDK12~1.2/bin/javac.exe,
-classpath,
C:\JDK12~1.2\jre\lib\rt.jar;C:\JDK12~1.2\jre\lib\i18n.jar;C:\JDK12~1.2\jre\classes;C:\JDK12~1.2\jre\lib\rt.jar;D:\WEBLOG~1\lib\Weblogic510sp3boot.jar;D:\weblogic\classes\boot;D:\WEBLOG~1\lib\Weblogic510sp3.jar;D:\WEBLOG~1\lib\Weblogic_RDBMS.jar;D:\weblogic\license;D:\weblogic\lib\rmi-iiop12.jar;D:\weblogic\classes;D:\weblogic\lib\weblogicaux.jar;D:\WEBLOG~1\license;D:\WEBLOG~1\lib\collections.zip;D:\WEBLOG~1\lib\foundation-bmp-deploy.jar;D:\WEBLOG~1\lib\axiom-bmp-deploy.jar;D:\WEBLOG~1\lib\ebusiness-bmp-deploy.jar;D:\WEBLOG~1\lib\examples-bmp-deploy.jar;D:\WEBLOG~1\lib\Helper-bmp.jar;D:\Oracle\Ora81\jdbc\lib\classes111.zip;D:\WEBLOG~1\lib\wljsp.jar;D:\WEBLOG~1\lib\um_tags.jar;D:\WEBLOG~1\lib\esjsp.jar;D:\WEBLOG~1\lib\rules.jar;D:\WEBLOG~1\lib\jrulesserviceprovider.jar;D:\WEBLOG~1\lib\esportal.jar;D:\WEBLOG~1\lib\pt_admin.jar;D:\WEBLOG~1\lib\foundation.jar;D:\WEBLOG~1\lib\axiom.jar;D:\WEBLOG~1\lib\bridge.jar;D:\WEBLOG~1\classes;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25661.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25662.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25663.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25664.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25665.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25666.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25667.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25668.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25669.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25670.jar;D:\weblogic\lib\persistence\WebLogic_RDBMS.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25671.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25672.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25673.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25674.jar;D:\WebLogicCommerce\lib\wljsp.jar;D:\WebLogicCommerce\lib\esportal.jar;D:\WebLogicCommerce\lib\esjsp.jar;D:\WebLogicCommerce\lib\um_tags.jar;%WEBLOGIC_HOME%\myserver\servletclasses;D:\WebLogicCommerce\server\classfiles,
-d, D:\WebLogicCommerce\server\classfiles,
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_wen\repository\_userlogin.java])
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.io.IOException.<init>(IOException.java, Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:96)
at jsp.portals.wmdev_wen.repository.header._jspService(header.java:229)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
Sat May 20 18:31:05 EDT 2000:<E> <ServletContext-General> Servlet failed
with Exception
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[C:/JDK12~1.2/bin/javac.exe,
-classpath,
C:\JDK12~1.2\jre\lib\rt.jar;C:\JDK12~1.2\jre\lib\i18n.jar;C:\JDK12~1.2\jre\classes;C:\JDK12~1.2\jre\lib\rt.jar;D:\WEBLOG~1\lib\Weblogic510sp3boot.jar;D:\weblogic\classes\boot;D:\WEBLOG~1\lib\Weblogic510sp3.jar;D:\WEBLOG~1\lib\Weblogic_RDBMS.jar;D:\weblogic\license;D:\weblogic\lib\rmi-iiop12.jar;D:\weblogic\classes;D:\weblogic\lib\weblogicaux.jar;D:\WEBLOG~1\license;D:\WEBLOG~1\lib\collections.zip;D:\WEBLOG~1\lib\foundation-bmp-deploy.jar;D:\WEBLOG~1\lib\axiom-bmp-deploy.jar;D:\WEBLOG~1\lib\ebusiness-bmp-deploy.jar;D:\WEBLOG~1\lib\examples-bmp-deploy.jar;D:\WEBLOG~1\lib\Helper-bmp.jar;D:\Oracle\Ora81\jdbc\lib\classes111.zip;D:\WEBLOG~1\lib\wljsp.jar;D:\WEBLOG~1\lib\um_tags.jar;D:\WEBLOG~1\lib\esjsp.jar;D:\WEBLOG~1\lib\rules.jar;D:\WEBLOG~1\lib\jrulesserviceprovider.jar;D:\WEBLOG~1\lib\esportal.jar;D:\WEBLOG~1\lib\pt_admin.jar;D:\WEBLOG~1\lib\foundation.jar;D:\WEBLOG~1\lib\axiom.jar;D:\WEBLOG~1\lib\bridge.jar;D:\WEBLOG~1\classes;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25661.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25662.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25663.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25664.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25665.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25666.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25667.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25668.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25669.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25670.jar;D:\weblogic\lib\persistence\WebLogic_RDBMS.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25671.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25672.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25673.jar;D:\WebLogicCommerce\server\tmp_deployments\ejbjar25674.jar;D:\WebLogicCommerce\lib\wljsp.jar;D:\WebLogicCommerce\lib\esportal.jar;D:\WebLogicCommerce\lib\esjsp.jar;D:\WebLogicCommerce\lib\um_tags.jar;%WEBLOGIC_HOME%\myserver\servletclasses;D:\WebLogicCommerce\server\classfiles,
-d, D:\WebLogicCommerce\server\classfiles,
D:\WebLogicCommerce\server\classfiles\jsp\portals\wmdev_wen\repository\_userlogin.java])
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.io.IOException.<init>(IOException.java, Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:96)
at jsp.portals.wmdev_wen.repository.header._jspService(header.java:229)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:153)
at
com.beasys.commerce.axiom.jsp.JspServiceManager.service(JspServiceManager.java:1033)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

Hi Robert,
Our team is well aware of the problem with WLCS 2.0 and WLS SP3 that shows
up when using the MyBuyBeans demo.
We are looking into this problem in engineering and we will post any
solution(s) once we figure out the offending issue.
Thanks.
Nelson Paiva
WLCS Developer Relations Engineer
</Customer>
After we installed SP3 for our Weblogic Server and Commerce Server, our
Example portal failed at the login step with the following error on html
page:
</Customer>

ORA-24327 error when trying to configure Oracle JDriver 2.0 on Commerce Server 3.5 SP1 on WLServer 6.0 SP2

When I try to install and configure the Oracle JDriver v.2.0 to work with Commerce
Server 3.5 SP1 and WebLogic Server 6.0 SP2, on starting up the commerce server,
I get the exceptions that follow this message. I cannot run the dbping utility
because it says it cannot find the BEA license file to verify that JDriver is
licensed for use. I looked over previous discussion threads on this particular
Oracle error, and the problem in the previous cases appears to have been use of
the wrong TNS name. I am referencing the same TNS name that is in my server's
tnsnames.ora file. I can connect to the database using SQLNet and the same connection
parameters that I have set up in weblogic. My Oracle home directory is set to
the directory just above the client install. I am trying to configure Commerce
Server on a Sun SPARC system running Solaris 8. Any help would be greatly appreciated.
Thanks,
Jon Morgan
---------- LOGIN ERROR CODE: 24327
java.sql.SQLException: Error while trying to retrieve text for error ORA-24327
(WEBLOGIC/********@ARBR.intelixinc)
at weblogic.db.oci.OciConnection.getLDAException(OciConnection.java:161)
at weblogic.jdbcbase.oci.Driver.connect(Driver.java:92)
at com.beasys.commerce.axiom.contact.security.RDBMSDelegate.init(RDBMSDe
legate.java:194)
at com.beasys.commerce.axiom.contact.security.RDBMSDelegate.<init>(RDBMS
Delegate.java:139)
at com.beasys.commerce.axiom.contact.security.RDBMSDelegate$DFactory.get
Instance(RDBMSDelegate.java:975)
at com.beasys.commerce.util.Pool.<init>(Pool.java:37)
at com.beasys.commerce.axiom.contact.security.RDBMSRealm.<init>(RDBMSRea
lm.java:127)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.security.acl.Realm.getRealm(Realm.java:84)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:265)
at weblogic.security.SecurityService.initialize(SecurityService.java:123
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
<Aug 7, 2001 11:50:29 AM EDT> <Emergency> <Server> <Unable to initialize the ser
ver: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: com.beasys.commerce.axiom.contact.secur
ity.RDBMSException: realm initialization failed, action 'Driver.connect', - wit
h nested exception:
[java.sql.SQLException: Error while trying to retrieve text for error ORA-24327
- (WEBLOGIC/********@ARBR.intelixinc)]
java.lang.IllegalAccessError: com.beasys.commerce.axiom.contact.security.RDBMSEx
ception: realm initialization failed, action 'Driver.connect', - with nested
ex
ception:
[java.sql.SQLException: Error while trying to retrieve text for error ORA-24327
- (WEBLOGIC/********@ARBR.intelixinc)]
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:265)
at weblogic.security.SecurityService.initialize(SecurityService.java:123
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: com.beasys.commerce.axiom.contac
t.security.RDBMSException: realm initialization failed, action 'Driver.connect',
- with nested exception:
[java.sql.SQLException: Error while trying to retrieve text for error ORA-24327
- (WEBLOGIC/********@ARBR.intelixinc)]
java.lang.IllegalAccessError: com.beasys.commerce.axiom.contact.security.RDBMSEx
ception: realm initialization failed, action 'Driver.connect', - with nested
ex
ception:
[java.sql.SQLException: Error while trying to retrieve text for error ORA-24327
- (WEBLOGIC/********@ARBR.intelixinc)]
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:265)
at weblogic.security.SecurityService.initialize(SecurityService.java:123
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception

Wrong Forum, you want the APEX LISTENER support forum, this is the APEX support forum..
Thank you,
Tony Miller
LuvMuffin Software

The server has experienced an error on startup.

Has anyone seen this error before?
The server has experienced an error on startup. This problem must be fixed before using the system.
I am not sure what caused it but I first saw it after restarting the server and now when I go to http://localhost/portal/server.pt that message appears.
Any ideas on how to fix it?
Thanks.

I've seen this one when the connection to the database is failing for some reason. To see what is happening, restart IIS (or java server) to clear the cache, start PTSpy and then try to hit the page again. You should see all the startup messages and any errors.
Hope this helps,
Adam

Problem with Weblogic Commerce Server 3.1

I am currently evaluating the Weblogic Commerce server 3.1 product. I have
installed the Weblogic server 5.1 and the service pack 6 along with the
Commerce Server. I can get into the WLCS Commerce Server Templates and can
navigate the store categories and search for items but when I try to add to
the shopping cart or view the shopping cart I get taken to the 'servererror'
template. I have included at the bottom of this message the message from
the log file. Does anyone have any idea why I am getting this error?
Thanks in advance,
Barry Childs
Manager Knowledgebase Applications
Xactsites
<<<<<<< weblogic.log >>>>>>>
Fri Nov 10 14:00:16 MST 2000:<E> <WebAppServletContext-wlcs> Servlet failed
with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at: 'wl':
For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java,
Compiled Code)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java,
Compiled Code)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java,
Compiled Code)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java, Compiled
Code)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
Compiled Code)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestinat
ion(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:376
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

I am currently evaluating the Weblogic Commerce server 3.1 product. I have
installed the Weblogic server 5.1 and the service pack 6 along with the
Commerce Server. I can get into the WLCS Commerce Server Templates and can
navigate the store categories and search for items but when I try to add to
the shopping cart or view the shopping cart I get taken to the 'servererror'
template. I have included at the bottom of this message the message from
the log file. Does anyone have any idea why I am getting this error?
Thanks in advance,
Barry Childs
Manager Knowledgebase Applications
Xactsites
<<<<<<< weblogic.log >>>>>>>
Fri Nov 10 14:00:16 MST 2000:<E> <WebAppServletContext-wlcs> Servlet failed
with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at: 'wl':
For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java,
Compiled Code)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java,
Compiled Code)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java,
Compiled Code)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java, Compiled
Code)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
Compiled Code)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestinat
ion(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:376
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

Starting Commerce Server and Personalization Server

I am trying to evaluate these products. I am running NT 4.0, SP5 with
256MB RAM. I have installed Weblogic Server 5.1.0 with SP 6. I have
installed the latest version of the Commerce Server and Personalization
Server. I had to remove the -server switch from the java command line in
the startup script in order to get the JVM to start. The Commerce server
begins to initialize, then a bunch of exceptions are thrown, then it
shuts itself down.
I have attached the log file
WeblogicCommerceServer3.2\server\weblogic.log
Thanks for any help on this.
[weblogic.log]

The error in your weblogic.log file of:
2001:<E> <T3Services> COMMERCE_SERVER_FRAMEWORK,LOG_ERROR,"Current WebLogic build may
not be compatible with the WebLogic Commerce Server implementation. Minimum Build:
83914 Current Installation Build: 66825"
Tue Apr 24 16:50:53 EDT
means that WLCS cannot find the correct service pack files for WLS 5.10. Might check
to see if the WLS 5.10 SP6 files (weblogic510sp6.jar and weblogic510s6boot.jar) are
located in d:\weblogic\lib.
Ted
jcerruto wrote:
I am trying to evaluate these products. I am running NT 4.0, SP5 with
256MB RAM. I have installed Weblogic Server 5.1.0 with SP 6. I have
installed the latest version of the Commerce Server and Personalization
Server. I had to remove the -server switch from the java command line in
the startup script in order to get the JVM to start. The Commerce server
begins to initialize, then a bunch of exceptions are thrown, then it
shuts itself down.
I have attached the log file
WeblogicCommerceServer3.2\server\weblogic.log
Thanks for any help on this.
Name: weblogic.log
weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
Encoding: base64

Server https-WEB: CORE0125 The server terminated abnormally with error code

"Server https-WEB: CORE0125 The server terminated abnormally with error code 0, An attempt will be made to restart it. "
This happens every time I reboot the server or logoff. It has no ill effect on the server itself except generating these event log errors I am using Sun One 6.1 SP 1 on a wondows 2003 server. I have to resolve this beofore I can go any furthur in my project. Any help? This error comes up for both the web servive and the admin service.

Thanks to a post I just discovered, I have solved this problem.
The JVM within Sun Web Server is accepting kill signals from Windows when users logoff. When the JVM dies, apparently the web server service just dies as well. It's a long story and I don't really care to understand it fully.
You can refer to the thread I found for the solution of passing the JVM a startup option to ignore these signals.
http://swforum.sun.com/jive/thread.jspa?forumID=16&threadID=23382
Or, you can just disable the JVM completely as I did. Though there is a checkbox for this for user-defined servers under the Java tab. I couldn't find where to do this for the admin server itself, so I commented out the line in magnus.conf that loads j2ee-plugin.dll.
We'll see if this causes any other problems, but so far so good.

Hybrid Connection fails for Windows SQL Server 2014 - SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted

Hello,
I have configured BizTalk Services Hybrid Connection between Standard Azure Website and SQL Server 2014 on premise.
Azure Management portal shows the status of Hybrid Connection as established.
However, the website throws an error when trying to open a connection
<
addname="DefaultConnection"
connectionString="Data
Source=machine name;initial catalog=AdventureWorks2012;Uid=demouser;Password=[my password];MultipleActiveResultSets=True"
providerName="System.Data.SqlClient"
/>
(The same website, with the same connection string deployed on SQL Server machine works correctly).
I tried various options with the connections sting (IP address instead of machine name, Trusted_Connection=False, Encrypt=False, etc. the result is the same
[Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
[SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.
I tried various machines - on premise and a clean Azure VM with SQL Server and it results in the same error - below full stack
The certificate chain was issued by an authority that is not trusted
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ComponentModel.Win32Exception: The certificate chain was issued by an authority that is not trusted
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
[SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +5341687
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +546
System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle, SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock) +5348371
System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate) +91
System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate) +331
System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec, FeatureExtension requestedFeatures, SessionData recoverySessionData) +2109
System.Data.SqlClient.SqlInternalConnectionTds.Login(ServerInfo server, TimeoutTimer timeout, String newPassword, SecureString newSecurePassword) +347
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover) +238
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) +892
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) +311
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData) +646
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) +278
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) +38
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +732
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +85
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1057
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +78
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) +196
System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +146
System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +16
System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) +94
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +110
System.Data.SqlClient.SqlConnection.Open() +96
System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +44
[EntityException: The underlying provider failed on Open.]
System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +203
System.Data.EntityClient.EntityConnection.Open() +104
System.Data.Objects.ObjectContext.EnsureConnection() +75
System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) +41
System.Data.Objects.ObjectQuery`1.System.Collections.Generic.IEnumerable<T>.GetEnumerator() +36
System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) +369
System.Linq.Enumerable.ToList(IEnumerable`1 source) +58
CloudShop.Services.ProductsRepository.GetProducts() +216
CloudShop.Controllers.HomeController.Search(String SearchCriteria) +81
CloudShop.Controllers.HomeController.Index() +1130
lambda_method(Closure , ControllerBase , Object[] ) +62
System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) +14
System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) +193
System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +27
System.Web.Mvc.Async.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41() +28
System.Web.Mvc.Async.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _) +10
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) +32
System.Web.Mvc.Async.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() +58
System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +225
System.Web.Mvc.Async.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) +10
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) +34
System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +23
System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +99
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +27
System.Web.Mvc.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) +14
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +39
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +29
System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) +10
System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) +25
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +31
System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +9
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +9651188
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.36213
Regards,
Michal
Michal Morciniec

Same issue here, looking for more information !

Trying to install Bea WebLogic Commerce Server 3.2

Hi there!
This is my environment:
Red Hat Linux 6.2 Kernel 2.2.14;
Bea WebLogic Server 5.1 service pack 9 (couldn't find service pack 6);
Java 1.3.1 (only for the Commerce Server);
Java 1.2.2 (only for Bea WebLogic Server);
512 Mb RAM
I followed instructions to install an evaluation copy of the Commerce Server 3.2
and this is my log of activities:
1. Registered software in order to get my evaluation license;
2. Downloaded the 1.3.1 version of java for Linux (they say: "The Solaris and
Linux versions of J2SE 1.3 ship with both VM implementations" (regarding client
& server implementations) source: http://java.sun.com/j2se/1.3/docs/guide/performance/hotspot.html);
3. Installed Java 1.3.1 as documentation says;
4. Installed WLCS 3.2 following step by step the guide regarding the "Does not
have a windowing environment" section (i found an error because my bundled version
does not have the UninstallerData/Uninstaller_Haystack file);
5. Ran the StartCommerce.sh procedure to start the server;
6. Got this error: (please see below)
What's wrong?
Thanks in advance
Sergio Ríos
Ps: this is the error:
Fri May 25 11:56:17 CDT 2001: <WebLogicServer> T3StartupDef KeyBootstrap com.beasys.commerce.ebusiness.security.KeyBootstrap
reports: Encryption not enabled
Fri May 25 11:56:17 CDT 2001: <ListenThread> Listening on port: 7501
Fri May 25 11:56:18 CDT 2001: <SSLListenThread> Listening on port: 7502
Fri May 25 11:56:18 CDT 2001: <Posix Performance Pack> System has file descriptor
limits of - soft: '1024', hard: '1024'
Fri May 25 11:56:18 CDT 2001: <Posix Performance Pack> Using effective file
descriptor limit of: '1024' open sockets/files.
Fri May 25 11:56:18 CDT 2001: <Posix Performance Pack> Allocating: '3' POSIX
reader threads
Fri May 25 11:56:18 CDT 2001: <WebLogicServer> WebLogic Server started
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested 268435468
bytes
[desa@aplicacion WebLogicCommerceServer3.2]$

Hi there!
This is my environment:
Red Hat Linux 6.2 Kernel 2.2.14;
Bea WebLogic Server 5.1 service pack 9 (couldn't find service pack 6);
Java 1.3.1 (only for the Commerce Server);
Java 1.2.2 (only for Bea WebLogic Server);
512 Mb RAM
I followed instructions to install an evaluation copy of the Commerce Server 3.2
and this is my log of activities:
1. Registered software in order to get my evaluation license;
2. Downloaded the 1.3.1 version of java for Linux (they say: "The Solaris and
Linux versions of J2SE 1.3 ship with both VM implementations" (regarding client
& server implementations) source: http://java.sun.com/j2se/1.3/docs/guide/performance/hotspot.html);
3. Installed Java 1.3.1 as documentation says;
4. Installed WLCS 3.2 following step by step the guide regarding the "Does not
have a windowing environment" section (i found an error because my bundled version
does not have the UninstallerData/Uninstaller_Haystack file);
5. Ran the StartCommerce.sh procedure to start the server;
6. Got this error: (please see below)
What's wrong?
Thanks in advance
Sergio Ríos
Ps: this is the error:
Fri May 25 11:56:17 CDT 2001: <WebLogicServer> T3StartupDef KeyBootstrap com.beasys.commerce.ebusiness.security.KeyBootstrap
reports: Encryption not enabled
Fri May 25 11:56:17 CDT 2001: <ListenThread> Listening on port: 7501
Fri May 25 11:56:18 CDT 2001: <SSLListenThread> Listening on port: 7502
Fri May 25 11:56:18 CDT 2001: <Posix Performance Pack> System has file descriptor
limits of - soft: '1024', hard: '1024'
Fri May 25 11:56:18 CDT 2001: <Posix Performance Pack> Using effective file
descriptor limit of: '1024' open sockets/files.
Fri May 25 11:56:18 CDT 2001: <Posix Performance Pack> Allocating: '3' POSIX
reader threads
Fri May 25 11:56:18 CDT 2001: <WebLogicServer> WebLogic Server started
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested 268435468
bytes
[desa@aplicacion WebLogicCommerceServer3.2]$

Using Hprof with Commerce Server 3.5

My company is beginning the move to J2EE and I have been tasked with researching
profilers. I quickly came across Hprof, which is provided by the Sun JVM through
the use of the -Xrunhprof option. I have been able to successfully profile a
very small test application (stand alone app). However, I run into problems when
I use Hprof and try to start the example server provided with Commerce Server
3.5 (with WebLogic 6.0). Please see below for my syntax and results.
Syntax
%JAVA_HOME%\bin\java -Xrunhprof:cpu=times,doe=y .....
Results
The server appears to start and work correctly (no HRPOF ERROR: messages). When
I shut it down (using the console) and look at the java.hprof.txt file that is
created, the hprof data has not been fully written to the file. The file ends
in the middle of a trace:
TRACE 6687:
java/net/URLStreamHandler.getDefaultPort(URLStreamHandler.java:Unknown line)
I am curious if anyone has run into this problem before and how they might have
corrected it. Can anyone suggest a set of Hprof parameters to use? Or provide
a link to a good description of all of the parameters (I haven't found a lot of
documentation on it)?
I know that there are other commercial profilers (JProbe, Optimizeit, etc.) but
I would like to learn the basics before diving into them.
Any comments or suggestions would be appreciated.
Thanks
--Chris

Hi Martin,
You probably already noticed, but a new WLCS 3.5 license has been
posted at http://commerce.bea.com/downloads/commerce_servers.jsp
Thanks for posting this. I'm sorry it didn't get answered until now.
If you ever have a question in the newsgroup that is not answered quickly
enough to get you on track with your evaluation or development process
then you can let our support team know about it by opening a support case
(for free) at http://www.bea.com/support/index.jsp
Martin Swan wrote:
When will the license on your site be updated, it ran out yesterday ?--
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com

BEA WebLogic Commerce Server 3.5 with MS SQL Server 2000 as DB

Ooops !
Sorry but in my last mail I forgot to attach the file with the
stdout log with the described example portal errors. Here is
the message and the file.
Davide Pozzi
Hi to all.
I have a problem using BEA WebLogic Server 3.5 (with service
pack 1) with SQL Server 2000 as the database. I followed the
instructions for SQL Server 7 included in the file readme.txt > in WLCS_35_DDLand the (thin) Web documentation on the
subject. The I tried to run the example portal and the
templates examples. All is working well apart from the fact
that some data seem not to be taken from the database. For
example the example portal lacks the news titles in the "News > Index" portletand the ads in the "AcmePromotion" portlet. In > the templates examples some logo
are missing (the E-Business
Control Center loads, but no campains or discounts, etc. are
loaded). When I start the example portal, a lot of exceptions > arise. In theattached text file the stdout log of Commerce
Server is reported.
Can anyone tell me a hint to solve these problems ? There are > known problemssetting up SQL Server 2000 with Commerce Server > 3.5 ? I've seen that Commerce
Server 3.5 is not yet certified > for SQL Server 2000, is BEA going to certificate
it ?
>
Thank you in advance for any help.
Davide Pozzi[errors.txt]

Ooops !
Sorry but in my last mail I forgot to attach the file with the
stdout log with the described example portal errors. Here is
the message and the file.
Davide Pozzi
Hi to all.
I have a problem using BEA WebLogic Server 3.5 (with service
pack 1) with SQL Server 2000 as the database. I followed the
instructions for SQL Server 7 included in the file readme.txt > in WLCS_35_DDLand the (thin) Web documentation on the
subject. The I tried to run the example portal and the
templates examples. All is working well apart from the fact
that some data seem not to be taken from the database. For
example the example portal lacks the news titles in the "News > Index" portletand the ads in the "AcmePromotion" portlet. In > the templates examples some logo
are missing (the E-Business
Control Center loads, but no campains or discounts, etc. are
loaded). When I start the example portal, a lot of exceptions > arise. In theattached text file the stdout log of Commerce
Server is reported.
Can anyone tell me a hint to solve these problems ? There are > known problemssetting up SQL Server 2000 with Commerce Server > 3.5 ? I've seen that Commerce
Server 3.5 is not yet certified > for SQL Server 2000, is BEA going to certificate
it ?
>
Thank you in advance for any help.
Davide Pozzi[errors.txt]

Commerce Server won't shut down with command on NT

I need to have the Commerce server shut down using a command line argument; i.e. set-environment.bat followed by %JDK_HOME%\bin\java -classpath %WEBLOGIC_CLASSPATH% weblogic.Admin t3://localhost:7501 SHUTDOWN system mypass.
The system user and password work for the default weblogic server and with the console but not for the commerce server.
The error that occurs is "Exception in thread "main" java.lang.SecurityException: Authentication for
user system denied in realm weblogic".
The software is Weblogic Commerce Server 3.2 and Weblogic Server 5.1.0 SP6, and Java SDK 1.3 (JDK) running on Windows NT 4 SP6. The java.policy file grants all permissions and is unchanged. I did add a user in the portal demo but that is all.
I opened a case on evalnet but haven't found a solution.
The weblogic.properties file has an appropriate line
weblogic.password.system=password (it has my real password)
All of the weblogic.allow.execute.weblogic.servlet.??? properties are set to the default of system.
How else is the realm authentification set up? Where can I look for problems with the user?

Nevermind, I found the problem. The system password for my weblogic default server is meaningless for commerce server as it has its own weblogic.properties file with the system user password of "weblogic".

Startup of commerce server 3.5 generates errors.

Similar Messages

Maybe you are looking for