Hi,
We are in process of WF7611 upgrade from AIX to Linux platform.After Installing the client and Reportcaster,We are not able to access the ReportCaster as it is displaying ' 500:Internal; server error '.Through Admin console ,it is displaying message that 'distribution server is not running' . When we trying to start Distribution server using 'schbkr' below error is coming :

 
./schbkr &
[2]     25494
[ukx01034]:wfedws02$ java.net.MalformedURLException
        at java.net.URL.<init>(URL.java:601)
        at java.net.URL.<init>(URL.java:464)
        at java.net.URL.<init>(URL.java:413)
        at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:650)
        at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
        at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
        at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
        at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
        at ibi.broker.distribute.util.DSTSendModeHandler.process(DSTSendModeHandler.java:106)
        at ibi.broker.distribute.util.DSTSendModeHandler.getSendMode(DSTSendModeHandler.java:87)
        at ibi.broker.scheduler.util.SCHConfigReader.readSendMode(SCHConfigReader.java:552)
        at ibi.broker.scheduler.SCHStart.initResources(SCHStart.java:412)
        at ibi.broker.scheduler.SCHStart.start(SCHStart.java:397)
        at ibi.broker.SCHScheduler.main(SCHScheduler.java:101)
Console is listening on port: 50200
Unable to initialize console at port #:50200
java.net.BindException: Address already in use


        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at java.net.ServerSocket.<init>(ServerSocket.java:97)
        at ibi.broker.scheduler.service.SCHConsole.<init>(SCHConsole.java:161)
        at ibi.broker.scheduler.service.SCHServiceFactory.createConsole(SCHServiceFactory.java:79)
        at ibi.broker.scheduler.SCHCasterContext.init(SCHCasterContext.java:81)
        at ibi.broker.scheduler.SCHCasterManager.start(SCHCasterManager.java:57)
        at ibi.broker.scheduler.SCHStart.start(SCHStart.java:398)
        at ibi.broker.SCHScheduler.main(SCHScheduler.java:101)
Cannot create Console service
java.net.BindException: Address already in use


        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at java.net.ServerSocket.<init>(ServerSocket.java:97)
        at ibi.broker.scheduler.service.SCHConsole.<init>(SCHConsole.java:161)
        at ibi.broker.scheduler.service.SCHServiceFactory.createConsole(SCHServiceFactory.java:79)
        at ibi.broker.scheduler.SCHCasterContext.init(SCHCasterContext.java:81)
        at ibi.broker.scheduler.SCHCasterManager.start(SCHCasterManager.java:57)
        at ibi.broker.scheduler.SCHStart.start(SCHStart.java:398)
        at ibi.broker.SCHScheduler.main(SCHScheduler.java:101)

[2] +  Done(1)                 ./schbkr &

 

We are using same Oracle ReportCaster repository in 2 different environments but with different USERIDs. Is this a cause for the problem? Please suggest.

Thanks in advance.

This message has been edited. Last edited by: Kerry,

I think the problem here is that port 50200 is already in use,as stated clearly in the message.
Report caster needs its own privately ownde port. IF it can't claim the port, this message will be generated.
Check which process has the port allocated and kill that process. Then try again.