This error is affecting my desktop client of scrumworks pro 4.4. I can't access team manager, although I can access the user manager screen.
Any help?
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
avax.ejb.EJBException: javax.persistence.EntityNotFoundException: Unable to find com.danube.scrumworks.team.User with id -777170439116380989
-
Hello,
Were any user accounts deleted recently that may have been attached to a team?
Are you using MySQL or Hypersonic?
If you log in as the Global Administrator, does it have the same issue? Or is it only your personal admin account that is affected? -
-
Thanks Mark,
this was on Hypersonic. I editied scrumworks.script, removing the line that included that user ID
INSERT INTO TEAMS_USERS VALUES(-777170439116380989,752729677681983493)
and it seems to be working now.
I am still seeing lots of warnings: 19:52:08,591 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 1-a822b43:e269:4e36fa5f:b7e21ea822b43:e269:4e36fa5f:b7e225 >
do I need to worry about these? -
-
Many of the XAR resource errors are junk errors. In the current 5.1 version of Scrumworks reporting on most of those has been cleaned up to make the log less cluttered.
-
-
I'm also having this problem, using scrumworks pro 4.2.1. I believe one of our managers did some deleting of some accounts of former employees and now there's a couple of log messages like this whenever anyone tries to log in using the standalone java client, although the web client does fine.
I'm not the usual admin for our Scrumworks instance and I'm just getting oriented. It doesn't look like there's either a MySQL or Hypersonic instance running on the box. Is there somewhere else I should be looking for the database? -
-
Aha, got it with some help from Mark.
I located my mysql instance on another server, got in and found two dangling entries in the teams_users table pointing to non-existent users in the userejb table. Clearing them out fixed me up. -
Loading Profile...




EMPLOYEE

