Member Avatar for balor

this is my prob an i someone cab help me about it:

when i click a link into my page, it will then open a new window which is connected to a database. when it loads.. after 2-3 seconds the "Page cannot be displayed error" will then occur.. what is the problem with this? i need your help pls.. :sad:

  • 3 Contributors
  • 2 Replies
  • 101 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by zippee

Dani AI

Generated

Brief, practical diagnostic steps and likely causes for the symptom described (new window opens, appears to start loading, then 2–3 seconds later shows "Page cannot be displayed"). The behaviour usually means the browser did not receive a complete HTTP response (connection reset or server error mid-response) or the application hung on a blocking operation (commonly a database call) and the client times out. As pointed out, more diagnostic data is required; the checklist below shows what to gather and what to try first. As suggested, surface useful error output — prefer structured server-side logging over client alerts.

Collect diagnostic data: record the HTTP exchange (browser DevTools Network tab or curl -v/wget --server-response) and note the HTTP status code, response headers, and timing. Check webserver error logs (IIS/Apache), application logs, and database logs for entries at the exact timestamp. Reproduce the request from the server itself (curl localhost/URL) to rule out network/proxy issues.

Common root causes and focused checks:

  • Unhandled server exception: server returns 500 or the process crashes — add try/catch and log exceptions with timestamps.
  • Blocking/slow DB query or connection timeout: log connect/start/finish times around database calls; run the query directly on the DB to check plan and locks.
  • Middlebox (proxy, firewall, load‑balancer) closing the connection: compare server-side and client-side timings.
  • Session/cookie or POST-to-new-window issues when opening a new window.

Safe immediate actions: add short, timestamped server-side logs around DB connect and query execution; enable detailed errors only on a development/staging host (do not leave on in production). Example debug toggles (temporarily):

# ASP.NET (web.config)
<system.web>
  <customErrors mode="Off"/>
</system.web>
# PHP (temporary)
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(E_ALL);

Prioritize getting the HTTP status and server logs first; those typically point to the exact failure (exception, timeout, connection reset) and make a targeted fix possible.

Recommended Answers

All 2 Replies

Member Avatar for tgreer

This is impossible to diagnose with the information given. Is the URL to the dynamic page correct? Are the database connection strings correct? Is the web-server properly configured to serve pages in whatever server-side language you're using?

In any case, this is probably a server-side issue, rather than HTML or JavaScript.

Member Avatar for zippee

I would say there is error in your server side script. Add script to display warning when error found will help you solve your problem.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.