Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

How to Migrate App Center Version 4.1.16 to Version 4.2

Created: 23 Jan 2014 • Updated: 27 Jan 2014 | 5 comments
PHRAIWAN's picture
I try to migrate app center version 4.1.16 to 4.2 
Our systems
App Center 4.1.16 on CentOS 5.8
External Databases MySQL 5.1 on CentOS 5.8 
Create a new server for App Center 4.2 on CentOS 6.4
My Step 
- Setup the new CentOS/RHEL 6.4 server for App Center 4.2
- create new MDM Core database on external database
When i start the page Configure Symantec App Center by port 8000 
App Center Information
- i use information same as App Center 4.1.16 
- i use email same as version 4.1.16
Database Information
    Config Encruption Key File 
- same as version 4.1.16
    Use External Database
- same as version 4.1.16
    MDM Core Database
- create new 
SSL Information
- use cert same as App Center 4.1.16
Email Information
- use information same as App Center 4.1.16
when i click Submit i got an error  " An error occurred while processing master config file."
error migrate.JPG
i already attach log config for app center 
Please help.
Operating Systems:

Comments 5 CommentsJump to latest comment

James007's picture

Does you have see best practices for upgrading App Center 4.2

Migrating to Symantec App Center 4.2
Article:HOWTO94513  |  Created: 2013-12-09  |  Updated: 2013-12-18  |  Article URL
PHRAIWAN's picture

Thank you James007

I already see the document and video.

Maybe i made something wrong i do not understand how to config MDM Core database ??

James007's picture

See this articles

Configuring and troubleshooting the MDM core
Article:HOWTO94514  |  Created: 2013-12-09  |  Updated: 2013-12-13  |  Article URL
PHRAIWAN's picture

I have to create and config mdm core database before migrate 4.2 ??

Andrew_C's picture

Hello Phraiwan,

Please review the following log files- this error typically occurs if there are insufficient privileges set on the DB (App Center or MDM Core DB):




The configurator.log file should provide a helpful error. Ensure the user account on the MDM Core DB has all privileges assigned.