After Upgrade, INCOMING and OUTGOING settings page has errors.

TroyBailey August 6, 2012

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

https://answers.atlassian.com/questions/72125/can-t-modify-incoming-mail-parameters-after-upgrade

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(ASTIdentifier.java:223) 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.ASTNotNode.evaluate(ASTNotNode.java:63) at org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:62) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:85) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.runtime.directive.Parse.render(Parse.java:263) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.Template.merge(Template.java:328) at org.apache.velocity.Template.merge(Template.java:235) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:381) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java

1 answer

0 votes
Eric Dalgliesh
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 6, 2012

Hi Troy,

This looks like a new bug. I've filed it here https://jira.atlassian.com/browse/JRA-29244

Thanks,

Eric

Suggest an answer

Log in or Sign up to answer