Customer notifications are not working (they are not sent) in Service Desk 4.0.1 when connecting to a MS SQL database.
- Install a fresh JSD 4.0.1 instance
- Connect it to a MS SQL database by following the instructions in Connecting JIRA to MS SQL 2014
- Configure an outgoing mail server in ⚙ > System > Outgoing Mail
- Create a new Service Desk project
- Log into the customer portal with a customer account
- Create a new SD request
- Open the request from the agent view, by logging with an agent account, and add a public comment
The customer should have received 2 customer notifications
- the request created notification
- the public comment added notification
The customer did not receive any notification.
In fact, the table which contains the customer notification (AO_4E8AE6_NOTIF_BATCH_QUEUE) is completely empty, which means that no notification is created at all.
The following query returns no result at all:
If you are using JIRA with JAVA 8
- Stop JIRA
- Move the MS SQL driver mssql-jdbc-7.2.0.jre8.jar from the folder below (please make a backup of it or move it to a temporary folder)
- Copy the driver mssql-jdbc-6.2.1.jre8.jar to the same folder
- Start JIRA
If you are using JIRA with Java 11
Please note that we do not have a fully tested workaround for JIRA running with Java 11 and involving the replacement of the ms sql jdbc driver.
For this reason, as a workaround, what you can do is either downgrade to your previous version or 4.0.0 of Service Desk, which are both unaffected by this problem. Here are the steps you can follow to execute a downgrade. 8.0.0 might be your best bet since it's a closer down version to what you are on:
- Download the Jira ServiceDesk 4.0.0 Server installer from the link below to install Jira Core 8.0.0 + Service Desk 4.0.0: Update Jira Service Desk Server. You will want to click on View all versions to get to the 4.0.0 installer for Windows.
- Install Jira Service Desk Server 4.0.0 as a new separate standalone instance as a medium for the 'downgrade'. That being said, there should be a new JIRA_Home, JIRA_Installation, and new database for this Service Desk 4.0.0 instance on a new server.
- Once this new instance (4.0.0) is ready, shut it down.
- Allocate adequate application memory as per the Jira Sizing Guide and set the flag -Djira.downgrade.allowed=true on the JSD 4.0.0 instance as per our Setting properties and options on startup documentation for your new Windows instance. This is to allow the downgrade to run properly.
- Start the new 4.0.0 instance of Service Desk.
- Take a latest XML backup from your 4.0.1 Service Desk instance that you currently have that is encountering these issues.
- Restore the backup into the new 4.0.0 instance. There will be a message that needs to be acknowledged on the UI after selecting the backup for restoration. Acknowledge it, verify the correct backup file has been chosen and then click on the Restore button again to kick start the restoration process.
- Once this is done, your user will be logged out. Re-login to the 4.0.0 instance, ensure the JSD application is installed and licensed, and that you are able to run automation and send out notifications to customers on some test issues.
Other Service Desk functionalities are also impacted in Service Desk 4.0.1, when running with a MS SQL Database: