View and Print User requesting publishing job to be created

[avillanueva]

I came across an interesting case that I did not see documented anywhere. I had a job fail to publish at the very end of its run:

Jun 26, 2025, 3:21:04 PM:Done deleting temporary workspace publish13463010064453792551tmp.
Jun 26, 2025, 3:21:04 PM:Start Store Component Viewable Files
Jun 26, 2025, 3:21:18 PM:Uploading Files
Jun 26, 2025, 3:21:24 PM:Error Finalizing Representation
Jun 26, 2025, 3:21:24 PM:Unexpected Exception has occured
Jun 26, 2025, 3:21:24 PM:End Store Component Viewable Files, Error Occured

I've seen this before when we had vaulting issues but other jobs were done just fine. Checking BGMS logs, I noticed this related access exception in the publishing logs:

2025-07-02 07:51:10,018 ERROR [PublisherQueue3.PollingThread] wt.access.evaluation.report Administrator - "<username>" does not have Delete permission for "EPMDoc Config Spec - wt.epm.EPMDocConfigSpec:1834898779" in Administrative Domain "Site /User".
2025-07-02 07:51:10,159 ERROR [PublisherQueue3.PollingThread] wt.wvs.viewmarkup.StandardViewMarkUpService Administrator - ViewMarkUpService: Error postStoreDerviedImage (wt.access.accessResource/19) wt.access.NotAuthorizedException: ATTENTION:  Secured Action. You do not have the necessary authorization for this operation. Contact your administrator if you believe you have received this message in error.
	at wt.access.StandardAccessControlManager.hasAccess(StandardAccessControlManager.java:11084)

Checking that user I noticed they were a View and Print user. According to CS157235 V&P users cannot create anything. What is strange is that a EPMDocConfigSpec is workspace related right? Publishing is done by a service account user. Odd that Windchill allows the user to request republishing but does not allow it to succeed since their license prevents it. IMHO, V&P should allow interaction with WVS information, markups and annotations. 

[Fadel]

Looks like https://www.ptc.com/en/support/article/CS292124 

[avillanueva]

Thanks for this @Fadel. What is strange is that the user did not see this or must not have since I did see a failed publish job with their username on it. Actually, I resubmitted their job myself is when I saw it. If it was as simple as a popup message denying the action, that would not have created the publish job. it should have not gotten that far. I suspect there is a gap. 

[Fadel · Accepted solution]

@avillanueva  is this on system upgraded/updated recently to 13.0.1 , There are some SPRs fixed with regards to Print & View and publishing  

[TomU]

I've seen this before.  I've added an explicit DENY ACL to prevent this from happening.

Similar concept presented here:  https://www.ptc.com/en/support/article/CS412442