|
Home > Archive > IIS Server Security > January 2004 > IIS Upgrade using ODBC and ASP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
IIS Upgrade using ODBC and ASP
|
|
|
| I have ASP pages using ODBC calls to connect to a
separate server running SQL Server. When upgrading from
Win2000 to Win2003, the pages broke and I am getting
errors of unable to find page.
The DSN for the ODBC works correctly, but the ASP pages
are not able to display correctly.
Is there a new security piece I am missing in IIS?
| |
| Ken Schaefer 2004-01-24, 1:58 am |
| "Page can not be displayed" is a generic error mesaage. Please scroll down
to find more information. If the *web* server can not be contacted you will
see "can not find server or DNS error". If the webserver can be contacted,
but is having a problem, you will see a HTTP status code, eg "500 Internel
Server Error". If so, you need to disable "Show Friendly HTTP Errors" in
your copy of IE (Tools -> Options -> Advanced) and reload the page to see
the real error message the server is sendig to your browser. Post that
message to the group.
Cheers
Ken
"Rick" <anonymous@discussions.microsoft.com> wrote in message
news:0ad301c3c97c$556dc210$a501280a@phx.gbl...
: I have ASP pages using ODBC calls to connect to a
: separate server running SQL Server. When upgrading from
: Win2000 to Win2003, the pages broke and I am getting
: errors of unable to find page.
:
: The DSN for the ODBC works correctly, but the ASP pages
: are not able to display correctly.
:
: Is there a new security piece I am missing in IIS?
|
|
|
|
|