Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Toolkit version 2
JTNeville
Anyone using it? Some of the pieces bomb on upload but still appear in their respective areas (connectors, view sets, etc...)
Here's the error. Anyone successfully loaded Toolkit 2 or know why this error occurs? Thanks.
WorkSite MP has encountered an error. Additional information is unavailable.
Context: General
Details: A generic application error occurred. See previous logs for additional error and warning messages.
Action: Click Back and then repeat your previous steps. If this problem persists, contact your support staff.
com.imanage.workteam.exceptions.WtAppException:Error during file handling operations (com.imanage.workteam.exceptions.WtAppException:WorkSite MP has encountered an error. Additional information is unavailable.
Context: General
Details: Error during file handling operations
Action: Click Back and then repeat your previous steps. If this problem persists, contact your support staff.
com.imanage.workteam.exceptions.WtAppException:Error during file handling operations (com.imanage.workteam.exceptions.WtAppException:WorkSite MP has encountered an error. Additional information is unavailable.
Context: General
Details: Base document cannot be null
Action: Click Back and then repeat your previous steps. If this problem persists, contact your support staff.
com.imanage.workteam.exceptions.WtAppException:Base document cannot be null))
Underlying StackTrace:
WorkSite MP has encountered an error. Additional information is unavailable.
Context: General
Details: Error during file handling operations
Action: Click Back and then repeat your previous steps. If this problem persists, contact your support staff.
com.imanage.workteam.exceptions.WtAppException:Error during file handling operations (com.imanage.workteam.exceptions.WtAppException:WorkSite MP has encountered an error. Additional information is unavailable.
Context: General
Details: Base document cannot be null
Action: Click Back and then repeat your previous steps. If this problem persists, contact your support staff.
com.imanage.workteam.exceptions.WtAppException:Base document cannot be null)
Underlying StackTrace:
com.imanage.workteam.exceptions.WtAppException: WorkSite MP has encountered an error. Additional information is unavailable.
Context: General
Details: Base document cannot be null
Action: Click Back and then repeat your previous steps. If this problem persists, contact your support staff.
com.imanage.workteam.exceptions.WtAppException:Base document cannot be null
at com.imanage.workteam.configtool.utilities.ConfigDeployUtil.applyDeltasForVersion(ConfigDeployUtil.java:890)
at com.imanage.workteam.configtool.utilities.ConfigDeployUtil.handleDeploy(ConfigDeployUtil.java:838)
at com.imanage.workteam.configtool.utilities.ConfigDeployUtil.processDeltaFile(ConfigDeployUtil.java:627)
at com.imanage.workteam.configtool.utilities.ConfigDeployUtil.handleDeltaFiles(ConfigDeployUtil.java:582)
at com.imanage.workteam.configtool.utilities.ConfigDeployUtil.handleDeltaFiles(ConfigDeployUtil.java:574)
at com.imanage.workteam.configtool.bundles.viewSet.ViewSetUploadCmd.execute(ViewSetUploadCmd.java:90)
at com.imanage.workteam.configtool.servlets.ConfigDispatchServlet.process(ConfigDispatchServlet.java:59)
at com.imanage.workteam.configtool.servlets.ConfigBaseServlet.doProcess(ConfigBaseServlet.java:112)
at com.imanage.workteam.configtool.servlets.ConfigBaseServlet.processPost(ConfigBaseServlet.java:98)
at com.imanage.workteam.AbstractBaseServlet.doPostBody(AbstractBaseServlet.java:283)
at com.imanage.workteam.AbstractBaseServlet.doPost(AbstractBaseServlet.java:262)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.imanage.workteam.AbstractBaseServlet.serviceBody(AbstractBaseServlet.java:203)
at com.imanage.workteam.AbstractBaseServlet.service(AbstractBaseServlet.java:179)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2422)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
Find more posts tagged with
Comments
Migrateduser
not that the dump indicates it, but have you extended the object model? Most of STK is based on a single extended object model superset for all its capabilities.
And yes, it has been successfully applied.
JTNeville
Yes I extended the OM and checked the log to insure it executed successfully, but thanks for the pointer. I'm still looking at it. Think I'll install a second 4.1SP1 to another test server and see if I get the same errors.
Nicholas
To run Toolkit V2, you need to install the WSMP 4.1 SP1 HFB4, make you sure you have all installed successfully, I have deployed it successfully. Let me know if you are having issues.
Thanks Nicholas
Migrateduser
yes Nicholas,
He need WSMP 4.1 SP1 HFB4 for worksite mp server and same for web components. also try Project management templates, Schema extension and Projects.jar with extended connectors.
~Rishi Gupta
