An error occurred during PT compile

Hello all,

TeamSite 7.4.1 on Windows 2008 Server

We are migrating from TeamSite 6.7.2 to 7.4.1

Our TPLs and DCTs are ported over to new TeamSite server. While trying to preview/generate a DCR, we are getting PTcompile error. It is NOT a template error because we have tried emtpying the tpl and leaving simple 'Hello World' in there, which didn't work either.

Content_center log says this:

2014-09-11 09:48:41,330 [http-0.0.0.0-8080-43] ERROR com.interwoven.ui.formspub.utils.PerlPTCompiler () - perl PTCompiler utild error: executeSynCommand error
com.interwoven.serverutils100.utild.UtildClientException: executeSynCommand error
at com.interwoven.serverutils100.utild.UtildClient.executeSyncCommand(UtildClient.java:144)
at com.interwoven.ui.formspub.utils.PerlPTCompiler.compile(PerlPTCompiler.java:244)
at com.interwoven.ui.formspub.DoGenerateCommand.execute(DoGenerateCommand.java:147)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:1041)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:864)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:738)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommandLoop(CommandHandler.java:330)
at com.interwoven.ui.base.impl.command.CommandServlet.doGet(CommandServlet.java:163)
at com.interwoven.ui.base.impl.command.CommandServlet.doPost(CommandServlet.java:263)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.interwoven.livesite.spring.hibernate.web.filter.OpenSessionsInViewFilter.doFilterInternal(OpenSessionsInViewFilter.java:108)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.interwoven.ui.base.impl.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:203)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.interwoven.ui.base.util.SetRequestEncodingFilter.doFilter(SetRequestEncodingFilter.java:106)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.interwoven.hopi.HopiException: Unknown Hopi error
at com.interwoven.utild.utild_.ExecuteCommand(utild_.java:685)
at com.interwoven.utild.Utild.executeSyncCommand(Utild.java:154)
at com.interwoven.utild.Utild.executeSyncCommand(Utild.java:123)
at com.interwoven.serverutils100.utild.UtildClient.executeSyncCommand(UtildClient.java:142)
... 40 more
2014-09-11 09:48:41,331 [http-0.0.0.0-8080-43] ERROR com.interwoven.ui.base.impl.command.CommandHandler () - forward "error" not handled by descriptor iw.formspub.do_generate

Any pointers as to what this may be and how/where to fix it?

Thanks,

Uttara

Find more posts tagged with

Comments

nipper

What type of users do you have set up ? Are the OS users or non-OS users ? For PT compiler the users will need the ability to log on locally & execute a process on the server in their name.

Try with an admin account or a local account and see if they work.

UttaraK

Our access is set-up through AD groups. The user that is trying to run this is a domain user. This is how we are running on our 6.7.2 Dev, Prod and 7.4.1 Dev server.

I just tried running it with admin user and result is still the same. The user that I tried with is the administrator on the server and is a TeamSite Master. We do not have local users on this machine and our security team won't allow that, so not an option for us.

We are still getting the same error.

Uttara

Rick Poulin

You might also have relevant output in the iwutild_cmdout.log. If you do, that might indicate a problem with running the actual command. If you don't, then there might be a communication problem between the App Container and the iwutild.

UttaraK

If I run it as a regular domain user (not admin), then I do not get any error in iwutild_cmdout.log OR iwutild.log.

If I run it as administrator, then iwutild_cmdout.log says 'Could not open presentation template <template path_name>' where as the template path is correct and I can open same through windows explorer.

You mentioned about communication problem between App container and iwutild. How do we proceed in that direction for that issue? Where or what could we check/fix?

Thanks for your help,

Uttara

Rick Poulin

iwutild is a bit of a black box, so beyond making sure that the service is running and that the right ports are listening, there's not a whole lot you can do to troubleshoot the issue yourself. That's usually an HP support ticket. That said, the lack of errors is not necessarily a bad sign.

When you say you're running it, which command are you running.. iwpt_compile, or the workflow? Your result sounds backwards if it's somehow locking out admins -- check the perms on the file and anything that your template is importing/reading.

Also, just saw your response to nipper.. domain accounts are fine, but they still need the 'log on locally' and 'local execute' permissions granted in your security policies.

nipper

Your test does confirm the users do not have proper access. Change their access to log on locally.

That is not the only issue, as shown by the Admin test. However that you can work on

Open a DOS prompt and go to Y:\default\main\path\to\WORKAREA\content\templatedata\whatever\this\data

and then try running iwpt_compile by hand. Post the results.

UttaraK

Alright, the issue resolved !

It was not local log on rights, but something else.

The only two changes we made are:

1. In iwutild.cfg,

Changed impersonate to 'false' from true

AND

in iw.cfg,

[authentication]
disable_ext_task_impersonation=true
impersonate_without_password=false

Thats it! Did a iwreset -a and started seeing preview and page generates.

We believe only one of them, (iwutild.cfg change) made it work, and am working on confirming that now.

I know that now our CLTs will be run as 'system' and not actual user, but thats okay for us at the moment.

Glad to have it resolved, thanks for your replies and directions!

Uttara