search www.xcnetwork.com
Simplifying group collaboration...
 
Product Category Optional Search Text  

Article ID:
211
Categories:
Configuration
Error Messages
General Information
Products:
XC Connect (OS X Server)
Date Created:
20/06/2006 08:31 AM
Date Updated:
20/06/2006 08:31 AM
OS X 10.3.9 upgrade
 
Question:
Why am I experiencing problems with my XCN Server after upgrading to OS X Server 10.3.9?
 
Answer:
If you are upgrading OS X 10.3 to 10.3.9 (Server and/or client), it may be necessary to also apply the following update, which addresses Java not initializing properly after the 10.3.9 upgrade (http://www.apple.com/support/downloads/javaupdateformacosx1039.html).

Further information is available about the Java fix here: (including a simple test for Java functionality) http://docs.info.apple.com/article.html?artnum=301380

Other things to check on the computer in which the XCN Server software is installed.

- go to Applications/Server/Server Admin
- select your computer
- select ?web?
- make sure that is ?Running?
- select the ?settings? tab
- select the ?Sites? tab
- re-check to make sure that you have enabled your server to listen on port 80

- go to Applications/Server/Server Admin
- select your computer
- select "Firewall"
- select "New"
- select "Other" from the 'Port Name' drop down menu
- in the 'Port Number' field enter ?10001?
- in the 'Description' field enter ?XCN?
- select ?OK?

- go to System Preferences / Sharing and make sure that "Personal Web Sharing" is selected

Once you have followed the above steps, please execute:

Applications>Xchange Network Server > Troubleshoot Server to ensure that everything is configured properly.

If it is not, please stop and restart your server:

- Go to Applications|Utilities| and open 'Terminal'
- Type sudo sh /usr/local/xcnetwork/stopxcnetwork.sh
- Type sudo sh /usr/local/xcnetwork/startxcnetwork.sh

Once the server is back up, please try executing:

Applications -> Xchange Network Server -> Test Server

If you see a section like this:

ERROR: Tomcat AJP port not listening.
ERROR: Alternate Tomcat port not listening.

Then it means the problem is still present. If the above text is  not present in the output, then please try going to http://localhost/xcnetwork/ admin/ as things should be working properly.

If the problem is still present, please try changing the port Tomcat listens on for its shutdown commands. To do this, edit the file:

/Applications/Xchange Network Server/tomcat/conf/server.xml

You should see a line near the top with the port for Apache. Change this port to another port (e.g., 8001) and save the file.

Next,

- Go to Applications|Utilities| and open 'Terminal'
- Type sudo sh /usr/local/xcnetwork/stopxcnetwork.sh
- Type sudo sh /usr/local/xcnetwork/startxcnetwork.sh

Once this is done, please try going to:

http://localhost/xcnetwork/admin/

Please if these procedures do not resolve the problems you are experiencing, please send us the following files so we can investigate further:

1. The output from /Applications/Xchange Network Server/ Restart Server.command

2. The output from /Applications/Xchange Network Server/ Test Server.command

3. The output from /Applications/Xchange Network Server/ Troubleshoot  Server.command

4. The XCN Server logs from /Applications/Xchange Network Server/logs
 
Please rate this article (1 being worst, 5 being best):
1  2  3  4  5  
 
Click here to send specific feedback about this article.
home    products    buy now    try now    xc bridge    partners    support    contact    about us    knowledge base    site map    privacy
Copyright© 2002-2008 Xchange Network LLC. All rights reserved.