Error during upgrade
I upgraded our test environment from 9.0.6 to 9.0.9 today but i get this error
2019-04-01 10:54:33 Attempting to Create CiresonAnalytics Jobs 2019-04-01 10:54:33 Failed to Create CiresonAnalytics Jobs CiresonAnalytics on sqlth01 : Error converting data type nvarchar to int.
What can i do?
Best Answer
-
Billy_Wilson Member Ninja IT Monkey ✭✭✭✭The problem here is with the Run Data Sync every X Minutes on the Cireson Analytics section setting during the installer. In the version where I get the error, the sync interval is set to 17.
In my other lab, the interval is set to the default 1,440.
Apparently, if you use a value that the installer converts into a decimal by converting minutes into hours ({value}/60 - in the case above 17 was converted into 0.283333333333333) then the value is inserted into the SQL script which, when run, will error because the field is an int field and sees the 0.decimal value as a string. Whereas the value 1,440 above is converted to 24 in the settings and goes through fine.
I will log this as a bug, but in the mean time, I simply changed my value back to the default 1,440 (I edited C:\Users\{install account}\AppData\Roaming\Cireson Setup\setup.config directly) and the Portal upgraded correctly.
6
Answers
In my other lab, the interval is set to the default 1,440.
Apparently, if you use a value that the installer converts into a decimal by converting minutes into hours ({value}/60 - in the case above 17 was converted into 0.283333333333333) then the value is inserted into the SQL script which, when run, will error because the field is an int field and sees the 0.decimal value as a string. Whereas the value 1,440 above is converted to 24 in the settings and goes through fine.
I will log this as a bug, but in the mean time, I simply changed my value back to the default 1,440 (I edited C:\Users\{install account}\AppData\Roaming\Cireson Setup\setup.config directly) and the Portal upgraded correctly.
I had an identical issue, but with a non-English locale. After switching the current region to US and (probably more important) datetime/number format to English, the installer succeeded without any issues.