Email is not being sent after upgrading Jira Align Self-Hosted
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
Summary
After updating Jira Align On-Premise to 10.110 or higher, emails stop being sent.
Environment
Jira Align Self-Hosted
Diagnosis
Emails display with "pending" status under Administration > Logs > Email
The following errors are reported in Jira Align's backoffice service log AgileCraft_BackOffice_*.log
1
2
3
4
5
6
Could not load file or assembly 'file:///C:XXXXXXXXX\\BackofficeService\\ServiceTasks.BackOffice.dll' or one of its dependencies.
An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework.
This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous.
If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch.
See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.Cause
This error can occur due to the .NET Framework 4 and later default policy which prohibits remote assemblies from running. Jira Align 10.110 and higher requires .NET Framework 4.8 as documented in:
Upcoming changes to Jira Align .NET requirements for on-premise instances in 10.110.0
As documented in Microsoft documentation: <loadFromRemoteSources> Element
In the .NET Framework version 3.5 and earlier versions, if you loaded an assembly from a remote location, the assembly would run partially trusted with a grant set that depended on the zone in which it was loaded. For example, if you loaded an assembly from a website, it was loaded into the Internet zone and granted the Internet permission set. In other words, it is executed in an Internet sandbox. If you try to run that assembly in the .NET Framework version 4 and later versions, an exception is thrown.
The <loadFromRemoteSources> element lets you specify that the assemblies that would have run partially trusted in earlier versions of the .NET Framework are to be run fully trusted in the .NET Framework 4 and later versions. By default, remote assemblies do not run in the .NET Framework 4 and later.
Solution
Grant the BackOffice assembly permission to run using the following steps:
As a Windows Admin, log into the Jira Align application server
Launch Services, and stop the BackOffice service ->
AgileCraft_Backoffice_[CUSTOMER_NAME]Make a backup copy of the file
C:\[ROOT_DIRECTORY]\BackofficeService\AgileCraft.Backbone.exe.ConfigCopy
AgileCraft.Backbone.exe.configfromC:\[ROOT_DIRECTORY]\Releases\[VERSION]\Sources\BackofficeServicetoC:\[ROOT_DIRECTORY]\BackofficeService– this will replace your current file.With a text editor (e.g. Notepad++), edit
AgileCraft.Backbone.exe.configLocate the <connectionStrings> tag and add your SQL DB information (SERVERNAME,USERNAME,PASSWORD):
1<connectionStrings> <add name="Metabase" connectionString="Data Source=SERVERNAME;Initial Catalog=AgileCraftServer;Integrated Security=False;User Id=USERNAME;Password=PASSWORD;MultipleActiveResultSets=True;Encrypt=yes;TrustServerCertificate=True;" /> </connectionStrings>Locate the <runtime> tag and add the <loadFromRemoteSources enabled="true"/> tag immediately after it:
1 2 3<runtime> <loadFromRemoteSources enabled="true"/> ...Save the file.
Switch back to Services, then start the
BackOfficeservice.
Was this helpful?