Re:The JDBC exception in log file

<Jul 1, 2010 1:57:59 AM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "xxxDS": Io exception: The Network Adapter could not establish the connection>
<Jul 1, 2010 1:57:59 AM EDT> <Info> <JDBC> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:300)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:204)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1096)
at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2018)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

The root cause of this exception is: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
1. From Weblogic Admin Console, go to this Datasource and TEST the connection and see if it is connecting successfully. May be the Host/Port for the Oracle connection and username/password or SID name may be invalid or wrongly configured.
2. If you have any client to connect to this database like SQL Developer etc, try to connect to that db schema from this tool and see if this works.
3. One more thing. Check the Firewall settings and specially if the DB Port is open on the server where the database is running. In our Env, usually unless we open the port like for Oracle 1521, outsiders or other machines cannot connect to that database either from SQL Developer or from weblogic datasoures. So check for the port not open issues.
4. Last option is if the Network is down and not able to connect to that db server. Check with Network guys.
Thanks
Ravi Jegga

Similar Messages

  • Can I modify WLI system Bean's transaction attribute --turn on archiver resulting endless exception in log file

    hi,erveryone,
    one difficult question need help.
    Environment: WLS8.1sp2 + WLI8.1sp2 + ORACLE9i + solaris9
    when I started archiver manually,just for a while, wli system generated about 40,000 JMS messages in
    wli.internal.worklist.timer.queue,and consume the great mass of system resource of Database server,I had to stop these
    archive processes immediately to keep other applicaitons which using the same database running normal. I did so by
    following steps:
    (1) in WLI console, delete wli.internal.worklist.timer.queue;
    (2) in WLI console, reconstruct wli.internal.worklist.timer.queue;
    (3) restart wli server.
    after server was restarted, wli server output endless and repeatly exception to log file ,the typical exception was:
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '54' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B26B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    java.sql.SQLException: Transaction rolled back: Unknown reason.
    java.sql.SQLException: Transaction rolled back: Unknown reason
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1299)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1055)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '96' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B96B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found..
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1165)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    The wli server generated log file very quickly ,:it can output 1M bytes log file per second,all logged information
    is similar to the <BEA-010049> excetpion metioned above. BEA support engineer suggested me to totally stop the
    archive ,I did so,but the server was still ouput the log file like crazy as before and the normal log information are
    completely override by <BEA-010049> excetpion.
    I checked the EntityEJBs in WLI console :Mywlidomain> Applications> WLI System EJBs> WLI Worklist Persistence$)A#,and
    found that in statistics table :
    ListenerBean : Pool miss ratio = 99.67%, transaction rollback ration = 99.90%,Destory Bean Ratio = 99.48%(see
    attachment)
    WorklistTimerMDB: transaction rollback ratio = 99.97%
    It seems ListenerBean worked incorrectly.I searched in support.bea.com and found one example which also about server
    output endless log file,the author solved this problem by changing Bean's transaction-attribute from 'Required'
    to 'RequiresNew' thought he didn't know why it works. I try this method by changing ListenerBean's
    transaction-attribute from 'Required' to 'RequiresNew'.
    $weblogic_home/integration/lib/wli-ejbs.ear/ejb-jar-generic.xml:
    <ejb-name>CommentBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>ListenerBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>RequiresNew</trans-attribute> -----------the default value is Required,I modified it to
    RequiresNew.
    </container-transaction>
    <container-transaction>
    really it works, the log file output resume normal. But there are still some problems:
    (1) this exception is still exist:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
    (2) is this method safe ?(Does "Modify ListenBean's transaction-attribute" impat other parts of wli system?)
    (3) after changed the transaction attribute, if turn on archive again, the server output endless exception:
    ####<Jun 1, 2005 5:14:58 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '63' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-2F43890B86B0A8856F80> <BEA-010036> <Exception from ejbStore:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1292)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    How can I solve these problem ? any suggestion is warm welcome.
    Thanks in advance.
    Great Lou

    Back up all data to at least two different storage devices, if you haven't already done so. The backups can be made with Time Machine or with a mirroring tool such as Carbon Copy Cloner. Preferably both.
    Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume with the default options.This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For details of how this works, see here:
    Using Setup Assistant
    Transfer only "Users" and "Settings" – not "Applications" or "Other files." Don't transfer the Guest account, if it was enabled on the old system. Test. If the problem is still there, you have a hardware fault. Take the machine to an Apple Store for diagnosis.
    If the problem is resolved, reinstall your third-party software cautiously. Self-contained applications that install into the Applications folder by drag-and-drop or download from the App Store are safe. Anything that comes packaged as an installer or that prompts for an administrator password is suspect, and you must test thoroughly after reinstalling each such item to make sure you haven't restored the problem.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

  • The format of Audit log file

    We have a perl script to extract data from Audit log files(Oracle Database 10g Release 10.2.0.1.0) which have format as bellow.
    Audit file /u03/oracle/admin/NIKKOU/adump/ora_5037.aud
    Oracle Database 10g Release 10.2.0.1.0 - Production
    ORACLE_HOME = /u01/app/oracle/product/10.2.0
    System name:     Linux
    Node name:     TOYDBSV01
    Release:     2.6.9-34.ELsmp
    Version:     #1 SMP Fri Feb 24 16:54:53 EST 2006
    Machine:     i686
    Instance name: NIKKOU
    Redo thread mounted by this instance: 1
    Oracle process number: 22
    Unix process pid: 5037, image: oracleNIKKOU@TOYDBSV01
    Sun Jul 27 03:06:34 2008
    ACTION : 'CONNECT'
    DATABASE USER: 'sys'
    PRIVILEGE : SYSDBA
    CLIENT USER: oracle
    CLIENT TERMINAL:
    STATUS: 0
    After we update the db from Release 10.2.0.1.0 to Release 10.2.0.4.0, the format of Audit log file had been changed to something likes below.
    Audit file /u03/oracle/admin/NIKKOU/adump/ora_1897.aud
    Oracle Database 10g Release 10.2.0.4.0 - Production
    ORACLE_HOME = /u01/app/oracle/product/10.2.0
    System name:     Linux
    Node name:     TOYDBSV01
    Release:     2.6.9-34.ELsmp
    Version:     #1 SMP Fri Feb 24 16:54:53 EST 2006
    Machine:     i686
    Instance name: NIKKOU
    Redo thread mounted by this instance: 1
    Oracle process number: 21
    Unix process pid: 1897, image: oracle@TOYDBSV01
    Tue Oct 14 10:30:29 2008
    LENGTH : '135'
    ACTION :[7] 'CONNECT'
    DATABASE USER:[3] 'SYS'
    PRIVILEGE :[6] 'SYSDBA'
    CLIENT USER:[0] ''
    CLIENT TERMINAL:[7] 'unknown'
    STATUS:[1] '0'
    Because we have to rewrite the perl script, could anyone tell us where we can find the manual to describe the format of the Audit log file.

    Oracle publishes views of the audit trail data. You can find a list of the views for the 11.1 database here:
    http://download.oracle.com/docs/cd/B28359_01/network.111/b28531/auditing.htm#BCGIICFE
    The audit trail does not really change between patchsets as that would constitute underlying structure changes and right now, the developers are not allowed to change the underlying structure of tables in patchsets. But, we can change what may be displayed in a column from patchset to patchset. For example, we are getting ready to update the comment$text field to display more information like dblinks and program names.
    I personally don't like overloading the comment$text field like that, but sometimes when you need the information, that is the only choice except to wait for the next major release :)
    As for the output of the audit log files, those can change between patchsets because of bugs that were found and some changes to support Audit Vault. My apologies out there for anyone that is reading the audit files written to the OS directly, I would recommend using the views.
    Hope that helps. Tammy

  • How to delete the data in archived log files

    hi
    how can i delete the enteries in archived log files. and what is the disadvantage of deleting archived log enteries.

    There is no documented way to delete data stored in archived log files: you can only remove the archived log files if needed.

  • Used to convert all my videos into iPhone mp4 format using Any Video Converter - then add it to my iPhone 3GS. But last few days, I cant add video files to iTunes. and the iTunes doesnt even specify the reason except for that "files are not supported"

    Everyting was perfect earlier. Used to convert all my videos into iPhone mp4 format using Any Video Converter - then add it to my iPhone 3GS. But last few days, I cant add video files to iTunes. and the iTunes doesnt even specify the reason except for that "files are not supported"
    Everything is fine.
    -They are the right format
    -Quicktime is updated
    -I have tried simply dragging them into the 'movie' library
    -I have tried going to file<add file to library
    Nothing works, has anyone else had this problem and found a way around it?
    Any and all help appreciated.

    In addition to Mike's suggestions,  you only have 4GB of RAM and Mavericks does use more RAM than other versions. You may also want to look at the apps that startup on login and the possiblity of upgrading RAM.

  • How to increase the size of Redo log files?

    Hi All,
    I have 10g R2 RAC on RHEL. As of now, i have 3 redo log files of 50MB size. i have used redo log size advisor by setting fast_start_mttr_target=1800 to check the optimal size of the redologs, it is showing 400MB. Now, i want to increase the size of redo log files. how to increase it?
    If we are supposed to do it on production, how to do?
    I found the following in one of the article....
    "The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance, however it must balanced out with the expected recovery time.Undersized log files increase checkpoint activity and increase CPU usage."
    I did not understand the the point however it must balanced out with the expected recovery time in the above given paragraph.
    Can anybody help me?
    Thanks,
    Praveen.

    You dont have to shutdown the database before dropping redo log group but make sure you have atleast two other redo log groups. Also note that you cannot drop active redo log group.
    Here is nice link,
    http://www.idevelopment.info/data/Oracle/DBA_tips/Database_Administration/DBA_34.shtml
    And make sure you test this in test database first. Production should be touched only after you are really comfortable with this procedure.

  • Is the disk equal to log files and other questions?

    In the web page http://www.oracle.com/technology/documentation/berkeley-db/je/GettingStartedGuide/introduction.html#dplfeatures, there is a statement, " The checkpointer is responsible for flushing database data to *disk* that was written to cache as the result of a transaction commit ".
    I wonder if the disk here means log files under the JE home directory.
    From my understanding of these documents and other web resources, the check pointer is to write records in Cache to Log files (disk), and then cleaner is to reorganize and then to remove unused log files. For the records in a Cache, they are brought from disk to Cache by querying the index organized in a B-Tree structure, and the In-Compressor is to delete some empty internal nodes of B-Tree.
    I wonder if the above is right to describe relations among these components, check pointer, cleaner, B-Tree and In-Compressor.
    Thanks for your help!
    Best,
    Jiangfan

    Jiangfan Shi wrote:
    I wonder if the disk here means log files under the JE home directory. Yes.
    I wonder if the above is right to describe relations among these components, check pointer, cleaner, B-Tree and In-Compressor. Yes.

  • I can't get this script to produce output to the screen or a log file

    I can't get this script to produce output to the screen or a log file of the select statement results as they are executed.
    SET SERVEROUTPUT ON size 100000
    DECLARE
    v_schema     Varchar2(50);
    v_statement      Varchar2(500);
    v_name varchar2(30);
    v_id varchar2(8);
    v_pwd varchar2(16);
    v_acct varchar2(16);
    CURSOR get_schemas IS
    SELECT DISTINCT owner
    FROM all_tables
    WHERE table_name = 'USERID'
    ORDER BY owner;
    BEGIN
    OPEN get_schemas;
    LOOP
    FETCH get_schemas INTO v_schema;
    EXIT WHEN get_schemas%NOTFOUND;
              v_statement := 'SELECT name,usid,passwd,acctnum INTO v_name,v_id,v_pwd,v_acct FROM '||v_schema||'.userid';
              execute immediate v_statement;
              DBMS_OUTPUT.PUT_LINE('Name='||v_name||' ID='||v_id||' PW='||v_pwd||' AC='||v_acct);          
    END LOOP;
    CLOSE get_schemas;
    END;
    /

    Duplicate post.
    When I run this script nothing is output to the screen or spooled to a file

  • I get the following error: Error log file location: /Library/Logs/Adobe/Installers

    I get the error U44M1P7 Error log file location: /Library/Logs/Adobe/Installers
    Does anyone have an idea what I need to do?  Thanks

    Did you ever find a solution? I am in sort of the same boat. I even had an Adobe rep try to help me. For some reason my Adobe App Manager does not work on my Macbook. It orginally did but one day it just would not launch. After numerous attempts of uninstalling and re-installing without success, the only workaround solution was to create another user on my Macbook and install the Application Manager on that user's account. I can then download the apps / programs and updates from there. When I log out of that user and back into my main account the Adobe programs work....well most of them. I have noticed that certain programs, like Muse will launch and work correctly under my second user account but it will not luanch without error on the main account.
    The fact that no one at Adobe seems to be able to provide a solution is frustraing. Everything worked fine one day, then its all messed up. Switching users is not an ideal solution at all.

  • What is the extension for debug log file name?

    Hi,
    1) Please let me know what is the extension for debug log file....
    is it .dbg or .log ?
    in one of the sr the service engineer asked to put .log as the extension is this correct?
    here is what he said...
    a) Enable the following Profiles at user level:
    OM: Debug Level = 5
    INV: Debug Trace = YES
    INV: Debug Level = 11
    INV: Debug File = [directory value from above query]/logfilename.log
    (make sure that you have write permission for this file and directory)
    WSH: Debug Enabled - Yes
    WSH: Debug Level - Statement
    2) do the end-user (for whom trace is enabled) need to have read and write permissions on the directory and the log file?
    Thanks
    Raju

    user652672 wrote:
    1) Please let me know what is the extension for debug log file....
    is it .dbg or .log ?
    INV: Debug File = [directory value from above query]/logfilename.log
    (make sure that you have write permission for this file and directory) It is what you set in the value of "INV: Debug File" profile option (according to the above value, it will be logfilename.log).
    2) do the end-user (for whom trace is enabled) need to have read and write permissions on the directory and the log file?No, just make sure the directory is writable by the oracle and applmgr users.

  • Changing the Naming convention of Log Files

    Hi,
    Is there a way to change the naming convention of log files. Instead of
    00000000.jdb, 00000001.jdb, ... to
    DB000000.jdb, DB000001.jdb etc
    Thanks in advance.

    No, there isn't a way to do that. We didn't anticipate a need to do that -- could you please explain the need?
    Putting a prefix on the file name would unnecessarily limit the total size of the data set, if file names are limited to the 8.dot.3 format as you've shown.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How do i record all exception in log file?

    Hi,
    how can i record my all exceptions in a log file? So it is easy for me......thnx.

    By using the jdk1.4 Logger class in the java.util.logging package (or an external product like Log4J if you're using jdk1.3 and lower), and putting the log statements in your catch blocks to record the exceptions thrown?

  • How to change the loacation of tenpdb, log files on server without reinstal

    Hi
    I completed the installation of EP, MS SQL and Web AS Java on Win 2003 Server.
    Now I want to change the destination drive for the log file, ms sql data and the tempdb. files in the server. Can anyone guide me to accomplish this without reinstallation.
    thanks in advance
    Regards
    Madhu

    Hi
    Thanks for the information.
    I am unable to locate the Homogeneous guide. can you please send it to me (my email [email protected])
    Also can you please explain how to dettach and attach the db from ms sql and also where would I have to indicate the new location for the Temp, & log files.
    Thanks
    Regards
    Madhu

  • How to know the history of shrinking log files in mssql

    hello,
    In my SAP system some one shrinked the log file to 100 GB to 5 GB.How we would check when this
    was shrinked recently .
    Regards,
    ARNS.

    hi,
    Did u check the logfile in sapdirectory.There will be entry of who changed the size and the time.
    Also,
    Goto the screen where we usually change the logfile size.In that particular field press f1 and goto technical setting screen. Get the program name , table name  and field name.
    Now using se11 try to open the table and check whether the changed by value is there for that table.
    Also open the program and debug at change log file process block.use can see in which table it update the changes.
    There is a case of caution in this case.
    The size of the application server's System Log is determined by the
    following SAP profile parameters. Once the current System Log reaches
    the maximum file size, it gets moved to the old_file and and a new
    System Log file gets created. The number of past days messages in the
    System Log depends on the amount/activity of System Log messages and the
    max file size. Once messages get rolled off the current and old files,
    they are no longer retrievable.
    rslg/local/file /usr/sap/<SID>/D*/log/SLOG<SYSNO>
    rslg/local/old_file /usr/sap/<SID>/D*/log/SLOGO<SYSNO>
    rslg/max_diskspace/local 1000000
    rslg/central/file /usr/sap/<SID>/SYS/global/SLOGJ
    rslg/central/old_file /usr/sap/<SID>/SYS/global/SLOGJO
    rslg/max_diskspace/central 4000000  .

  • Exceptions at log file while creating a repository service

    Hello,
    I have implemented a repository service and set it to respond to all events. The service is writing itself at the correct repositories but doesn't respond to any event. By going over the log files I found the following logs. Can someone please tell me if he sees something that can cause this?
    Devtlev: If you are reading this post (and I'm sure you will at some point... ), it is a continuation to our long long repository service post, but I thought it would be better to open new one
    // Log when deployingThe Repository Service
    #1.5#000BCDFB696800620000004100001A200003FAA9C0F55D3A#1120031924082#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###An upload sequence will start now. Please do not stop the server or serious deployment issues may arise.#
    #1.5#000BCDFB696800620000004400001A200003FAA9C0F749B6#1120031924207#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###The upgrades of the upload sequence will start now, there are 1 upgrade(s) to perform#
    #1.5#000BCDFB696800620000004500001A200003FAA9C0F74A6B#1120031924207#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###Processing upgrade: 1 out of 1. Config archive: RepositoryServices.prjconfig#
    #1.5#000BCDFB696800620000004600001A200003FAA9C1050406#1120031925114#com.sapportals.config.fwk.util.BasicConfigurable#sap.com/irj#com.sapportals.config.fwk.util.BasicConfigurable#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning##Plain###configurable [counter.CounterService] instance of [configclass_config://install/cm/repository_services/counter.CounterService] has a property without corresponding attribute: active#
    #1.5#000BCDFB696800620000004700001A200003FAA9C105055B#1120031925114#com.sapportals.config.fwk.util.BasicConfigurable#sap.com/irj#com.sapportals.config.fwk.util.BasicConfigurable#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning##Plain###configurable [counter.CounterService] instance of [configclass_config://install/cm/repository_services/counter.CounterService] has a property without corresponding attribute: description#
    #1.5#000BCDFB696800620000004B00001A200003FAA9C22E421E#1120031944597#com.sapportals.portal.prt.service.config.UpgraderBridge#sap.com/irj#com.sapportals.portal.prt.service.config.UpgraderBridge#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###Time to import the configuration of RepositoryServices.prjconfig: 19796#
    #1.5#000BCDFB696800620000004D00001A200003FAA9C22E5257#1120031944597#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###The upload sequence is now complete, all the upgrades have been performed.#
    #1.5#000BCDFB696800620000005300001A200003FAA9C230142B#1120031944706#com.sapportals.wcm.crt.CrtClassLoaderRegistry#sap.com/irj#com.sapportals.wcm.crt.CrtClassLoaderRegistry#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning#1#/Applications/KMC/CRT#Plain###register new classloader with id = null#
    // Log when entering the KM under Content Administration -> KM Content
    #1.5#000BCDFB6968003E0000008400001A200003FAA9CD1A7029#1120032127601#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16881e10e87411d9ce5b000bcdfb6968#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
    #1.5#000BCDFB696800600000004F00001A200003FAA9CD2343A8#1120032128179#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16e05030e87411d9ae07000bcdfb6968#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
    #1.5#000BCDFB696800510000002A00001A200003FAA9CD237B8D#1120032128195#com.sapportals.wcm.repository.runtime.CmSystem#sap.com/irj#com.sapportals.wcm.repository.runtime.CmSystem#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#/Applications/KMC/RF#Plain###CM system is starting ...
    #1.5#000BCDFB6968006C0000003500001A200003FAA9CD257EF1#1120032128320#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
    #1.5#000BCDFB6968006C0000003800001A200003FAA9CD259C9B#1120032128335#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
    #1.5#000BCDFB6968006C0000003B00001A200003FAA9CD25AB06#1120032128335#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
    #1.5#000BCDFB696800510000002B00001A200003FAA9CD405BCE#1120032130085#com.sapportals.wcm.protocol.webdav.UriMetaMap#sap.com/irj#com.sapportals.wcm.protocol.webdav.UriMetaMap#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Warning##Plain###replacing existing mapping WebUriMapper[/www/ep6sp9test <-> http://ep6sp9test.justice.gov.il/]#
    #1.5#000BCDFB696800510000002C00001A200003FAA9CD6649D1#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.api.NoSuchUserException: The given ID "RoyC" is not valid!#
    #1.5#000BCDFB696800510000002D00001A200003FAA9CD665926#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:134)#
    #1.5#000BCDFB696800510000002E00001A200003FAA9CD665A6A#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
    #1.5#000BCDFB696800510000002F00001A200003FAA9CD665BBC#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
    #1.5#000BCDFB696800510000003000001A200003FAA9CD665D8F#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at counter.CounterService.startUpImpl(CounterService.java:61)#
    #1.5#000BCDFB696800510000003100001A200003FAA9CD665F1D#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
    #1.5#000BCDFB696800510000003200001A200003FAA9CD666052#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
    #1.5#000BCDFB696800510000003300001A200003FAA9CD6661CE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
    #1.5#000BCDFB696800510000003400001A200003FAA9CD666301#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
    #1.5#000BCDFB696800510000003500001A200003FAA9CD666434#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
    #1.5#000BCDFB696800510000003600001A200003FAA9CD666569#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
    #1.5#000BCDFB696800510000003700001A200003FAA9CD666694#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
    #1.5#000BCDFB696800510000003800001A200003FAA9CD6667B1#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
    #1.5#000BCDFB696800510000003900001A200003FAA9CD666925#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
    #1.5#000BCDFB696800510000003A00001A200003FAA9CD666B06#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
    #1.5#000BCDFB696800510000003B00001A200003FAA9CD666C7B#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
    #1.5#000BCDFB696800510000003C00001A200003FAA9CD666DB2#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
    #1.5#000BCDFB696800510000003D00001A200003FAA9CD666ED3#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
    #1.5#000BCDFB696800510000003E00001A200003FAA9CD666FFD#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
    #1.5#000BCDFB696800510000003F00001A200003FAA9CD667132#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
    #1.5#000BCDFB696800510000004000001A200003FAA9CD667271#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.prepareNestedControls(WdfProxy.java:1302)#
    #1.5#000BCDFB696800510000004100001A200003FAA9CD6673C7#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.createNestedControls(WdfProxy.java:1209)#
    #1.5#000BCDFB696800510000004200001A200003FAA9CD6674EA#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Control.create(Control.java:291)#
    #1.5#000BCDFB696800510000004300001A200003FAA9CD6676AF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.create(WdfProxy.java:1280)#
    #1.5#000BCDFB696800510000004400001A200003FAA9CD667867#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:464)#
    #1.5#000BCDFB696800510000004500001A200003FAA9CD6679B6#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000004600001A200003FAA9CD667AD3#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
    #1.5#000BCDFB696800510000004700001A200003FAA9CD667BED#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000004800001A200003FAA9CD667D13#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
    #1.5#000BCDFB696800510000004900001A200003FAA9CD667E40#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000004A00001A200003FAA9CD667F70#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
    #1.5#000BCDFB696800510000004B00001A200003FAA9CD66809D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000004C00001A200003FAA9CD66818D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:268)#
    #1.5#000BCDFB696800510000004D00001A200003FAA9CD6682AB#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)#
    #1.5#000BCDFB696800510000004E00001A200003FAA9CD66838A#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:32)#
    #1.5#000BCDFB696800510000004F00001A200003FAA9CD66847A#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.Container.preRender(Container.java:118)#
    #1.5#000BCDFB696800510000005000001A200003FAA9CD668550#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.Container.preRender(Container.java:118)#
    #1.5#000BCDFB696800510000005100001A200003FAA9CD668734#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.Container.preRender(Container.java:118)#
    #1.5#000BCDFB696800510000005200001A200003FAA9CD66889C#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.rendering.PageContext.render(PageContext.java:936)#
    #1.5#000BCDFB696800510000005300001A200003FAA9CD6689CF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)#
    #1.5#000BCDFB696800510000005400001A200003FAA9CD668AD8#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)#
    #1.5#000BCDFB696800510000005500001A200003FAA9CD668CAE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)#
    #1.5#000BCDFB696800510000005600001A200003FAA9CD668E04#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)#
    #1.5#000BCDFB696800510000005700001A200003FAA9CD668F2F#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)#
    #1.5#000BCDFB696800510000005800001A200003FAA9CD669041#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000BCDFB696800510000005900001A200003FAA9CD66921D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:100)#
    #1.5#000BCDFB696800510000005A00001A200003FAA9CD6693B8#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:321)#
    #1.5#000BCDFB696800510000005B00001A200003FAA9CD669503#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)#
    #1.5#000BCDFB696800510000005C00001A200003FAA9CD669638#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#
    #1.5#000BCDFB696800510000005D00001A200003FAA9CD669776#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#
    #1.5#000BCDFB696800510000005E00001A200003FAA9CD6698AE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
    #1.5#000BCDFB696800510000005F00001A200003FAA9CD6699DF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
    #1.5#000BCDFB696800510000006000001A200003FAA9CD669B11#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
    #1.5#000BCDFB696800510000006100001A200003FAA9CD669C39#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
    #1.5#000BCDFB696800510000006200001A200003FAA9CD669D73#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)#
    #1.5#000BCDFB696800510000006300001A200003FAA9CD669F50#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
    #1.5#000BCDFB696800510000006400001A200003FAA9CD66A0F4#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
    #1.5#000BCDFB696800510000006500001A200003FAA9CD66A240#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
    #1.5#000BCDFB696800510000006600001A200003FAA9CD66A362#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#
    #1.5#000BCDFB696800510000006700001A200003FAA9CD66A47E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)#
    #1.5#000BCDFB696800510000006800001A200003FAA9CD66A5BC#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)#
    #1.5#000BCDFB696800510000006900001A200003FAA9CD66A6E2#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#000BCDFB696800510000006A00001A200003FAA9CD66A82E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
    #1.5#000BCDFB696800510000006B00001A200003FAA9CD66A958#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000BCDFB696800510000006C00001A200003FAA9CD66AA75#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)#
    #1.5#000BCDFB696800510000006D00001A200003FAA9CD66AC60#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000BCDFB696800510000006E00001A200003FAA9CD66ADF1#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)#
    #1.5#000BCDFB696800510000006F00001A200003FAA9CD66AF30#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)#
    #1.5#000BCDFB696800510000007000001A200003FAA9CD66B04D#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)#
    #1.5#000BCDFB696800510000007100001A200003FAA9CD66B166#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)#
    #1.5#000BCDFB696800510000007200001A200003FAA9CD66B29B#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)#
    #1.5#000BCDFB696800510000007300001A200003FAA9CD66B3C6#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)#
    #1.5#000BCDFB696800510000007400001A200003FAA9CD66B4FD#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#000BCDFB696800510000007500001A200003FAA9CD66B626#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#000BCDFB696800510000007600001A200003FAA9CD66B740#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)#
    #1.5#000BCDFB696800510000007700001A200003FAA9CD66B930#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)#
    #1.5#000BCDFB696800510000007800001A200003FAA9CD66BAE7#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#000BCDFB696800510000007900001A200003FAA9CD66BC1A#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#000BCDFB696800510000007A00001A200003FAA9CD66BD2E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)#
    #1.5#000BCDFB696800510000007B00001A200003FAA9CD66BE38#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)#
    #1.5#000BCDFB696800510000007C00001A200003FAA9CD66BF5C#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###----
    caused by -
    #1.5#000BCDFB696800510000007D00001A200003FAA9CD66C07D#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.core.persistence.datasource.PersistenceException: The given ID "RoyC" is not valid!#
    #1.5#000BCDFB696800510000007E00001A200003FAA9CD66D01F#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.splitPrincipalDatabagID(DataSourceBaseImplementation.java:492)#
    #1.5#000BCDFB696800510000007F00001A200003FAA9CD66D1FB#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.PrincipalFactory.getPrincipalType(PrincipalFactory.java:123)#
    #1.5#000BCDFB696800510000008000001A200003FAA9CD66D3C0#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:127)#
    #1.5#000BCDFB696800510000008100001A200003FAA9CD66D517#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
    #1.5#000BCDFB696800510000008200001A200003FAA9CD66D633#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
    #1.5#000BCDFB696800510000008300001A200003FAA9CD66D742#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at counter.CounterService.startUpImpl(CounterService.java:61)#
    #1.5#000BCDFB696800510000008400001A200003FAA9CD66D86E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
    #1.5#000BCDFB696800510000008500001A200003FAA9CD66D9A1#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
    #1.5#000BCDFB696800510000008600001A200003FAA9CD66DB03#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
    #1.5#000BCDFB696800510000008700001A200003FAA9CD66DC3B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
    #1.5#000BCDFB696800510000008800001A200003FAA9CD66DD5A#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
    #1.5#000BCDFB696800510000008900001A200003FAA9CD66DECD#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
    #1.5#000BCDFB696800510000008A00001A200003FAA9CD66E096#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
    #1.5#000BCDFB696800510000008B00001A200003FAA9CD66E20E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
    #1.5#000BCDFB696800510000008C00001A200003FAA9CD66E33B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
    #1.5#000BCDFB696800510000008D00001A200003FAA9CD66E464#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
    #1.5#000BCDFB696800510000008E00001A200003FAA9CD66E57D#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
    #1.5#000BCDFB696800510000008F00001A200003FAA9CD66E6B8#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
    #1.5#000BCDFB696800510000009000001A200003FAA9CD66E7F7#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
    #1.5#000BCDFB696800510000009100001A200003FAA9CD66E92F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
    #1.5#000BCDFB696800510000009200001A200003FAA9CD66EA5C#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
    #1.5#000BCDFB696800510000009300001A200003FAA9CD66EDA0#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.prepareNestedControls(WdfProxy.java:1302)#
    #1.5#000BCDFB696800510000009400001A200003FAA9CD66EF2B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.createNestedControls(WdfProxy.java:1209)#
    #1.5#000BCDFB696800510000009500001A200003FAA9CD66F066#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Control.create(Control.java:291)#
    #1.5#000BCDFB696800510000009600001A200003FAA9CD66F186#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.create(WdfProxy.java:1280)#
    #1.5#000BCDFB696800510000009700001A200003FAA9CD66F29B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:464)#
    #1.5#000BCDFB696800510000009800001A200003FAA9CD66F3D4#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000009900001A200003FAA9CD66F4FC#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
    #1.5#000BCDFB696800510000009A00001A200003FAA9CD66F62F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000009B00001A200003FAA9CD66F72E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
    #1.5#000BCDFB696800510000009C00001A200003FAA9CD66F843#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000009D00001A200003FAA9CD66F92E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
    #1.5#000BCDFB696800510000009E00001A200003FAA9CD66F9F7#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
    #1.5#000BCDFB696800510000009F00001A200003FAA9CD66FABF#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:268)#
    #1.5#000BCDFB69680051000000A000001A200003FAA9CD66FC22#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)#
    #1.5#000BCDFB69680051000000A100001A200003FAA9CD66FDDF#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:32)#
    #1.5#000BCDFB69680051000000A200001A200003FAA9CD66FF3C#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.Container.preRender(Container.java:118)#
    #1.5#000BCDFB69680051000000A300001A200003FAA9CD670042#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.Container.preRender(Container.java:118)#
    #1.5#000BCDFB69680051000000A400001A200003FAA9CD670207#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.Container.preRender(Container.java:118)#
    #1.5#000BCDFB69680051000000A500001A200003FAA9CD670360#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.rendering.PageContext.render(PageContext.java:936)#
    #1.5#000BCDFB69680051000000A600001A200003FAA9CD670467#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)#
    #1.5#000BCDFB69680051000000A700001A200003FAA9CD670558#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)#
    #1.5#000BCDFB69680051000000A800001A200003FAA9CD67063E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)#
    #1.5#000BCDFB69680051000000A900001A200003FAA9CD67071D#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)#
    #1.5#000BCDFB69680051000000AA00001A200003FAA9CD6707FB#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)#
    #1.5#000BCDFB69680051000000AB00001A200003FAA9CD6708D6#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000BCDFB69680051000000AC00001A200003FAA9CD6709AA#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:100)#
    #1.5#000BCDFB69680051000000AD00001A200003FAA9CD670AC3#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:321)#
    #1.5#000BCDFB69680051000000AE00001A200003FAA9CD670BE6#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)#
    #1.5#000BCDFB69680051000000AF00001A200003FAA9CD670D10#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#
    #1.5#000BCDFB69680051000000B000001A200003FAA9CD670ED4#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#
    #1.5#000BCDFB69680051000000B100001A200003FAA9CD67109E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
    #1.5#000BCDFB69680051000000B200001A200003FAA9CD671202#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
    #1.5#000BCDFB69680051000000B300001A200003FAA9CD67132E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
    #1.5#000BCDFB69680051000000B400001A200003FAA9CD671447#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
    #1.5#000BCDFB69680051000000B500001A200003FAA9CD671574#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)#
    #1.5#000BCDFB69680051000000B600001A200003FAA9CD67169F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
    #1.5#000BCDFB69680051000000B700001A200003FAA9CD6717D8#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
    #1.5#000BCDFB69680051000000B800001A200003FAA9CD67190F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
    #1.5#000BCDFB69680051000000B900001A200003FAA9CD671A2E#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#
    #1.5#000BCDFB69680051000000BA00001A200003FAA9CD671BF6#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)#
    #1.5#000BCDFB69680051000000BB00001A200003FAA9CD671DB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)#
    #1.5#000BCDFB69680051000000BC00001A200003FAA9CD671EFE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#000BCDFB69680051000000BD00001A200003FAA9CD672044#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
    #1.5#000BCDFB69680051000000BE00001A200003FAA9CD672159#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000BCDFB69680051000000BF00001A200003FAA9CD67227C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)#
    #1.5#000BCDFB69680051000000C000001A200003FAA9CD6723A8#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000BCDFB69680051000000C100001A200003FAA9CD6724D7#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)#
    #1.5#000BCDFB69680051000000C200001A200003FAA9CD6725FB#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)#
    #1.5#000BCDFB69680051000000C300001A200003FAA9CD672716#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)#
    #1.5#000BCDFB69680051000000C400001A200003FAA9CD6728EB#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)#
    #1.5#000BCDFB69680051000000C500001A200003FAA9CD672A9C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)#
    #1.5#000BCDFB69680051000000C600001A200003FAA9CD672BF0#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)#
    #1.5#000BCDFB69680051000000C700001A200003FAA9CD672D0F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#000BCDFB69680051000000C800001A200003FAA9CD672E22#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#000BCDFB69680051000000C900001A200003FAA9CD672F4E#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)#
    #1.5#000BCDFB69680051000000CA00001A200003FAA9CD67309C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)#
    #1.5#000BCDFB69680051000000CB00001A200003FAA9CD6731D4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#000BCDFB69680051000000CC00001A200003FAA9CD6732E5#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#000BCDFB69680051000000CD00001A200003FAA9CD6733F2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)#
    #1.5#000BCDFB69680051000000CE00001A200003FAA9CD6735DA#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)#
    #1.5#000BCDFB69680051000000CF00001A200003FAA9CD673771#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###----
    caused by -
    #1.5#000BCDFB69680051000000D000001A200003FAA9CD6738B2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.core.persistence.datasource.PersistenceException: The given ID "RoyC" is not valid!#
    #1.5#000BCDFB69680051000000D100001A200003FAA9CD6739D8#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.splitPrincipalDatabagID(DataSourceBaseImplementation.java:492)#
    #1.5#000BCDFB69680051000000D200001A200003FAA9CD673AFF#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.PrincipalFactory.getPrincipalType(PrincipalFactory.java:123)#
    #1.5#000BCDFB69680051000000D300001A200003FAA9CD673C2F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:127)#
    #1.5#000BCDFB69680051000000D400001A200003FAA9CD673D53#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
    #1.5#000BCDFB69680051000000D500001A200003FAA9CD673E8A#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
    #1.5#000BCDFB69680051000000D600001A200003FAA9CD673FB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at counter.CounterService.startUpImpl(CounterService.java:61)#
    #1.5#000BCDFB69680051000000D700001A200003FAA9CD6740CE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
    #1.5#000BCDFB69680051000000D800001A200003FAA9CD6742E2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
    #1.5#000BCDFB69680051000000D900001A200003FAA9CD67447D#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
    #1.5#000BCDFB69680051000000DA00001A200003FAA9CD6745BE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
    #1.5#000BCDFB69680051000000DB00001A200003FAA9CD6746D6#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
    #1.5#000BCDFB69680051000000DC00001A200003FAA9CD6747F1#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
    #1.5#000BCDFB69680051000000DD00001A200003FAA9CD674927#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
    #1.5#000BCDFB69680051000000DE00001A200003FAA9CD674A53#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
    #1.5#000BCDFB69680051000000DF00001A200003FAA9CD674B83#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
    #1.5#000BCDFB69680051000000E000001A200003FAA9CD674CB0#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
    #1.5#000BCDFB69680051000000E100001A200003FAA9CD674DCE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
    #1.5#000BCDFB69680051000000E200001A200003FAA9CD674FB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
    #1.5#000BCDFB69680051000000E300001A200003FAA9CD67514B#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
    #1.5#000BCDFB69680051000000E400001A200003FAA9CD675293#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
    #1.5#000BCDFB69680051000000E500001A200003FAA9CD6753BD#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###     at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
    #1.5#000BCDFB69680051000000E600001A200003FAA9CD6754FD#1120032132647#System.err#sap.com/irj#Syste

    Hi Roy,
    for the first log entry, see this posting: /thread/41655 [original link is broken]
    Search for "property without corresponding attribute" in it and have a look at my answer.
    The second error is, to be short:
    com.sap.security.api.NoSuchUserException: The given ID "RoyC" is not valid!#
    ... at counter.CounterService.startUpImpl(CounterService.java:61)#
    Have a look at your own code what's wrong with it (seems that you pass your user ID instead of uniqueID). Use getUserByLogonID(...) instead.
    Hope it helps
    Detlev

Maybe you are looking for

  • Problem hanging that I can't seem to fix

    I generally leave my MBP on all the time. Twice when I've returned to it over the last three days, it is locked at the desktop. It has not gone into sleep mode and I need to press the power button in order to restart the machine. Of course, it then t

  • Indesign CS4 Crashes When Printing to PDF

    Hi all, I've been having an issue lately with InDesign CS4 crashing every time I print to PDF. I've never had the issue before, but now it seems to happen constantly. I am running Windows 7, and when I print to PDF, my dialog box gets to "DOWNLOADING

  • Scale on x axis for radians

    Hi, I'm trying to make a cosine plot and have run into trouble. I've described the issues in this thread: http://discussions.apple.com/thread.jspa?messageID=12507456#12507456 The main issue is that I have 24 points on the abscissa, which run from 0 t

  • Oracle 9i download - setup.exe doesn't do anything

    I downloaded the three files for EE 9i, extracted to Disk1,2,3 etc. When I run setup.exe nothing happens. If I run setup.exe and watch task manager I see javaw.exe runs but then stops - there are no error messages, only ORA..... directories full of f

  • Why does my ipod not work when i plug it into the wall and work when i plug it into my computer?

    hello?