S3 File Transfer - No File Found - ACC to AAM

Avatar

Avatar
Validate 10
Level 4
davidl14970702
Level 4

Likes

30 likes

Total Posts

93 posts

Correct reply

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

Avatar
Validate 10
Level 4
davidl14970702
Level 4

Likes

30 likes

Total Posts

93 posts

Correct reply

13 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
davidl14970702
Level 4

08-07-2019

We are integrating ACC with AAM through core services. Everything (meaning server configuration) "looks" good but when I run the imporSharedAudiences workflow errors out on "No file to transfer found".

Im trying to figure out what to trouble shoot next. It seems like the workflow is fine. What would the conditions need to be for a file to be present? Is there another way I can check for the file?

Replies

Avatar

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

179 likes

Total Posts

273 posts

Correct reply

160 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

179 likes

Total Posts

273 posts

Correct reply

160 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile
craigthonis
Employee

08-07-2019

Hi David,

I'd recommend in this case submitting a ticket to Campaign Support as we'll need to review your environment and items such as the external account setup and the AAM side along with confirming the credentials being used in the integration.

Regards,

Craig

Avatar

Avatar
Validate 10
Level 4
davidl14970702
Level 4

Likes

30 likes

Total Posts

93 posts

Correct reply

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

Avatar
Validate 10
Level 4
davidl14970702
Level 4

Likes

30 likes

Total Posts

93 posts

Correct reply

13 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
davidl14970702
Level 4

08-07-2019

Updated -

I've played with the URL path for our bucket, and now I am getting this error.

CRL-290151 HTTP response received from S3 403.

Any thoughts on how to get past this one? Or is this a support issue?