Jira error occurred communicating with the server can be easily resolved. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped a customer with a Jira error that occurred communicating with the server

All about the Jira error that occurred communicating with the server

If you have been coming across this Jira error:

"Error Occurred Communicating with the server. Please reload the page and try again."

It may be due to filtering issues in the issue navigator. It may also be due to loading a filter where the query utilizes a specific custom field. According to our Support Techs, you may also come across logs similar to those below in the atlassian-jira.log:

2021-03-21 05:42:03,663 http-bio-8180-exec-19 ERROR admin 342x15949x1 15kcaax 203.143.12.26,0:0:0:0:0:0:0:1 /rest/issueNav/1/issueTable [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service 
com.atlassian.cache.CacheException: com.atlassian.jira.exception.DataAccessException: Could not find any field config schemes for field config '10800' 
... 
Caused by: com.atlassian.jira.exception.DataAccessException: Could not find any field config schemes for field config '10800' 
	at com.atlassian.jira.issue.fields.config.persistence.FieldConfigSchemePersisterImpl.getConfigSchemeForFieldConfig(FieldConfigSchemePersisterImpl.java:208)

This error often pops up when a filter or search query uses a particular customer field in the search criteria. We can also detect affected fieldconfigurations using SQL as seen below:

select fc.id from fieldconfiguration fc left join fieldconfigschemeissuetype fcsit on (fc.id = fcsit.fieldconfiguration) where fcsit.id is null;

In fact, the error is due to a database integrity issue resulting from invalid entries in the fieldconfiguration table.

How to resolve Jira error occurred communicating with the server

Before we modify the database as a part of the solution, it is a good idea to back up the data.

1. First, we have to find the ID of the problematic entry in the field config table and check the ID in the stack trace. For instance, the above error log indicates the problematic ID as 10800.
2. Then, we have to run the SQL statements shown below against Jira database in order to delete the problematic entry in the fieldconfiguration table:

   delete from fieldconfiguration where id='10800'; 
   or
    // Delete all orphaned records in fieldconfiguration delete from fieldconfiguration where id in (select fc.id from fieldconfiguration fc left join fieldconfigschemeissuetype fcsit on (fc.id = fcsit.fieldconfiguration) where fcsit.id is null);
3. After that, we have to check if the previous step caused any orphaned records in the customfieldoption table as seen below:

   select count (customfieldconfig) from customfieldoption where customfieldconfig not in (select id from fieldconfiguration ); 
   count ------- 0
4. Finally, we have to restart the Jira instance in order for the changes to take effect.

[Looking for another solution to this query? We are just a click away.]

Conclusion

To conclude, the skilled Support Engineers at Bobcares demonstrated how to resolve the Jjira error that occurred communicating while with the server.