Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

While trying to start the reopository scan getting error

Karan Vora
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 8, 2025

While trying to start the reopository scan getting error

Error calling server:com.google.gwt.user.client.rpc.StatusCodeException: 500 The call failed on the server; see server log for details Unknown.Gd(AdminGwtModule-0.js) Unknown.Cib(AdminGwtModule-0.js) Unknown.XWb(AdminGwtModule-0.js) Unknown.new qXb(AdminGwtModule-0.js) Unknown.u$b(AdminGwtModule-0.js) Unknown.wqb(AdminGwtModule-0.js) Unknown.Kqb(AdminGwtModule-0.js) Unknown.eval(AdminGwtModule-0.js) Unknown.Njb(AdminGwtModule-0.js) Unknown.Qjb(AdminGwtModule-0.js) Unknown.eval(AdminGwtModule-0.js).

If i create a add new repo with same location the scan gets triggered without error

2 answers

0 votes
Anwesha Pan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 22, 2026

Hi @Karan Vora 👋🏻

First of all, welcome to community! ✨

To answer your question, I would suggest you to do the following steps:

  1. Check Server Logs: Search for the specific timestamp of the error in your log files. Look for "Exception" or "Error" entries that provide more detail than the GWT message.
  2. Permanent Replacement: Since adding a new repo with the same location fixes the issue, the simplest resolution is to delete the problematic repository record and continue using the new one.
  3. Update JRE: Ensure the server is running on a supported and updated JRE to avoid compatibility issues with older GWT modules.

I hope this helps & resolves your issue. 🙂

Thanks,
Anwesha

0 votes
Shawn Doyle - ReleaseTEAM
Community Champion
October 2, 2025

Hi @Karan Vora 

 

Is this all the Fisheye server logs tell you?  I would expect to see something like an out of memory error, or something that could lead us in the right direction.

If adding a 2nd repo works, it could be a misconfig in the server settings.  You can remove the line for that repo and see if it starts up. (always make a backup copy of the config file)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events