AWRunSQLPackageCMD returned actual error code 1603

[JanKulir]

Anyone seen on-premise DB upgrade error: ' AWRunSQLPackageCMD returned actual error code 1603'  ?
Can't figure out what causes it. Upgrading from on-premise AW 9.0.5.0

[DonSorcinelli]

Which DB upgrade installer are you running? It would need to be 9.1, as the DB upgrade installers are not incremental.
Also - you can check to see if a log file was created in  or AirWatch or [new version] or Database. The log file in the directory where the installer runs is not very detailed (error 1603 is a sort of ' catch all'  error code).

[JanKulir]

Hi Don,
tried both 9.1.4 and 9.1.5 with the same error, the server was rolled back so cant get more logs, but will keep eye on what you suggested next time

[PeterAir]

On which version is your SQL server? Newer versions of AW do not support SQL 2008 anymore. I think that I've seen a similar message when trying to upgrade on SQL 2008.

[CharlesTchia]

I'm currently noticing the same issue with an upgrade as Jan. As suggested by Don, in the log file, failure is coming back with:

' ERROR: MEMConfigMigration - Migration has failed.
...SmartGroup_BlueprintDefaultSmartGroup
...Scheduler_HealthAttestationSample
...GettingStartedOverride_MigrateSecureApps
...DeviceProfileSettingValue_AddEnableDevicePasscodePolicy
...SystemCodeOverride_OverrideCIMDEndPoint
...SystemCodeOverride_OverrideHeartBeatSample
An error occurred while the batch was being executed.
Updating database (Failed)
*** Could not deploy package.
Warning SQL72015: The column [eventLog].[DeviceInformationEventType].[DeviceEventTypeID] is being dropped, data loss could occur.
Warning SQL72015: The column [eventLog].[DeviceInteractionEventType].[DeviceEventTypeID] is being dropped, data loss could occur.
Warning SQL72015: The column [mobileManagement].[AAProxyAppMapping].[InternalApplicationID] is being dropped, data loss could occur.
Warning SQL72015: The column [mobileManagement].[AAProxyAppMapping].[RecommendedExternalApplicationID] is being dropped, data loss could occur.
Warning SQL72015: The column [scheduler].[ServiceHealthHistory].[RoutineInstanceName] is being dropped, data loss could occur.
Warning SQL72015: The column [scheduler].[ServiceHealthHistory].[RoutineName] is being dropped, data loss could occur.
Warning SQL72015: The column [scheduler].[ServiceHealthHistory].[RoutineStateCode] is being dropped, data loss could occur.
Warning SQL72015: The column [scheduler].[ServiceHealthHistory].[ServiceInstanceName] is being dropped, data loss could occur.
Warning SQL72015: The column [scheduler].[ServiceHealthHistory].[ServiceStateCode] is being dropped, data loss could occur.
Error SQL72014: .Net SqlClient Data Provider: Msg 50000, Level 16, State 13, Procedure MEMConfigMigration, Line 296 String or binary data would be truncated.
Error SQL72045: Script execution error.  The executed script:
PRINT 'Begin Post-Deployment Script...';'

We are on SQL 2012.

[JanKulir]

We are on SQL 2012 as well.
Originally, it was on SQL 2008 but was migrated about 1/2 year ago. Migration went without problem.
This is the first upgrade after migration.

[CharlesTchia]

Just an update on my previous post, some configurations in powershell that we were playing with in the past tripped up the install. I had some names in the limit sync section and because of the long characters (256 character limit in the script), the upgrade script wasn't liking it. I've killed these off now and upgrade is progressing

[AmaurySOBACO]

Hi, same error here,

@Charles,

what exactly did you do to solve the problem ?

Thanks in advance,

[JanKulir]

Hi, have you migrated DB to new server recently?
The reason I had the problem was, that after migrating server from SQL 2008 to 2012, I had made sure to re-create the DB owner so as not to have problem with right to database, but I forgot that the SQL DB jobs in scheduler also have owner - which was orginal owner from 2008 DB.. So for me it was failing because I was missing rights to manipulate database jobs - when I manually changed owner of all the AirWatch jobs to the new AirWatch DB owner, update succeeded.

[AmaurySOBACO]

no recent migration ...

I do not understand because, install FAIL at the end of the upgrade, during Post-Deployment Script, at dbo.UpgradeHistory ...

[CharlesTchia]

Hi Amaury

in our case, we had some settings under Email (Groups and Settings > All Settings > Email > Configuration) from when we were testing out with Powershell. I had an entry there with a long CN name which tripped the upgrade script