Unable to login to business central

[ganesh bambal]

Hi

I am running business central on Linux server but unable to login using wbadmin

Please help

Regards

Ganesh 

[Leonard Budney]

I'm having this issue as well: when I log into jBPM on the business-central-workbench-showcase docker image, using one of the predefined users (e.g., admin/admin), the login screen simply refreshes. This is strange, because I have successfully used that docker image not too long ago (perhaps a week or two?), and the image hasn't changed in 9 months.

The last line in /opt/jboss/wildfly/standalone/log/server.log is:

2024-05-18 23:03:59,770 INFO  [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-18-thread-1) Initialize deployments task finished successfully.

Scrolling back in the same log file, I do see an exception thrown:

2024-05-18 23:03:37,483 ERROR [org.uberfire.ext.metadata.io.BatchIndex] (Thread-118) Index fails. [@dashbuilder/datasets/m
aster]: java.util.concurrent.CompletionException: java.lang.RuntimeException: Repository not found inside space dashbuilde
r with path default://master@dashbuilder/datasets/definitions/gitContributors.dset (root path default://master@dashbuilder
/datasets/)

Any help would be very much appreciated.

Thanks!

[Leonard Budney]

A couple of people sent replies that I don't see here, so I'll post to let everyone know that this problem seems to be resolved.

I'm not sure why, but rebooting my machine resolved the login issue. I'm running business-central-workbench-showcase under docker-compose, so it was brought up automatically after reboot, and I was able to log in.

This is at least slightly interesting, because stopping the container and running a new one didn't resolve the problem; I tried that several times. I also blew away and recreated the persistent volume for .niogit, with no effect. I would expect running a new container is as good as a reboot, but t'weren't.

The suggestions I received were to try logging in as a different user (which didn't work before the reboot), and running an earlier version of the container (which I didn't try because the reboot cleared up the problem).

Thanks all!

[Carlos Gamboa Hernández]

Are you able to log in with another user? Perhaps something changed at the permissions level, the same happened to me when foolishly I changed the permissions for one of the roles that wbadmin was assigned to. Then I logged in with kieserver user and reverted the latest changes I made. And I solved it.

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/bbba5cc3-fa0b-4509-9894-b673846d3adbn%40googlegroups.com.

--

     Carlos Humberto Gamboa Hernandez

       Java Architect and Software specialist

[ganesh bambal]

Hello,
please try to login using incognito mode.

if that doesn't work

try to use the previous version of docker image.

I was facing this issue for jbpm standalone 7.74 when I downgraded to jbpm standalone 7.69 it worked fine.
Regards.
Ganesh 

--