Supercontainer files cannot be viewed after server migration

[lotus_lotus]

Hello,

 

We had a supercontainer license version we were using with our Filemaker 11 solution hosting the SC at the FM server.

 

The files were stored in a specific format like http://IP_address/SuperContainer/Files/xyz/1/Docs/

 

But, after we migrated to a new server and also simultaneously migrated the supercontainer files in the same directory structure to the new server and applied the new paths but the old files could not be viewed. Instead we were shown a page with 404 error described below. We again upgraded ourselves to a ENTERPRISE version and installed in the same server and this is what we observed when we set the path to view for the existing files.

 

We had set the port to 8080 and the URL looks like http://IP_address:8080/SuperContainer/Files/xyz/1/Docs/ . Please suggest us why we cannot view the existing files with the new path. Here we use 'internal IP' in the address and and this is what we see as the page loads,

HTTP Status 404 -

type Status report

message

description The requested resource () is not available.

Apache Tomcat/5.0.28

[SCninja]

Hey there,

 

If I were to guess the reason for the 404 error (web server isn't available), is that somewhere within your FM solution you are still pointing to the old IP address/server machine where your SuperContainer instance used to run. Ensure that you can connect to the SuperContainer server by simply trying to connect using your browser.

 

If you're able to see the SuperContainer version page in Safari/Firfox/IE, then this means SuperContainer is in fact running. From here, ensure that your functions, web viewers, etc. in your FileMaker solution are pointing to the same IP address on which SC is deployed. 

 

Signed,