Skip to main content
I
IQ1
Inspiring
July 25, 2019
Answered

Application does not work after changing name of database

  • July 25, 2019
  • 1 reply
  • 995 views

Hello,

  I had a change of Server name to the database, I changed this in the admin portal of cold fusion after that my application home page appears but when I login I cannot get in, it says the following error ,

Can someone please advise what could be wrong ?

HTTP Error 403.18 - Forbidden

The specified request cannot be processed in the application pool that is configured for this resource on the Web server.

Thanks

IQ

    This topic has been closed for replies.
    Correct answer Charlie Arehart

    I realize you're simply writing what you observe, but there's simply no connection between changing a CF Admin DSN to point to a new server, and a failure of a page reporting application pool problems. There must be some other explanation for your application error. Are you 100% positive that before you changed the DSN, the exact same URL from the exact same browser had been working? I'd think your application would fail with this error REGARDLESS of the change of the CF Admin DSN name used by that app.

    Or here's a possibility: could it be that your application is now failing (because in changing the DSN, you have code still looking for the old DSN), and an error handler (either in CF or in IIS) may be redirecting requests to some new domain or folder, which may be different from the one you started the request on? Look closely to see if that URL is indeed changing.

    Let us know what you find (or if you already found and solved this).

    (And I would swear I offered this answer in days past, but I see it's not here.)

    1 reply

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity ExpertCorrect answer
    Community Expert
    July 29, 2019

    I realize you're simply writing what you observe, but there's simply no connection between changing a CF Admin DSN to point to a new server, and a failure of a page reporting application pool problems. There must be some other explanation for your application error. Are you 100% positive that before you changed the DSN, the exact same URL from the exact same browser had been working? I'd think your application would fail with this error REGARDLESS of the change of the CF Admin DSN name used by that app.

    Or here's a possibility: could it be that your application is now failing (because in changing the DSN, you have code still looking for the old DSN), and an error handler (either in CF or in IIS) may be redirecting requests to some new domain or folder, which may be different from the one you started the request on? Look closely to see if that URL is indeed changing.

    Let us know what you find (or if you already found and solved this).

    (And I would swear I offered this answer in days past, but I see it's not here.)

    /Charlie (troubleshooter, carehart. org)
    I
    IQ1Author
    Inspiring
    July 29, 2019

    The was a file aplications.cfm which also needed the dsn change.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices