cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X

Translate the entire conversation x

Question about Arbortext Editor backward compatibility

ML_12573696
4-Participant

Question about Arbortext Editor backward compatibility

I am using Arbortext Editor version 8.2.3.0 however, the contracting company used Arbortext Editor 6.0. I used the contracting company's XML to create one in Arbortext 8.3.2.0. Is there a compatibility issue with using aXML created with Arbortext Editor version 6.0 and creating a new XML version in Arbortext Editor 8.2.3.0?

Is there an issue with the publishing service? I obtain the fatal error when publishing (see attached titled  image.png).

 

 

5 REPLIES 5

Dear Customer,

 

From the snapshot, it looks like some access issues because it is accessdenied exception. Could you please review that .xsl file if the user has access over that location/folder?

 

As you are asking if there is an issue with the publishing service, could you please provide more details about this? Are you using Arbortext Publishing Engine or Arbortext Editor with Styler for publishing a document?

 

Regards,

Manpreet Singh

ML_12573696
4-Participant
(To:manpsingh)

I am working on a network folder in my working folder. I have full read/write access to this folder so I assume Arbortext Editor can access this network folder also. The XML file is located in this network folder.

 

We are using Arbortext Editor with a Styler (xslfo-main-v7.0.xsl) installed on my C drive for publishing that came with version 8.3.2.0.

Hi,

Arbortext 8.3.2.0 is not yet released.

You are correct. 

ML_12573696_0-1738766266994.png

 

MG_10509405
5-Regular Member
(To:ML_12573696)

The error you see is most likely because you try to publish with styles that are outside defined custom folder. This is a new security feature.

 

Add the path to APTCUSTOM environment variable and try again.

 

https://www.ptc.com/en/support/article/CS223823

Announcements

Top Tags