コミュニティアチーブメントバーを展開する。

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.

Mark Solution

この会話は、活動がないためロックされています。新しい投稿を作成してください。

解決済み

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 受け入れられたソリューション

Avatar

正解者
Level 10

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.

元の投稿で解決策を見る

6 返信

Avatar

Level 10

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

Level 10

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

Avatar

Level 10

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

正解者
Level 10

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.