The XML page cannot be displayed | Community
Skip to main content
nicolletta
New Participant
November 2, 2016
Solved

The XML page cannot be displayed

  • November 2, 2016
  • 15 replies
  • 5629 views

Hello,

 

I have this error on Adobe Campaign when I'm trying to visualize workflow tab on a campaign  in “Targeting and workflows” tabs.

I’ve try figuring out but I cannot see where the error source is.

 

 

 have two platforms of Adobe Campaign, testing and production and in production when I try to go to this url: https://xxxxxxxxxxx-prod1.campaign.adobe.com/xtk/xsl/dhtml/targetPreview.xsl I get « Forbidden. You don't have permission to access /xtk/xsl/dhtml/targetPreview.xsl on this server”.

In testing environement I don’t have this error when I try to acces the same page.

 

 

Thank you for your suggestions.

Best regards,

 

Nicoleta

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amit_Kumar

Hi Nicoleta,

 it looks like this file is not allowed from the apache server. please hack your firewall settings are apache config for prod for .xsl type files?

Regards,

Amit

15 replies

nicolletta
New Participant
March 6, 2017

Hello Amit,

 

Support confirmed that the problem was in apache configuration file: 

"The configuration file for the apache need to be change to give proper file permission to a specific file path (the one that contains the xsl used within that workflow). Unfortunately, since this patch/configuration change is done at the server level, we do not have access to it. I only know the configuration change was needed to have access to the following folder: /usr/local/neolane/nl6/datakit/xtk/fra/xsl"

Thank you.

Best regards,

Nicoleta

nicolletta
New Participant
March 2, 2017

Hello Florent,

After opening three support tickets, support applied yesterday a patch on my platform. For now I don’t have more details about the applied patch. It is working fine now. Adobe Campaign Support team said on 14/02/2017: “The permanent fix has been added to the latest build that is currently being evaluated by Adobe Quality Assurance team right now. Once verified and the build is release, you would need to upgrade your environment to get the permanent fix.”


Best regards,
Nicoleta

nicolletta
New Participant
January 17, 2017

Hello Florent,

I'm still working with support on this. As soon as I'll have a solution I'll post it. 

Regards,

Nicoleta

florentlb
New Participant
January 13, 2017

Hi Nicoleta,

Did you manage to resolve your issue with Amit's answer?

Florent

Amit_Kumar
New Participant
January 3, 2017

You got it right. Do let me know if that worked. sorry for the typo earlier.

nicolletta
New Participant
December 23, 2016

Amit_Kumar wrote...

Hi Nicoleta,

 it looks like this file is not allowed from the apache server. please hack your firewall settings are apache config for prod for .xsl type files?

Regards,

Amit

 

Hello Amit,

 

Thank you for your answer.

You are saying that I should look in apache config file to see if .xsl is well configurated?

I also should ask Adobe support to check firewall settings for .xls, as all the platform are hosted at Adobe?    

Best regards,

Nicoleta

Amit_Kumar
Amit_KumarAccepted solution
New Participant
December 23, 2016

Hi Nicoleta,

 it looks like this file is not allowed from the apache server. please hack your firewall settings are apache config for prod for .xsl type files?

Regards,

Amit

florentlb
New Participant
December 5, 2016

Hi Nicoleta,

I don't know any easy way of doing this. I will double check and let you know if I have more informaiton to share about this.

Florent.

nicolletta
New Participant
December 1, 2016

Florent,

Thank you for your suggestions also. I’ll ask my client if they want to upgrade.

Is there an easy way to compare two Adobe Campaign instances? Is there a way to easily extract all the code installed on the platform? I wasn’t there where the project stared and I can see that I can extract code object by object.

 

Thank you.

Best regards,

Nicoleta

florentlb
New Participant
December 1, 2016

Hello Nicoleta,

I suggest you follow support recommendations, while I'll try to find some more insight about it. We had a new build released earlier this week (8765).

Are there any configuration differences between your testing and production instances? Like specific customization or different JS scripts in the workflow? These are common causes for this display issue.

 

Florent.