Managed Settings missing in Profile Manager after upgrade to Server 3

Eric,

There is only one InstalledApplicationList per device, so it is correct that the number of updated rows is equal to the number of devices you have. This column holds a YAML-encoded array of the applications installed on the device, which is also why it's extremely difficult to hand-edit. In Server 3 there is a row per installed application per device in a different table, but that table is populated from the InstalledApplicationList of each device.

Can you paste in the full set of commands you are using to try to fix this? There must be something we're missing....

I can confirm that. The command didn't really remove the application either. It still shows up in the list with no details.

I did use that command and it didn't remove the application. I suspect it removed the listed applications from the devices. Which it can then get from the devices next time they connect.

I cut and pasted the commands directly from your posting.

Yes, this latest command does NOT remove the applications themselves. It just removes the list of applications that Profile Manager keeps for each device. And yes, that list is fetched from the device with any Update Information command.

Okay, I have made some progress. I realized that I had left Profile Manager on when I had tried to remove the installed applications, so I shut down the service, then tried to delete the installed applications list. This time, it worked, and I was able to re-run the migration per your other command without encountering the string too long error.

At a guess, I now have a properly populated devices table, albeit without information on the installed applications. I have not started profile manager yet as the conversion attempt yeilded a bunch of messages of the form:

3:: [5425] Created mdm_task from task 4154:

<MDMTask:0x7ffbc2dc0ac0> (table "mdm_tasks")

[<PGConnection:0x7ffbc2c131b0> owner: <NSOperationQueue:0x7ffbc2c12de0 'NSOperationQueue Main Queue'>, inTransaction: YES, last used 0.000 seconds ago]

Column | Value

[1;32m——————————————————————————+————————————————————————————————————— [0m

args | <NULL>

asset_id | <NULL>

completed_at | 2013-10-18 17:58:36.000000

id | 8

internal_task_id | <NULL>

library_item_task_id | 8

library_item_tombstone_id | <NULL>

mdm_target_id | 20

profile_id | <NULL>

push_arg_tombstone_id | <NULL>

skipped | f

succeeded | 1

task_type | UpdateInformation

updated_at | 2013-10-18 17:58:36.000000

uuid | d493fe10-1a4c-0131-701f-34159e01c1d0

yaml | <NULL>

2:: [5425] [2013/10/30 15:18:14.141] [1;7;31mEXCEPTION: [0;31m No inferred target profile found for NO-OP-PushSettings task <-[MDMTask(Migration) migratedObjectWithMigrationState:results:forRow:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/mig rator/AppModels/MDMTask-Migration.m:119): "'self.profile_id = p.id' is nil"> [0m [0m

2:: [5425] [2013/10/30 15:18:14.142] [1;7;31mEXCEPTION: [0;31m No inferred target profile found for NO-OP-PushSettings task <-[MDMTask(Migration) migratedObjectWithMigrationState:results:forRow:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/mig rator/AppModels/MDMTask-Migration.m:119): "'self.profile_id = p.id' is nil">

[4;31mBACKTRACE: [0m {

[0;31m? | 4365440206

? | 4365460028

? | 4365444827

? | 4365444097

? | 4367781382

? | 4367658903

? | 4365443433

? | 4365467445

? | 140735538722301

[0m} [0m

I am guessing that this is historical information on previous tasks that I had run, and is not critical. Is this correct?

Yes, this is some old task information that is not supported by Profile Manager in Server 3. It should not cause any issues.

Just to finish this one off. I do see all of my devices and was able to update the information on all devices without issue. I filed a bug report with Apple over the migration issue.

Is this the path to the original database? Where is the new database?

So my error log doesn't reference the installed applications, instead it has this:

1:: [552] [2013/11/04 08:32:37.280] Starting migration of 'LabSession'...

2:: [552] [2013/11/04 08:32:37.575] Updating PGModel 'LabSession' (table 'lab_sessions')

0:: [552] [2013/11/04 08:32:39.548] [1;7;31mEXCEPTION: [0;31m Postgres <-[PGConnection executeSQL:withParams:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:432): "Postgres error 22001 (ERROR: value too long for type character varying(63)

)"> [0m [0m

Is it safe to blow that away?

I removed the records in the lab_sessions table and the migration proceeded.

Hi,

I have almost the same issue but without an other error message:

—————————— [0m

2:: [13358] [2013/11/07 11:20:49.999] Updating PGModel 'TemporaryUniqueIntegerTable' (table '__runtime_temp_migration_tool-41210-4494')

2:: [13358] [2013/11/07 11:20:50.003] Deleted 0 rows from installed_applications for device 741

0:: [13358] [2013/11/07 11:20:50.012] Migrated 'Device' in 5455.11ms. (346 rows processed)

3:: [13358] Total transaction time: 5.497234 seconds.

1:: [13358] [2013/11/07 11:20:50.307] Starting migration of 'LabSession'...

2:: [13358] [2013/11/07 11:20:50.321] Updating PGModel 'LabSession' (table 'lab_sessions')

0:: [13358] [2013/11/07 11:20:55.479] [1;7;31mEXCEPTION: [0;31m Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 23505 (ERROR: duplicate key value violates unique constraint "owner_lab_sessions_device_id_index"

DETAIL: Key (device_id)=(459) already exists.

)"> [0m [0m

0:: [13358] [2013/11/07 11:20:55.481] [1;7;31mEXCEPTION: [0;31m Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 23505 (ERROR: duplicate key value violates unique constraint "owner_lab_sessions_device_id_index"

DETAIL: Key (device_id)=(459) already exists.

)">

USERINFO: {

SQLSTATE = 23505;

errorMessage = "ERROR: duplicate key value violates unique constraint \"owner_lab_sessions_device_id_index\"\nDETAIL: Key (device_id)=(459) already exists.\n";

}

[4;31mBACKTRACE: [0m

[0;31m? | 4504946144

? | 4504828986

? | 4502611981

? | 4502595291

? | 4502594561

? | 4504952326

? | 4504829847

? | 4502593897

? | 4502617909

? | 140735650727421

? | 2

[0m [0m

0:: [13358] [2013/11/07 11:20:55.481] [1;7;31mEXCEPTION: [0;31m Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block

)"> [0m [0m

0:: [13358] [2013/11/07 11:20:55.482] [1;7;31mEXCEPTION: [0;31m Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block

)">

USERINFO: {

SQLSTATE = 25P02;

errorMessage = "ERROR: current transaction is aborted, commands ignored until end of transaction block\n";

}

[4;31mBACKTRACE: [0m

[0;31m? | 4504946144

? | 4504828986

? | 4502601229

? | 4502595291

? | 4502594561

? | 4504952326

? | 4504829847

? | 4502593897

? | 4502617909

? | 140735650727421

? | 2

[0m [0m

0:: [13358] [2013/11/07 11:20:55.483] Caught unhandled exception -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block

)"

0:: [13358] [2013/11/07 11:20:55.483] *****************************************

0:: [13358] [2013/11/07 11:20:55.483] Migration from version 1 database failed!

-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block

)"

0:: [13358] [2013/11/07 11:20:55.483] *****************************************

4:: [13358] Total transaction time: 0.003722 seconds.

1:: [13358] [2013/11/07 11:20:55.487] Finalizing migration....

2:: [13358] [2013/11/07 11:21:19.158] main RESULT:

[1;32m————————+———————————————————————————————————————————————————————————————— ———————————————————————————————————————————————————————————————————————————————— —————————————— [0m

Do you have an idea?

Thanks a lot in advance

Thank you mscott_mdm!

Had the same trouble with our insall. Thanks to the 'larger hammer' command and re-migration command I was able to get the devices back into the display.

So far so good i'll update if anything goes funky.