Jump to content

Branch Explorer Error


vozdemir

Recommended Posts

I just installed community edition and simply created new workspace. For testing purpose i added a file and checked-in. Created new branch, changed file and checked-in. When i click branch explorer it gives an error.

 

I am using MSSQL backend and user&password authentication.

 

Thank you,

 

Error:

 

There has been an unexpected error "Column 'FIDBRANCH' does not belong to table Changeset.". For more information check the server log.

 

 

Link to comment
Share on other sites

There is a lot of errors in the server log file. 

 

(null) NT AUTHORITY\SYSTEM at (null) INFO  Channel - conn       14 Tcp transport error. Connection closed

(null) NT AUTHORITY\SYSTEM at (null) INFO  Channel - Tcp transport error. ReceiveMessageStatus Connection closed

(null) NT AUTHORITY\SYSTEM at (null) INFO  Channel - conn       17 An existing connection was forcibly closed by the remote host

NT AUTHORITY\SYSTEM at  WARN  Upgrade - Client requested file not in the list of upgradeable files: server\config\extensions\jiraextension.conf

Link to comment
Share on other sites

Hi,

I´ve been investigating the problem and it´s definitely related to TURKISH_CI_AS collation on your SQL Server.

http://connect.microsoft.com/SQLServer/feedback/details/382858/field-names-becomes-case-sentive-when-we-use-turkish-ci-as

 

Plastic supports UTF-8 collation. Is it possible for you to change your SQL Server collation to UTF-8? Or maybe install a new SQL Server to store Plastic databases?

 

Best regards,

Carlos

Link to comment
Share on other sites

Hi,

 

I checked settings. My SQL Server's default collation is Turkish_CI_AS but when I create new repo from Plastic SCM, newly created repo's database's collation is Turkish_CS_AS. This is strange. Also there is not an UTF-8 collation in MS SQL Server. I tried many collation after db creation but nothing changed. I think collation must define when creating the database.

 

Can you change your db creation scripts to modify database's collation? I think this is solve our problem because I don't need any turkish collation in Plastic SCM's db's.

 

For example:

 

CREATE DATABASE rep_1 COLLATE Latin1_General_100_CI_AI

 

Thank you,

Link to comment
Share on other sites

  • 4 weeks later...
  • 3 months later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...