E
Earl Partridge
Windows XP, SP2 - FP2000
Several weeks ago after upgrading 98 to XP, and running an .asp page
on my local machine, data from an Access .mdb file would not display.
I received tips regarding IIS, PWS and ASP.
As I understand IIS is loaded with XP. Is PWS also automatically set
to start at boot-up or do I have to enable it in my startup list?
I also read Microsoft KB842242 and thought my problem might have
something to do with IIS being blocked by the Firewall. From that KB
article I think I was able to determine the port used by IIS and I added
that port as an exception in the Firewall.
I then attempt to run that .asp page (Preview in Browser) and all I get
is the code. I unchecked that port from my Firewall Exceptions, and
still only get the code when Preview in Browser.
I am able to work with this live at my host, where everything works
normally.
Several weeks ago after upgrading 98 to XP, and running an .asp page
on my local machine, data from an Access .mdb file would not display.
I received tips regarding IIS, PWS and ASP.
As I understand IIS is loaded with XP. Is PWS also automatically set
to start at boot-up or do I have to enable it in my startup list?
I also read Microsoft KB842242 and thought my problem might have
something to do with IIS being blocked by the Firewall. From that KB
article I think I was able to determine the port used by IIS and I added
that port as an exception in the Firewall.
I then attempt to run that .asp page (Preview in Browser) and all I get
is the code. I unchecked that port from my Firewall Exceptions, and
still only get the code when Preview in Browser.
I am able to work with this live at my host, where everything works
normally.