This document was generated from CDN thread
Created by: CHARLES SMITH on 10-07-2009 05:52:19 AM
Anyone know what could be causing these errors?
583: 10.0.9.71: Jul 10 2009 01:17:25.647 -0400: %CVP_7_0_MessagingLayer-1-PLUGIN_INITIALIZATION_FAILURE: SYS_RPT2 Plugin initialization failed due to Plugin : SYS_RPT2 encountered a socket disconnect due to: Transport is down [id:9]
584: 10.0.9.71: Jul 10 2009 01:17:25.647 -0400: %CVP_7_0_MessagingLayer-3-MESSAGING_LAYER: OutProcessClientConnection(SYS_RPT2)::terminateConnection encountered on plugin: SYS_RPT2 due to: Transport is down [id:1]
585: 10.0.9.71: Jul 10 2009 01:17:25.647 -0400: %CVP_7_0_MessagingLayer-1-PLUGIN_INITIALIZATION_FAILURE: SYS_RPT2 Plugin initialization failed due to host ip not defined [id:9]
Subject: RE: Strange errors in the CVP reporting server logs
Replied by: Sanjay Chandan on 22-02-2010 10:49:40 PM
Hi charles,
Even we are running into same issues, were you able to get any fix.
Thanks
Sanjay
Subject: RE: Strange errors in the CVP reporting server logs
Replied by: Rucha Khisti on 23-02-2010 03:49:38 PM
Hi,
The reason you see these error messages in the reporting log files is because your reporting subsystem can't connect to the call server.
Please check and make sure all the callservers associated with the reporting server are up and in service
Thanks
Rucha
Subject: RE: Strange errors in the CVP reporting server logs
Replied by: Doan Khanh Tan Thanh on 21-09-2011 10:10:00 AM
Hi all,
I have a problem on CVP Call Server. It suddenly lost the connection to the CVP PG due to an error say "Transport is down"
I attach along with the error log. Please help me on that, what is the error mean?
Thank you,
Thanh
Hi,
The reason you see these error messages in the reporting log files is because your reporting subsystem can't connect to the call server.
Please check and make sure all the callservers associated with the reporting server are up and in service
Thanks
Rucha
Subject: RE: Strange errors in the CVP reporting server logs
Replied by: Sheraz Saeed lodhi on 23-02-2012 03:28:37 AM
Hi I faced the same so i first removed all call servers from Reporting server through oamp and then associated them again and it worked.
