Welcome to my blog...
Hello
I created this blog to share my minimal knowledge with others on the issues I came across, the POC's I did, Installations & Configurations I did on Oracle Fusion Middleware, OBIEE and Oracle Primavera Applications.
LinkedIn: https://in.linkedin.com/pub/vinoth-kumar-subramani/18/260/7b9
I created this blog to share my minimal knowledge with others on the issues I came across, the POC's I did, Installations & Configurations I did on Oracle Fusion Middleware, OBIEE and Oracle Primavera Applications.
LinkedIn: https://in.linkedin.com/pub/vinoth-kumar-subramani/18/260/7b9
Technical Issues and Solutions
- DB Related (1)
- OBIEE Related (1)
- OIM (1)
- Oracle VM Related (5)
- Primavera Related (2)
- SOA / BPM / OSB Related (1)
- Weblogic Related (6)
Monday, June 8, 2015
Tuesday, June 2, 2015
You Do Not Have A License To Run Primavera P6. Please Contact Your System Administrator
If you are getting You Do Not Have A License To Run Primavera P6. Please Contact Your System Administrator, while login to your P6 home, follow the below steps.
Solution 1.
1. Go to p6 home
2. Give full permissions (777) to the license directory and the file, kavachart.key inside license directory.
3. Restart P6 server.
Solution 2:
Possible Reasons:
1. If you have installed the Primavera with unsupported JDK, some times the exception "You Do Not Have A License To Run Primavera P6. Please Contact Your System Administrator" may occur.
2. Due to unsupported version of JDK, some times it will authenticate your user, but it wont go to the next page.
To over come this you need to uninstall the exististing JDK, Weblogic & EPPM and reinstall with the supporting JDK.
NOTE: before proceeding with the installation check the certification metrix and then proceed with the supported binaries.
Weblogic Admin Server is running and its health is in Falied sate - The persistent store "XXXXXX" does not exist, [Store:280105]The persistent file store "XAFileStore" cannot open file XAFILESTORE000000.DAT.
If your Weblogic Admin server is running and its health is Failed, with the below error, follow the given solution.
weblogic.management.DeploymentException:
Internal error activating the JMS Server XAJMSServer:
weblogic.management.DeploymentException: The persistent store
"XAFileStore" does not exist
weblogic.store.PersistentStoreFatalException:
[Store:280105]The persistent file store "XAFileStore" cannot open
file XAFILESTORE000000.DAT.
####<Jun 2, 2015 12:57:58 PM
SAST> <Error> <JMS> <zaflappmlvu01.next.mtn.com>
<AdminServer> <[ACTIVE] ExecuteThread: '1' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
<38c8073e-1b4a-425c-9a83-28f75f436aab-00000004> <1433242678319>
<BEA-040123> <Failed to start JMS Server "XAJMSServer" due
to weblogic.management.DeploymentException: The persistent store
"P6FileStore" does not exist.
Solution:
1.
Go to Admin console
-> Domain -> Services -> Messaging -> JMS Servers -> (JMS Server
name) -> Configuration -> General -> Untarget the Persistent
Store.
2.
Then Go Services
-> Messaging -> Persistent Stores -> Configuration -> Directory. Go
to that specific directory in the specified path and take a backup and delete
the contents in it.
3.
Now target the
Persistent Store to the JMS Server and restart the server.
Not able to bring up the Weblogic Admin server - [Store:280105]The persistent file store "WLS_DIAGNOSTICS" cannot open file WLS_DIAGNOSTICS000000.DAT.
If you are not able to bring up the Weblogic Server and it throws the below exception, follow the given solution.
No matching store mbean found for =WLS_DIAGNOSTICS, must be a default store.
No matching store mbean found for =WLS_DIAGNOSTICS, must be a default store.
<Jun 2, 2015 12:51:43 PM SAST> <Critical>
<WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.diagnostics.lifecycle.DiagnosticComponentLifecycleException:
weblogic.store.PersistentStoreFatalException: [Store:280105]The persistent file
store "WLS_DIAGNOSTICS" cannot open file WLS_DIAGNOSTICS000000.DAT.
at
weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:97)
at
weblogic.diagnostics.lifecycle.DiagnosticFoundationService.start(DiagnosticFoundationService.java:108)
at
weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at
weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at
weblogic.work.ExecuteThread.run(ExecuteThread.java:254)
Caused by: weblogic.store.PersistentStoreFatalException:
[Store:280105]The persistent file store "WLS_DIAGNOSTICS" cannot open
file WLS_DIAGNOSTICS000000.DAT
<Jun 2, 2015 12:51:43 PM SAST> <Critical>
<Health> <BEA-310006> <Critical subsystem
PersistentStore.WLS_DIAGNOSTICS has failed. Setting server state to FAILED.
Reason: weblogic.store.PersistentStoreFatalException:
[Store:280105]The persistent file store "WLS_DIAGNOSTICS" cannot open
file WLS_DIAGNOSTICS000000.DAT.>
***************************************************************************
The WebLogic Server encountered a critical failure
Reason: Assertion violated
***************************************************************************
Exception in thread "main"
java.lang.NoClassDefFoundError: Could not initialize class
weblogic.protocol.ServerIdentityManager$Initializer
Solution:
- Go to DOMAIN_HOME/servers/<SERVERNAME>/data/ldap/ldapfiles and remove the EmbeddedLDAP.lok lock file
- Delete the *.dat file under DOMAIN_HOME/servers/<SERVERNAME>/data /store/default and DOMAIN_HOME/servers/<SERVERNAME>/data /store/diagnostics/
- Remove the contents under DOMAIN_HOME/servers/<SERVERNAME>/ tmp and DOMAIN_HOME/servers/<SERVERNAME>/ cache
- Now start the server
Subscribe to:
Posts (Atom)