-
Bug
-
Resolution: Fixed
-
Low
-
2.0.2, 2.3.2
Environment:
JIRA 6.2.7
Service desk 2.0.2
MS SQL Server 2008 R2/2012 with the database collation type = SQL_Latin1_General_CP1_CI_AS or SQL_Latin1_General_CP437_CI_AI
When trying to add an existent user as an agent, JIRA throws the following error:
Error There was a SQL exception thrown by the Active Objects library: Database: - name:Microsoft SQL Server - version:10.50.2500 - minor version:50 - major version:10 Driver: - name:jTDS Type 4 JDBC Driver for MS SQL Server and Sybase - version:1.2.4 java.sql.SQLException: Incorrect syntax near '-'. Please contact the system administrator.
Although if the page is refreshed the user was successfully added as an agent.
Tested this on PostgreSQL and that does not occurs.
Workaround:
- Refer the correct database collation type in our Connecting JIRA to SQL Server 2008 documentation.
- Change to other external database.
- is duplicated by
-
-
- Closed
-
- mentioned in
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
- was cloned as
-
DESK-4061 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-933] java.sql.SQLException: Incorrect syntax near '-'. When adding an existent user as agent.
Hi ezhang,
I just tested this behaviour on JIRA 6.3.11, JSD 2.1.1 with the right collation which is SQL_Latin1_General_CP437_CI_AI, but the same issue still happening. As mentioned in the ticket, after refreshing it, the Users would actually be included as an Agent and there seems to be any problem using that new Agent on ServiceDesk project.
Is this issue still related to this bug ticket? Attachment below for more details:
Cheers,
Julian.
Please see https://confluence.atlassian.com/display/JIRAKB/What+Database+Collation+X+Encoding+Should+be+Used+in+JIRA which explains why the encoding recommended by JIRA is what it is.
The workaround for this is to use the encoding recommended when connecting JIRA to a MSSQL.
ckimloong: We changed the database collation, but the error still occurs when we add an agent.
Hi,
This bug still occurs on:
SQL server version : 11.00.3412
Jira version 6.3.15
Service desk version : 2.3.2
/Mikael