Fix Legacy ASP 500 Error
Budget: $30 – $250 USD
I run a classic ASP, SQL-driven site on a shared-hosting plan. Everything works until a visitor clicks a particular link whose destination is stored in the database—at that moment the browser returns the generic “500 – Internal server error.” I need someone who knows the quirks of legacy ASP on shared IIS environments to trace the fault, explain the root cause, and guide me through (or implement) the fix without upsetting the rest of the application.
You’ll probably want to:
• turn on friendly-error detail, check IIS logs and SQL traces
• review the query and any redirect or response headers tied to that stored link
• patch the offending script or database record, then verify the page now loads cleanly
Deliverables
1. Short diagnostic summary: what broke and why
2. Step-by-step remedy applied (code or configuration)
3. Confirmation that the page loads without a 500 error on the live server
If you’ve rescued similar ASP sites before, I’d love to hear your plan and estimated turnaround.
You’ll probably want to:
• turn on friendly-error detail, check IIS logs and SQL traces
• review the query and any redirect or response headers tied to that stored link
• patch the offending script or database record, then verify the page now loads cleanly
Deliverables
1. Short diagnostic summary: what broke and why
2. Step-by-step remedy applied (code or configuration)
3. Confirmation that the page loads without a 500 error on the live server
If you’ve rescued similar ASP sites before, I’d love to hear your plan and estimated turnaround.