Skip to main content
Participant
October 3, 2006
Question

view asp pages in dreamweaverMX 2004

  • October 3, 2006
  • 5 replies
  • 456 views
Hi,

I've created an asp page in Dreamweaver, however, I can't view it. I've set up the site in the Site Manager for the "testing server" as c:\localhost\dirName and the "local server" is my machine as well c:\inetpub\wwwroot\dirName\. I had to set up the "testing server" b/c DW prompted me to create a testing server in order to view the asp page. I running windows XP Professional and using DWMX 2004. When I try to view the page, I get a "The page cannot be displayed" error like it can't find the server.

Can someone help me out with this? I would really like to use my own machine to test my asp pages.

Thanks!!!
Rod

P.S. I even tried to use a different port (as I had to do using VisualStudio.Net) i.e., c:\localhost:8001\dirName, but this did not work either. I'm not concerned with that though, so no need to reply about that.
This topic has been closed for replies.

5 replies

rod06Author
Participant
October 5, 2006
Hi Nancy and Julian,

THANK YOU for your replies, I really appreciate your time. Nancy, to answer your 1st question, I did use the 8001 port (as listed in my "P.S." of my first post), b/c I use it on IIS, but it did not work for the asp pages in dreamweaver. I set http://localhost:8001/gb as my testing server in DW and clicked "f12" -- I still can not view the page. To answer your 2nd question, a few years ago, when I first set up IIS to run my .Net pages, I had to use port 8001, I guess port 80 was being used by my ISP (DSL at the time), I really don't remember -- all I know is I was having trouble setting up Studio.Net so I visited a few blogs and found an answer -- use port 8001. For your 3rd question, I haven't created a default page for IIS, but if one is already there, I will try your suggestion when I return home today and let you know the results.

Julian, when I return home today, I will try your suggestion as well.

I know this topic is getting old, but I would really like to be able to view/test my asp pages at home. Years ago, I used PWS (I actually still have Win98 running on one of my desktops at home) using DW and Homesite, and I had no problem testing my asp pages.

I'm stumped. Any more help is always appreciated.

Rod
Inspiring
October 4, 2006
You'll need to untick your 'friendly messages' option in IE. This will give
a more descriptive error message.

--
Jules
http://www.charon.co.uk/charoncart
Charon Cart 3
Shopping Cart Extension for Dreamweaver MX/MX 2004



Inspiring
October 4, 2006
so you're using port 8001 for IIS? Then it should be
http://localhost:8001/gb/gb_proc.asp. Why aren't you using the default port
80?

What happens if you open a browser and type http://localhost/ ? Does the
default IIS page come up?


--
Nancy Gill
Adobe Community Expert
BLOG: http://www.dmxwishes.com/blog.asp
Author: Dreamweaver 8 e-book for the DMX Zone
Co-Author: Dreamweaver MX: Instant Troubleshooter (August, 2003)
Technical Editor: DMX 2004: The Complete Reference, DMX 2004: A Beginner's
Guide, Mastering Macromedia Contribute
Technical Reviewer: Dynamic Dreamweaver MX/DMX: Advanced PHP Web Development


"rod06" <webforumsuser@macromedia.com> wrote in message
news:efuhq3$2ub$1@forums.macromedia.com...
> HI Nancy, THANKS for your reply. I typed the wrong URL in my question but
> not
> in the browser. Actually, I just hitting "F12" to view the page in the
> browser
> (using IE 5 & 6) which is http://localhost/gb/gb_proc.asp . however, the
> page
> is not displaying. I'm not sure why not. My aspx pages show with no
> problem
> (using the 8001 port), but not the asp pages. I followed the tutorial in
> DWMX
> 2004 on setting up the local and testing servers (I've done this ALOT at
> work)
> it's really very easy to do - this is why I don't understand why I can't
> test
> my asp pages on my laptop.
>
> I could use more help figuring this out . . .
>
> Thanks again!
>
> Rod
>


rod06Author
Participant
October 3, 2006
HI Nancy, THANKS for your reply. I typed the wrong URL in my question but not in the browser. Actually, I just hitting "F12" to view the page in the browser (using IE 5 & 6) which is http://localhost/gb/gb_proc.asp . however, the page is not displaying. I'm not sure why not. My aspx pages show with no problem (using the 8001 port), but not the asp pages. I followed the tutorial in DWMX 2004 on setting up the local and testing servers (I've done this ALOT at work) it's really very easy to do - this is why I don't understand why I can't test my asp pages on my laptop.

I could use more help figuring this out . . .

Thanks again!

Rod
Inspiring
October 3, 2006
The path is correct. The URL prefix, however, should be
http://localhost/dirName rather than c:\localhost\dirName.


--
Nancy Gill
Adobe Community Expert
BLOG: http://www.dmxwishes.com/blog.asp
Author: Dreamweaver 8 e-book for the DMX Zone
Co-Author: Dreamweaver MX: Instant Troubleshooter (August, 2003)
Technical Editor: DMX 2004: The Complete Reference, DMX 2004: A Beginner's
Guide, Mastering Macromedia Contribute
Technical Reviewer: Dynamic Dreamweaver MX/DMX: Advanced PHP Web Development


"rod06" <webforumsuser@macromedia.com> wrote in message
news:efuapp$nuu$1@forums.macromedia.com...
> Hi,
>
> I've created an asp page in Dreamweaver, however, I can't view it. I've
> set
> up the site in the Site Manager for the "testing server" as
> c:\localhost\dirName and the "local server" is my machine as well
> c:\inetpub\wwwroot\dirName\. I had to set up the "testing server" b/c DW
> prompted me to create a testing server in order to view the asp page. I
> running windows XP Professional and using DWMX 2004. When I try to view
> the
> page, I get a "The page cannot be displayed" error like it can't find the
> server.
>
> Can someone help me out with this? I would really like to use my own
> machine
> to test my asp pages.
>
> Thanks!!!
> Rod
>
> P.S. I even tried to use a different port (as I had to do using
> VisualStudio.Net) i.e., c:\localhost:8001\dirName, but this did not work
> either. I'm not concerned with that though, so no need to reply about
> that.
>