on 10-15-2008 8:44 AM
Dear All,
i made changes in my custom logon.par file and uploaded it...now when i restarted the server it shows runtime error ...below is the log for that...Can nebody please solve this..
#
#1.5 #00188B76ACE8011902557F56000016580004586C65ABDED0#1223122492375#com.sap.caf.eu.gp.schedule.impl.ScheduleWorker##com.sap.caf.eu.gp.schedule.impl.ScheduleWorker#Guest#0####05d637608f5511dd80e200188b76ace8#SAPEngine_Application_Thread[impl:3]_31##0#0#Error#1#/System/Server#Plain###ERROR_ACQUIRE_CONNECTION
com.sap.caf.eu.gp.base.exception.EngineException: ERROR_ACQUIRE_CONNECTION
at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:92)
at com.sap.caf.eu.gp.schedule.impl.ScheduleDbImpl.getScheduleToProcess(ScheduleDbImpl.java:1936)
at com.sap.caf.eu.gp.schedule.impl.ScheduleService.getScheduleToProcess(ScheduleService.java:432)
at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.work(ScheduleWorker.java:81)
at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.run(ScheduleWorker.java:64)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
sfadevepapp
sapmnt
PDE
SYS
global
security
data
SecStore.properties" does not exist although it should..
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)
at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:89)
... 8 more
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
sfadevepapp
sapmnt
PDE
SYS
global
security
data
SecStore.properties" does not exist although it should..
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:193)
at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:188)
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
... 9 more
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
sfadevepapp
sapmnt
PDE
SYS
global
security
data
SecStore.properties" does not exist although it should..
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:117)
... 12 more
Caused by: com.sap.security.core.server.secstorefs.FileMissingException: File "
sfadevepapp
sapmnt
PDE
SYS
global
security
data
SecStore.properties" does not exist although it should.
at com.sap.security.core.server.secstorefs.StorageHandler.openExistingStore(StorageHandler.java:372)
at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1946)
at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
... 14 more
Regards,
Vinayak
Hi Vinayak,
If you have not changed any other code apart from HTML, this should not be the case.
Recheck the changes done and Run the Default component from portalapp.xml file.
If the PAR file is renamed, you will be having to replace the standard PAR name with new one in Authschemes.xml file in Configtool.
Regards,
Santhosh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.