We have recalled the 8202 build due to upgrade failure on MYSQL 4.1.18 as described below and will most probably come up with 8203 today fixing the issue.
Those who have already moved to 8202 can have a smooth migration to 8203(once its released) and rest can directly upgrade to 8203.
Apologies for the inconvenience caused.
SDP Support - FAQ
ServiceDesk Plus - Help Desk Software of your Choice
Those who have already moved to 8202 can have a smooth migration to 8203(once its released) and rest can directly upgrade to 8203.
Apologies for the inconvenience caused.
MaljeevWe have a problem in performing the upgrade to 8202 for MySQL database users who are in mysql version 4.1.18. and this issue is not with higher version of MySQL and other database flavors. During upgrade to 8202 we are trying to create "MobileApplications" table which got failed with the below errorMay 3, 2013 9:55:23 AM [com.adventnet.persistence.DataModelUpdateUtil] [INFO] : CREATING the table :: MobileApplications in module AssetMay 3, 2013 9:55:23 AM [SYSERR] [INFO] : java.sql.SQLException: Syntax error or access violation, message from server: "Specified key was too long; max key length is 1024 bytes"
SDP Support - FAQ
ServiceDesk Plus - Help Desk Software of your Choice