Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

Error in AEM content Synchronization - Adobe Campaign Classic

Avatar

Level 2

I'm facing an error while accessing the ontent from AEM in ACC. Attached is the screenshot. 

While the connectivity is established, I'm unable to fetch the content into delivery. Basically the content leisted from AEM is having absolute path (http://xxxx.com/content/campaign etc) while i think the relative path is only expected. As a result the original path is also getting appended and is throwing the error. 

Any help to fix this please.

Note: I've all the required changes in the serverConf.xml for urlpermission of the domain, still didnt help.

AEM - Campaign Integration Error.JPG

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi,

 

Looks like you have 2 url's concatenated together there.

 

Thanks,

-Jon

View solution in original post

6 Replies

Avatar

Correct answer by
Community Advisor

Hi,

 

Looks like you have 2 url's concatenated together there.

 

Thanks,

-Jon

Avatar

Level 2
Hi , Yes. When the email assets list in the dialog box, only the relative path is expected and the https://xxx.com should be added automatically. Since the asset listing shows up with http path it is showing 2 urls. Not sure if any settings should be changed in OSGi or somewhere to get the assets listed with the relative path.

Avatar

Level 4

Got this issue before. This has to be fixed from AEM side. Just some configuration change.

Avatar

Level 2
Can you let me know what is the configuration change? Is it to do with externalizer in OSGi, I've the correct configuration in there. Let me know if you recollect what should be changed in AEM side.

Avatar

Level 4
Unfortunately I have no idea what was changed by AEM team at that time. But I can assure you that this is not a problem with ACC.

Avatar

Level 3
I see similar issue in our systems. can you provide how this was fixed ?