Article - CS206968
Cognos ReportHelper command failed to do Update model with error java.io.InvalidClassException: org.apache.axis.AxisFault in Windchill PDMLink 10.2
Modified: 18-Feb-2016
Applies To
- Windchill PDMLink 10.1 F000 to 11.1 M020-CPS02
Description
- Cognos ReportHelper command failed to do Update model with error java.io.InvalidClassException: org.apache.axis.AxisFault.
- Cognos is installed successfully.
- While starting Cognos Services, cogserver.log reports following error:
DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>Process BmtMDProviderMain failed to start properly.</messageString></message></messages> External Report Server process BmtMDProviderMain cannot be startedProcess BmtMDProviderMain failed to start properly.java.io.IOException: Process BmtMDProviderMain failed to start properly. at com.cognos.pogo.reportservice.ReportServerProcess.getProcessOutput(ReportServerProcess.java:192) at com.cognos.pogo.reportservice.ReportServerProcess.start(ReportServerProcess.java:129) at com.cognos.metadataService.bibusHandler.mdprovider.MDProviderProcess.start(MDProviderProcess.java:58) at com.cognos.pogo.reportservice.ProcessFacade.createServerProcess(ProcessFacade.java:275) at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:158) at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:117) at com.cognos.metadataService.bibusHandler.mdprovider.MDProviderProcessFacade.<init>(MDProviderProcessFacade.java:61) at com.cognos.metadataService.bibusHandler.mdprovider.MDProviderComponentFactory.newProcessFacade(MDProviderComponentFactory.java:52) at com.cognos.pogo.reportservice.ProcessManager.createProcessFacade(ProcessManager.java:516) at com.cognos.pogo.reportservice.ProcessManager.startProcess(ProcessManager.java:492) at com.cognos.pogo.reportservice.ProcessManager.startProcessesDueToCapacity(ProcessManager.java:387) at com.cognos.pogo.reportservice.ProcessManager.safeRun(ProcessManager.java:345) at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61)
- Loadreports.log reports following errors:
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.ptc.windchill.cognos.CognosProxy.main(CognosProxy.java:63)
Caused by: wt.util.WTException: java.net.ConnectException: Connection refused
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.ptc.windchill.cognos.CognosProxy.main(CognosProxy.java:63)
Caused by: wt.util.WTException: java.net.ConnectException: Connection refused
- AccessControl.log reports following error:
com.ptc.windchill.cognos.CognosAccessControlManager - Error while connecting to Cognos Content Manager.
java.net.ConnectException: Connection refused
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.ptc.windchill.cognos.CognosProxy.main(CognosProxy.java:63)
java.net.ConnectException: Connection refused
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.ptc.windchill.cognos.CognosProxy.main(CognosProxy.java:63)
- MethodServer logs reports following error:
wt.util.WTException: The server did something wrong
Nested exception is: AxisFault
faultCode: Server
faultSubcode:
faultString: The server did something wrong
faultActor:
faultNode:
faultDetail:
{http://developer.cognos.com/schemas/bibus/3/}exception:<severity>error</severity><errorCode>NO_PROCESS</errorCode><ns1:message><messageString>DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit.</messageString><nestingLevel>1</nestingLevel></ns1:message><ns1:message><messageString>Handler trace back:
[the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler
[the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler
[service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler
[load_balancer] com.cognos.pogo.handlers.logic.ChainHandler
[lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler
[mdaChainHandler] com.cognos.pogo.handlers.logic.ChainHandler
[asyncMetadataServiceHandler] com.cognos.pogo.async.impl.AsyncHandler
[metadataServiceHandler] com.cognos.metadataService.bibusHandler.MDSRVHandler</messageString><nestingLevel>1</nestingLevel></ns1:message>
Nested exception is: AxisFault
faultCode: Server
faultSubcode:
faultString: The server did something wrong
faultActor:
faultNode:
faultDetail:
{http://developer.cognos.com/schemas/bibus/3/}exception:<severity>error</severity><errorCode>NO_PROCESS</errorCode><ns1:message><messageString>DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit.</messageString><nestingLevel>1</nestingLevel></ns1:message><ns1:message><messageString>Handler trace back:
[the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler
[the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler
[service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler
[load_balancer] com.cognos.pogo.handlers.logic.ChainHandler
[lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler
[mdaChainHandler] com.cognos.pogo.handlers.logic.ChainHandler
[asyncMetadataServiceHandler] com.cognos.pogo.async.impl.AsyncHandler
[metadataServiceHandler] com.cognos.metadataService.bibusHandler.MDSRVHandler</messageString><nestingLevel>1</nestingLevel></ns1:message>
This is a printer-friendly version of Article 206968 and may be out of date. For the latest version click CS206968