Starting Pipelined process (AC Classic)

Avatar

Avatar
Validate 1
Level 1
donaldims
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
donaldims
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
donaldims
Level 1

02-05-2019

We are in the Process of setting pipeline in a Production instance (tested and working in DEV). Following all the documentation steps just like Dev, it seems the same does not want to work for Prod. The process starts but then immediately throws the error below:

1744827_pastedImage_0.png

We have followed all steps as described and tried the troubleshooting steps several times but nothing seems to want to work.

Anyone experienced this before or have any other ideas to resolve this?

Any help would be greatly appreciated.

https://forums.adobe.com/external-link.jspa?url=https%3A%2F%2Fhelpx.adobe.com%2Fcampaign%2Fkb%2Ftrig...

Thanks,

Donald

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
MVP
Jean-Serge_Biro
MVP

Likes

353 likes

Total Posts

464 posts

Correct reply

153 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile

Avatar
Validate 1
MVP
Jean-Serge_Biro
MVP

Likes

353 likes

Total Posts

464 posts

Correct reply

153 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile
Jean-Serge_Biro
MVP

03-05-2019

Hi Donald,

Did you use a Open SSH different private/public key for your dev and your prod environments?
And in Adobe Experience Cloud (AEC) for Adobe Analytics triggers authentication, the key is correctly entered as you did for dev environment?

Perhaps there is a mislead in the key entered in AEC ?

Sorry I am not skilled yet with Pipeline AEC key issues, but I wonder because of your message error "invalid key".

Regards
J-Serge

Answers (1)

Answers (1)

Avatar

Avatar
Validate 10
Level 5
DarrenBiz
Level 5

Likes

68 likes

Total Posts

205 posts

Correct reply

37 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 5
DarrenBiz
Level 5

Likes

68 likes

Total Posts

205 posts

Correct reply

37 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
DarrenBiz
Level 5

06-05-2019

Agree with Jean-Serge. Check that you have pasted the right public key in that matches your production private key in the Legacy OAuth connection you created for your production instance. This should be different to the key pair you used for DEV.