View user in administrative screens give null pointer exception
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When trying to view a user in the administrative screens, a system error is thrown similar to the following.
The following appears in the atlassian-confluence.log:
1
2
3
4
5
6
7
8
2012-07-06 21:28:10,266 ERROR [http-10.0.2.191-80-2] [atlassian.confluence.servlet.ConfluenceServletDispatcher] sendError Could not execute action
-- url: /admin/users/viewuser.action | userName: user | referer: http://confluence.example.com/admin/users/showallusers.action?searchTerm=*&usernameTerm=*&fullnameTerm=&emailTerm=&resultsPerPage=10&advanced=false&startIndex=0
org.apache.velocity.exception.MethodInvocationException: Invocation of method 'canRemove' in class com.atlassian.confluence.user.actions.ViewUserAction threw exception java.lang.NullPointerException at /admin/users/viewuser.vm[line 141, column 42]
at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262)
at org.apache.velocity.runtime.parser.node.ASTReference.evaluate(ASTReference.java:470)
at org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:62)Causes
Confluence user base is unchanged but has changed locations. For example, reverting from Crowd or JIRA to Internal User Management.
Confluence index has been corrupted
Resolution
Rebuild the Confluence index from scratch
ℹ️ These errors will also dissipate as on a per user basis as the index updates itself but rebuilding it from scratch will ensure they are all corrected all at once.
Was this helpful?