nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Admin server Error : This VM does not support thread dumps

Sandesh AG

Am getting the below error while starting the Admin server. I tried deleting Adminserver.lok file but still getting the same error.

Please help me out to resolve the error.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

There are 1 nested errors:

weblogic.management.DeploymentException:

at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:129)

at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:191)

at weblogic.store.admin.DefaultStoreService.start(DefaultStoreService.java:60)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Caused by: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11

at weblogic.store.io.file.direct.DirectIONative.openConsiderLock(Native Method)

at weblogic.store.io.file.direct.DirectFileChannel.<init>(DirectFileChannel.java:54)

at weblogic.store.io.file.direct.DirectIOManager.open(DirectIOManager.java:179)

at weblogic.store.io.file.StoreFile.openInternal(StoreFile.java:112)

at weblogic.store.io.file.StoreFile.openDirect(StoreFile.java:168)

at weblogic.store.io.file.Heap.openStoreFile(Heap.java:398)

at weblogic.store.io.file.Heap.open(Heap.java:325)

at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:117)

at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:435)

at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:423)

at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:126)

... 5 more

<May 2, 2017 11:24:47 AM AST> <Critical> <Health> <BEA-310006> <Critical Subsystem PersistentStore._WLS_AdminServer has failed. Setting server state to FAILED.

Reason: weblogic.store.PersistentStoreFatalException: [Store:280105]The persistent file store "_WLS_AdminServer" cannot open file _WLS_ADMINSERVER000000.DAT.>

<May 2, 2017 11:24:47 AM AST> <Error> <> <BEA-000000> <***** This VM does not support thread dumps *****

Find more posts tagged with

Accepted answers

All comments

Gianni Ceresa

Hi,

Stop everything (if something is still running) and then delete the file(s) in .../user_projects/domains/<your domain: bi by default>/servers/AdminServer/data/store/default/ (you must have one file named _WLS_ADMINSERVER000000.DAT ).

Once deleted restart everything like you normally do (start.sh).

Syedsalmancs110

Hello Sandesh,

In addition to Gianni's update, since you already had AdminServer.lok file hence there is a chance that LDAP lok file must also be present, so verify and delete the same if found.

In general if a Weblogic Server(Admin or Managed) is not shutdown cleanly then before next startup you should verify and delete lock files from below mentioned location:

<DOMAIN HOME>/servers/<SERVER NAME>/tmp/<SERVER NAME>.lok

<DOMAIN HOME>/servers/<SERVER NAME>/data/ldap/ldapfiles/EmbeddedLDAP.lok

If you are deleting DAT files then do it from both the location mentioned below

<DOMAIN HOME>/servers/<SERVER NAME>/data/store/default

<DOMAIN HOME>/servers/<SERVER NAME>/data/store/diagnostics

You can also refer to below blog for Weblogic related lock file issues:

https://blogs.oracle.com/WebLogicServer/entry/potential_issues_with_weblogic_server

Thanks and Regards,

Syed Hamd Salman

Sandesh AG

Hi Gianni Ceresa and Syed Hamd Salman

I followed both the steps and now admin server issue got resolved. Admin server and Bi server started successfully and even opmn services also started.

Both Admin console and EM is opening without any problem.

But Analytics page is not opening.

I verified under servers in Console. Both Admin and Bi servers are in RUNNING mode.

Syedsalmancs110

Hi Sandesh,

Is presentation services up and running?

Execute opmnctl status command from <INSTANCE HOME>/bin location to verify status of BIEE Services.

what message is displayed when following URL http://machinename:port/analytics is used to launch analytics?

Please note port used in analytics URL is managed server port, default is 9704.

Thanks and Regards,

Syed Hamd Salman

Sandesh AG

Hi Syed Hamd Salman

Thanks for your quick reply,

Is presentation services up and running? - Yes (All services are running)

Port number and Ip address are correct. My url format is http://ip_address_of_instance:9704/analytics Before also I used to open with the same url. I have added the error message screenshot for your refernce.

But one thing I noticed here is after starting Bi_server if I keep the putty window open then after sometime am getting the below error message. I think because of this only Analytics is not opening.

Caused by: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User BISystemUser javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User BISystemUser denied

at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)

at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)

at java.security.AccessController.doPrivileged(Native Method)

at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)

at sun.reflect.GeneratedMethodAccessor385.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at javax.security.auth.login.LoginContext.invoke(LoginContext.java:762)

at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)

at javax.security.auth.login.LoginContext$4.run(LoginContext.java:690)

at javax.security.auth.login.LoginContext$4.run(LoginContext.java:688)

at java.security.AccessController.doPrivileged(Native Method)

at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:687)

at javax.security.auth.login.LoginContext.login(LoginContext.java:595)

at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)

at sun.reflect.GeneratedMethodAccessor383.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)

at com.sun.proxy.$Proxy34.login(Unknown Source)

at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)

at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)

at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)

at com.sun.proxy.$Proxy52.authenticate(Unknown Source)

at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)

at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)

at weblogic.security.services.Authentication.doLogin(Authentication.java:133)

at weblogic.security.services.Authentication.login(Authentication.java:74)

at weblogic.security.services.Authentication.login(Authentication.java:51)

at oracle.security.jps.wls.jaas.module.authentication.WlsUserAuthenticator.authenticate(WlsUserAuthenticator.java:59)

... 64 more

Syedsalmancs110

Looks like your System User password has corrupted and is out of sync, follow below steps and see if it helps resolve your issue:

a) Stop BIEE Services using opmnctl stopall command, from location <INSATNCE HOME>/bin

b) Then stop your Managed Server(bi_server1) either through console or from command line using command stopManagedWebLogic bi_server1 from location <DOMAIN HOME>/bin

c) Now keeping your Admin Server up and running reset your BISystemUser password in Console and EM

i) Log into Weblogic Console and change the BISystemUser password. Click on security realms > myreams > user and group

BISystemUser > Passwords

ii) Change password in EM:

Weblogic Domain > right click on bifoundation_domain > Security > Credentials > oracle.bi.system > system.user > Edit > change the password

d) Now stop your Admin Server(AdminServer) either through console or from command line using command stopWebLogic from location <DOMAIN HOME>/bin

e) Start your complete OBIEE Stack i.e. Admin Server, Managed Server and BIEE Services using OPMN.

Sandesh AG

Hi Syed Hamd Salman

While doing

i) Log into Weblogic Console and change the BISystemUser password. Click on security realms > myreams > user and group

It is not showing anything,

The screenshot I have added for your reference

But In EM I can change the password as you specified in step 2. But is it really required to that step?!!. Because both Admin Console and EM am able to login with old user credentials.

Syedsalmancs110

Yes both steps are mandatory, the reason you might not be able to view list of users in console is because some security configuration setting might have been performed and Activated but for it to be implemented restart of Weblogic Server is required.

a) Stop complete OBIEE Stack i.e. Admin Server, Managed Server and BIEE Services using OPMN.

b) Now only start Admin Server and do not start Managed Server and BIEE Services.

c) Perform BISystemUser password reset on Console and EM as mentioned in previous steps.

d) Once password reset is done then stop Admin Server as well and then start complete OBIEE Stack.

Sandesh AG

Hi Syed Hamd Salman

Appreciate your patience in replying to my post.

No luck! Even after restarting Admin server(stopping admin server and started only Admin server), I have performed below step,

i) Log into Weblogic Console and change the BISystemUser password. Click on security realms > myreams > user and group

It is not showing anything.

Screenshot is same as above reply

Syedsalmancs110

What does it show under Change Center within Weblogic Console Page on left hand side does it just show "Lock and Edit" or "Activate Changes" and "Revert Changes",attach complete Weblogic Console page screenshot