nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SitePublisher Component Unable to Load

System

I've created and tested a SitePublisher Component. It was working last week until today I got this pop-up error message when I view the components. I didn't change anything from the last version. It just keep on saying that the ".seed" file is unable to load or cannot be found.

I've attached two screenshots using my IE8 and Firefox and both got the same ".seed" error message.

Appreciate any help on this.

Thanks.

syntaxcode

Find more posts tagged with

Comments

cute_guy

Looks like Sitepublisher app is down or not loaded

Check your server log for any error related to iw-preview.war not deployed

Migrateduser

There are no logs pertaining to iw-preview.war or it was down.

Rick Poulin

There are no logs pertaining to iw-preview.war or it was down.

You must have had something in ApplicationContainer/server/default/log/server.log from the most recent startup of JBoss. You would not have anything with a recent timestamp -- this error would have appeared only when the app was initializing. There is no other explanation.

What's happening is that JBoss is failing to render files of type ".seed" because the LiveSite rendering filter is down, so it hands it off to the native servlet container, which returns an error page. Now, your webserver doesn't know what MIME type to assign to a "seed", so that's why your browser assumes it must be a binary format that you download to your desktop.

Migrateduser

Thanks for the explanation. So is this user account specific issue?, because some of the users with the same access rights didn't experience this error message. They can view the updated component I did. We even tried simultaneously and I get the same error. Any other workarounds?

sheikh1

Thanks for the explanation. So is this user account specific issue?, because some of the users with the same access rights didn't experience this error message. They can view the updated component I did. We even tried simultaneously and I get the same error. Any other workarounds?

To rule out that it is permissions issue, did you compare permissions between a working user and not working one?
Also try to recycle your jboss server, as Rick pointed your livesite servlet must not be running.

Rick Poulin

Thanks for the explanation. So is this user account specific issue?, because some of the users with the same access rights didn't experience this error message. They can view the updated component I did. We even tried simultaneously and I get the same error. Any other workarounds?

Well that threw me for a loop.. This shouldn't be user-specific, unless your controllers/externals are doing something user-specific and failing in a colossal way when something's not right. Which version of TS, and are you using LSCS?

Your best option is to trace this from a workstation that doesn't work. In Firefox, use the iw-preview URL that says "file not found" and add ":8080" at the right place to go direct to JBoss. That'll tell you if the problem is Apache/IWProxy or if it's the web app.

Also try restarting JBoss, and monitor the initialization logging for errors and exceptions. We're expecting a "iw-preview.war failed to startup" or something like that.

If all else fails, turn on debug logging for com.interwoven.livesite and hit the page again.

Migrateduser

TS = 7.2

Here's the error message from 8080...

The system has encountered an internal error.
com.interwoven.livesite.runtime.rendering.RenderingException: Unhandled Exception at com.interwoven.livesite.runtime.rendering.RenderingManager.handleException(RenderingManager.java:987) at com.interwoven.livesite.runtime.rendering.RenderingManager.render(RenderingManager.java:266) at com.interwoven.livesite.iw.servlet.preview.PreviewFilter.processRequest(PreviewFilter.java:172) at com.interwoven.livesite.iw.servlet.preview.PreviewFilter.doFilter(PreviewFilter.java:113) 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 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:619) Caused by: java.lang.RuntimeException: failed to load site data at com.interwoven.livesite.iw.servlet.preview.PreviewDataMapping.setSite(PreviewDataMapping.java:119) at com.interwoven.livesite.iw.servlet.preview.rendering.PreviewRenderingManager.doSetupSite(PreviewRenderingManager.java:226) at com.interwoven.livesite.runtime.rendering.RenderingManager.doSetUp(RenderingManager.java:439) at com.interwoven.livesite.runtime.rendering.RenderingManager.render(RenderingManager.java:231) ... 22 more Caused by: java.lang.RuntimeException: Failed to read SiteMap file using CSClient at com.interwoven.livesite.iw.servlet.preview.PreviewSiteMapCache.get(PreviewSiteMapCache.java:150) at com.interwoven.livesite.iw.servlet.preview.PreviewDataMapping.setLiveSiteDal(PreviewDataMapping.java:295) at com.interwoven.livesite.iw.servlet.preview.PreviewDataMapping.setSite(PreviewDataMapping.java:91) ... 25 more Caused by: java.lang.ClassCastException: com.interwoven.cssdk.filesys.impl.CSHoleImpl cannot be cast to com.interwoven.cssdk.filesys.CSSimpleFile at com.interwoven.livesite.iw.servlet.preview.PreviewSiteMapCache.get(PreviewSiteMapCache.java:121) ... 27 more

Rick Poulin

Ok, well first there must be something weird with your iwwebd config, because you should have seen that same exception whether you're hitting :80 or :8080. Double-check your rewrite.conf to make sure there's a rule to handle /iw-preview in there -- it may have been missed if you did a recent in-place upgrade, or if something else mucked with that file.

Caused by: java.lang.ClassCastException: com.interwoven.cssdk.filesys.impl.CSHoleImpl cannot be cast to com.interwoven.cssdk.filesys.CSSimpleFile at com.interwoven.livesite.iw.servlet.preview.Preview SiteMapCache.get(PreviewSiteMapCache.java:121)

This says that you have a component on the page that is attempting to read the sitemap for the current site, and that sitemap file is either marked for deletion or deleted entirely. File is located at /sites/YourSiteName/default.sitemap within the workarea. If you're in the /iwadmin/main/livesite/component branch previewing a component, make sure the context "preview site" you're using is a valid one. You'll find this just below the component layout properties box, when you're editing the component.

Migrateduser

Thanks a lot. I think I'm beginning to trace to where it started... I'll come back when I get some investigation... Much appreciated.