If another program running on the server has a port conflict with Tomcat it will affect both the Interactive Dashboard and the SData integration with Sage CRM.
Errors appearing for SData Provider requests
A port conflict for Tomcat would not affect IIS so the main interface for Sage CRM 7.0 would appear be working fine, but if an SData provider request is made (e.g. an ERP application requesting Sage CRM information using a SData provider request) then an error which looks something like the following would be returned:
<H1>Service Temporarily Unavailable!</H1>
<P>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</P>
<P><BR/> <BR/> <BR/> <BR/> Jakarta/ISAPI/isapi_redirector/1.2.28<BR/>
<P id="footer">Copyright © 1999-2009 Apache Software Foundation<BR/>All Rights Reserved</P>
There would also be problems synching data between Sage CRM and an ERP system (i.e. their sync status would be set to “Failed” in CRM) that is using the Sage SData contract. See http://sdata.sage.com for more details about ERP integration.
Errors appearing in the Interactive Dashboard
A port conflict would mean the dashboard would not be working at all, for example, if you tried to create a dashboard you’d get an error like “The Dashboard could not be saved. Please contact your System Administrator.”.
You can investigate this by looking in the logs
If you see the error “java.net.BindException: Address already in use: JVM_Bind” in the logs, this is because some application is already using Tomcat’s preferred port number.
You can solve this issue using the steps below:
1. Navigate to the folder containing your installs Tomcat’s server.xml file.
e.g. C:\Program Files\Sage\CRM\CRM70\tomcat\conf
2. Open the file and look for its port number. It’ll look something like “<Server port="10005" shutdown="SHUTDOWN">”.
3. You now have two options: you can force Tomcat to use an unused port (step 4), or you can kill the process (PID) which is using Tomcat’s port (steps 5, 6).
4. Open the command prompt and type “netstat –a –n”. This will tell you which ports are currently in use. Simply pick a port number which isn’t on screen, and update server.xml accordingly. You can now start Tomcat.
5. Open the command prompt and type “netstat –a –n –o”. This will tell you which ports are currently in use, and which PIDs are using them. Locate and make a note of the PID which is using Tomcat’s port.
6. Open “Windows Task Manager”, click “View”, click “Select Columns”, check “PID (Process Identifier)” and press “OK”. Locate the PID you made a note of in step 2 and -- assuming it isn’t a vital windows process -- kill it. You can now start Tomcat.