Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.
If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.
When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:
You may also want to review the installation or upgrading documentation.
Howdy Y'all:
Two of my 3 sites in this multi-site mojoPortal installation are working fine after upgrading to mojoPortal-2-2-5-8 5/21/2008. The third site gets:
The connection has timed out The server at datapoint.mine.nu is taking too long to respond. * The site could be temporarily unavailable or too busy. Try again in a few moments. * If you are unable to load any pages, check your computer's network connection. * If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
The connection has timed out The server at datapoint.mine.nu is taking too long to respond. * The site could be temporarily unavailable or too busy. Try again in a few moments.
* If you are unable to load any pages, check your computer's network connection.
* If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
I've checked that the functioning sites and the failing site match at "Administration Menu > Site Settings".
There are no errors at "Administration Menu > System Log".
There are no errors in the Application or System Event Logs.
Any suggestions are very much appreciated, Dale E. Moore
Are you sure the request is even making it to the server? This could be a DNS issue, it may not be pointing to the site.
I would check the IIS web logs and see what actual requests have come in for this site and what the response codes were.
Joe
Thanks for the pointers Joe; there must have been an SQL activity problem because the problem has healed itself.
I appreciate the thought about the IIS logs!