After Upgrade, INCOMING and OUTGOING settings page has errors.

After upgrading from 4.4 to 5.1.1 64-bit, Windows Server 2008R2 and SQL 2008, the INCOMING and OUTGOING pages for mail configuration will not work, and receive an error on the page. I have removed all of the old mail settings from the services page and checked the configuration files for anything regarding mail setup and have found nothing.

the jirauser permissions in the SQL Database are DBA.

I have checked all the things suggested by someone on the

Below id the beginning of error message on the OUTGOING mail handler page: (On the INCOMING page, it says 'getPopMailServers' instead of getSmtpMailServers) If you would like the entire messages, let me know.

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getSmtpMailServers' in class com.atlassian.jira.plugins.mail.webwork.ViewMailServers threw exception java.lang.RuntimeException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, NAME, DESCRIPTION, mailfrom, PREFIX, smtp_port, protocol, server_type, SERVERNAME, JNDILOCATION, mailusername, mailpassword, ISTLSREQUIRED, TIMEOUT, socks_port, socks_host FROM mailserver ORDER BY ID asc (Invalid column name 'socks_port'.) at /secure/admin/views/smtpServers.vm line 5, column 18 at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute( at org.apache.velocity.runtime.parser.node.ASTReference.execute( at org.apache.velocity.runtime.parser.node.ASTReference.evaluate( at org.apache.velocity.runtime.parser.node.ASTNotNode.evaluate( at org.apache.velocity.runtime.parser.node.ASTExpression.evaluate( at org.apache.velocity.runtime.parser.node.ASTIfStatement.render( at org.apache.velocity.runtime.parser.node.SimpleNode.render( at org.apache.velocity.runtime.directive.Parse.render( at org.apache.velocity.runtime.parser.node.ASTDirective.render( at org.apache.velocity.runtime.parser.node.ASTBlock.render( at org.apache.velocity.runtime.parser.node.ASTIfStatement.render( at org.apache.velocity.runtime.parser.node.SimpleNode.render( at org.apache.velocity.Template.merge( at org.apache.velocity.Template.merge( at at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(

1 answer

0 vote

Hi Troy,

This looks like a new bug. I've filed it here



Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,317 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot