java.io.IOException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Users running FishEye/Crucible 4.0.0 or 4.0.1 with MS SQL Server will encounter the following error, when trying to perform a backup: {code} 2016-03-21 10:25:19,952 WARN - Backup failed. java.io.IOException: Error reading database: Cannot encode value for unsupported column type: "bit" (-7) of column .cru_fisheye_user at com.atlassian.crucible.migration.item.SQLBackup$SaverImpl.backup(SQLBackup.java:82) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.createBackup(BackupManagerImpl.java:264) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.access$000(BackupManagerImpl.java:55) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:153) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:151) [fisheye.jar:?] {code} This does not affect users who upgraded directly to 4.0.2, and didn't ever run 4.0.0 or 4.0.1. Note, scheduled backups would not finish too, admins may not notice. h2. Workaround Users can do the following to manually fix the functionality: # Shutdown FishEye/Crucible # Execute the following SQL script on the MS SQL Server database: {code} DROP INDEX cru_idx_perm_fisheye_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_fisheye_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_fisheye_user ON cru_global_permission (cru_fisheye_user); DROP INDEX cru_idx_perm_crucible_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_crucible_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_crucible_user ON cru_global_permission (cru_crucible_user); {code} # Restart FishEye/Crucible
    via by Lukasz Pater,
  • Users running FishEye/Crucible 4.0.0 or 4.0.1 with MS SQL Server will encounter the following error, when trying to perform a backup: {code} 2016-03-21 10:25:19,952 WARN - Backup failed. java.io.IOException: Error reading database: Cannot encode value for unsupported column type: "bit" (-7) of column .cru_fisheye_user at com.atlassian.crucible.migration.item.SQLBackup$SaverImpl.backup(SQLBackup.java:82) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.createBackup(BackupManagerImpl.java:264) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.access$000(BackupManagerImpl.java:55) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:153) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:151) [fisheye.jar:?] {code} This does not affect users who upgraded directly to 4.0.2, and didn't ever run 4.0.0 or 4.0.1. Note, scheduled backups would not finish too, admins may not notice. h2. Workaround Users can do the following to manually fix the functionality: # Shutdown FishEye/Crucible # Execute the following SQL script on the MS SQL Server database: {code} DROP INDEX cru_idx_perm_fisheye_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_fisheye_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_fisheye_user ON cru_global_permission (cru_fisheye_user); DROP INDEX cru_idx_perm_crucible_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_crucible_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_crucible_user ON cru_global_permission (cru_crucible_user); {code} # Restart FishEye/Crucible
    via by Lukasz Pater,
  • Users running FishEye/Crucible 4.0.0 or 4.0.1 with MS SQL Server will encounter the following error, when trying to perform a backup: {code} 2016-03-21 10:25:19,952 WARN - Backup failed. java.io.IOException: Error reading database: Cannot encode value for unsupported column type: "bit" (-7) of column .cru_fisheye_user at com.atlassian.crucible.migration.item.SQLBackup$SaverImpl.backup(SQLBackup.java:82) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.createBackup(BackupManagerImpl.java:264) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.access$000(BackupManagerImpl.java:55) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:153) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:151) [fisheye.jar:?] {code} This does not affect users who upgraded directly to 4.0.2, and didn't ever run 4.0.0 or 4.0.1. Note, scheduled backups would not finish too, admins may not notice. h2. Workaround Users can do the following to manually fix the functionality: # Shutdown FishEye/Crucible # Execute the following SQL script on the MS SQL Server database: {code} DROP INDEX cru_idx_perm_fisheye_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_fisheye_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_fisheye_user ON cru_global_permission (cru_fisheye_user); DROP INDEX cru_idx_perm_crucible_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_crucible_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_crucible_user ON cru_global_permission (cru_crucible_user); {code} # Restart FishEye/Crucible
    via by Lukasz Pater,
  • Users running FishEye/Crucible 4.0.0 or 4.0.1 with MS SQL Server will encounter the following error, when trying to perform a backup: {code} 2016-03-21 10:25:19,952 WARN - Backup failed. java.io.IOException: Error reading database: Cannot encode value for unsupported column type: "bit" (-7) of column .cru_fisheye_user at com.atlassian.crucible.migration.item.SQLBackup$SaverImpl.backup(SQLBackup.java:82) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.createBackup(BackupManagerImpl.java:264) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.access$000(BackupManagerImpl.java:55) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:153) [fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:151) [fisheye.jar:?] {code} This does not affect users who upgraded directly to 4.0.2, and didn't ever run 4.0.0 or 4.0.1. Note, scheduled backups would not finish too, admins may not notice. h2. Workaround Users can do the following to manually fix the functionality: # Shutdown FishEye/Crucible # Execute the following SQL script on the MS SQL Server database: {code} DROP INDEX cru_idx_perm_fisheye_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_fisheye_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_fisheye_user ON cru_global_permission (cru_fisheye_user); DROP INDEX cru_idx_perm_crucible_user ON cru_global_permission; ALTER TABLE cru_global_permission ALTER COLUMN cru_crucible_user TINYINT NOT NULL; CREATE INDEX cru_idx_perm_crucible_user ON cru_global_permission (cru_crucible_user); {code} # Restart FishEye/Crucible
    via by Lukasz Pater,
    • java.io.IOException: Error reading database: Cannot encode value for unsupported column type: "bit" (-7) of column .cru_fisheye_user at com.atlassian.crucible.migration.item.SQLBackup$SaverImpl.backup(SQLBackup.java:82)[fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.createBackup(BackupManagerImpl.java:264)[fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl.access$000(BackupManagerImpl.java:55)[fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:153)[fisheye.jar:?] at com.atlassian.crucible.migration.BackupManagerImpl$2$1.perform(BackupManagerImpl.java:151)[fisheye.jar:?]
    No Bugmate found.