Expand my Community achievements bar.

SOLVED

Upgrade to Launch Failed ?

Avatar

Level 2

Hi Guys,

I am trying to upgrade my DTM property to Launch and I am using option of Upgrade to Launch. But it's failing each time i am trying to upgrade.

It's giving error:
Upgrade to Launch failed. Could not create the 'Production' environment correctly. Please contact Client Care if the issue persists.

1645801_pastedImage_4.png

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

I got same issue yesterday it turns out that if you have done a migration of the same web property previously using the option to keep the DTM production endpoint, then you can not migrate it once more using the DTM production endpoint which is logical.

I just removed the migrated web property in Launch and done the migration again and it worked.

Might be worth for the Adobe Launch team to put a better error message.

View solution in original post

6 Replies

Avatar

Community Advisor

Have you ever published the library ? If you never published it then the production env will not exist

Avatar

Level 2

Thanks for your reply Alexis!
I have already published few tags and adobe analytics tool in DTM, then only i tried to Upgrade to Launch but it failed few times.

Please find below screenshot for your reference and suggest to do the needful.

1646552_pastedImage_0.png

Avatar

Community Advisor

I heards from my colleague this morning that Adobe Launch is having some issues so that might be linked.

Avatar

Community Advisor

There is indeed an issue with activation : Adobe Status #2018121403

We noticed that it affects both Launch and DTM build functionality

Avatar

Employee Advisor

Were you able to get this one resolved?

Avatar

Correct answer by
Community Advisor

I got same issue yesterday it turns out that if you have done a migration of the same web property previously using the option to keep the DTM production endpoint, then you can not migrate it once more using the DTM production endpoint which is logical.

I just removed the migrated web property in Launch and done the migration again and it worked.

Might be worth for the Adobe Launch team to put a better error message.