Skip to main content
P
Pat_State
New Participant
May 8, 2008
Answered

after upgrade from mx7 to 8 Virtual directory cannot connect to Jrun server

  • May 8, 2008
  • 1 reply
  • 401 views

Upgraded a windows server 2003 from CFMX 7, with both updates, to CF8.01.
The site works correctly except for a virtual directory that points to a directory that is outside the iis website path. I can connect to the virtual directory with html and am working around this problem that way.

The error message is: Server Error The server encountered an internal error and was unable to complete your request.
Could not connect to JRun Server.

I don't see any issues when I looked in the cf logs, but it may be that I don't recognize the problem in the logs.

The virtual directory and cfmx7 had no problems, but after the upgrade, just the error message when trying to get to a .cfm.

I installed CF8 into the same web root as cfmx7, and the migration carried over all the settings. I did go into services and stop all the cfmx7 services and set them to manual.


I've attached the server.log.

Thanks for any assistance on this.
    This topic has been closed for replies.
    Correct answer Pat_State
    It looks like this was a combination of the upgrade, increasing use of ASP files and not having seperate application pools in IIS.

    We've just starting edding aspx apps, previously we only had one asp app so we only used the default app;icaton pool in iis. With the errors in the virtual directory started, we deleted and remade the VD with it's only application pool. That appears to have resolved the issues. The only concern I have is one of the VD did have it's own applicaton pool and still had the very slow response after the upgrade. But I'll see how this solution works for the future.

    The decesion was made to only have cf8 installed since that worked well on our testing server, so we did intend to overwrite the CFIDE folder.

    Thanks for checking this out and for your time on this.

    At this point I consider this closed. If something else comes up I'll start a new thread on it.

    1 reply

    V
    Vinu_kumar_t
    Participating Frequently
    May 14, 2008
    Can you try to reconfigure the IIS connector using wsconfig? Also if you use the same webroot as CFMX7 you will not be able to use CFMX7 as the CFIDE will be overwritten.

    - Vinu (kvinu@adobe.com)
    P
    Pat_StateAuthorCorrect answer
    New Participant
    May 14, 2008
    It looks like this was a combination of the upgrade, increasing use of ASP files and not having seperate application pools in IIS.

    We've just starting edding aspx apps, previously we only had one asp app so we only used the default app;icaton pool in iis. With the errors in the virtual directory started, we deleted and remade the VD with it's only application pool. That appears to have resolved the issues. The only concern I have is one of the VD did have it's own applicaton pool and still had the very slow response after the upgrade. But I'll see how this solution works for the future.

    The decesion was made to only have cf8 installed since that worked well on our testing server, so we did intend to overwrite the CFIDE folder.

    Thanks for checking this out and for your time on this.

    At this point I consider this closed. If something else comes up I'll start a new thread on it.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices