"?ASP Support" in PB 4.2 Platform Feature view and ASP no long

"?ASP Support" in PB 4.2 Platform Feature view and ASP no long

Post by TWlrZ » Wed, 27 Oct 2004 03:05:09


Thanks for the help.
ASP.DLL is in the flatrelease directory and I tried rebuilding ALL but it
still won't work.
I looked at the current-httpd.log but it just shows the same error I see in
IE6 browser
(error 501):

Mon, 25 Oct 2004 16:39:07 The web server is starting up.
Mon, 25 Oct 2004 16:43:33 192.168.123.102 GET / 200
Mon, 25 Oct 2004 16:43:43 192.168.123.102 GET /adminasp/defaultasp.htm 200
Mon, 25 Oct 2004 16:43:46 192.168.123.102 GET /adminasp/settings.asp 501
Mon, 25 Oct 2004 16:43:50 192.168.123.102 GET /adminasp/vroots.asp 501
Mon, 25 Oct 2004 16:43:54 192.168.123.102 GET /adminasp/logview.asp 501
Mon, 25 Oct 2004 16:44:06 192.168.123.102 GET /sysadmin 302

defaultasp.html is just a bunch of links to 3 asp pages and they don't seem
to load.
I guess it's time to follow it with the de *** ...
Mike
 
 
 

"?ASP Support" in PB 4.2 Platform Feature view and ASP no long

Post by John Spait » Wed, 27 Oct 2004 07:00:06

nother thing that may help narrow this down a bit. In your flatrelease dir
open up httpd.map, then look up InitASP. If everything is working right
(ASP in your image and build is all happy) you should see an "asp.obj" on
this line. If something is screwed up (HTTPD built without "knowing" ASP is
in the platform) you'd see aspstub.obj. This is my guess as to what's going
wrong, though I'm not sure why this is happening. I'll think more about it
if you confirm this is the problem.

Also you need to have JScript and or VBScript included in your platform for
ASP to work. However, if they weren't included then I think you'd get a
different error than 501.

--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation

Check out the new CE Networking Team Blog at http://blogs.msdn.com/cenet/.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. 2003 Microsoft Corporation. All rights
reserved.

"Mike"<< XXXX@XXXXX.COM >> wrote in message
news: XXXX@XXXXX.COM ... >> Thanks for the help. >> ASP.DLL is in the flatrelease directory and I tried rebuilding ALL but it >> still won't work. >> I looked at the current-httpd.log but it just shows the same error I see >> in >> IE6 browser >> (error 501): >> >> Mon, 25 Oct 2004 16:39:07 The web server is starting up. >> Mon, 25 Oct 2004 16:43:33 192.168.123.102 GET / 200 >> Mon, 25 Oct 2004 16:43:43 192.168.123.102 GET /adminasp/defaultasp.htm 200 >> Mon, 25 Oct 2004 16:43:46 192.168.123.102 GET /adminasp/settings.asp 501 >> Mon, 25 Oct 2004 16:43:50 192.168.123.102 GET /adminasp/vroots.asp 501 >> Mon, 25 Oct 2004 16:43:54 192.168.123.102 GET /adminasp/logview.asp 501 >> Mon, 25 Oct 2004 16:44:06 192.168.123.102 GET /sysadmin 302 >> >> defaultasp.html is just a bunch of links to 3 asp pages and they don't >> seem >> to load. >> I guess it's time to follow it with the debugger... >> Mike >> >> "John Spaith [MS]" wrote: >> >>> The question marks are there by design - I see them in my catalog viewer >>> too. I think they indicate that ASP and JScript/VBScript are optional >>> components that you don't have to include with the web server. >>> >>> Do you have asp.dll in your flatrelease directory? My guess is somehow >>> your >>> platform got built without it. If asp.dll isn't there, drag+drop the asp >>> from your feature view into the image and then rebuild your platform. If >>> ASP.dll is in your flatreleasedir already and you're seeing these >>> problems, >>> try rebuilding your platform anyway. Something may have got messed up - >>> effectively platform rebuild is the Control-Alt-Delete equivalent on CE >>> :). >>> >>> If this still doesn't help, post \windows\www\current-httpd.log (or >>> something like that) and maybe this will have some insight, as it's >>> httpd's >>> log. If there's nothing helpful there and still failing, you'll need to >>> get >>> a debug image of the OS (or at least debug HTTPD.dll and ASP.dll) and >>> turn >>> on full debug zones and then post to the newsgroup for me to look at. >>> >>> -- >>> John Spaith >>> Software Design Engineer, Windows CE >>> Microsoft Corporation >>> >>> Check out the new CE Networking
 
 
 

"?ASP Support" in PB 4.2 Platform Feature view and ASP no long

Post by TWlrZ » Thu, 28 Oct 2004 02:31:06

hat's it. I created a test platform from scratch and it works...
so I
1. ripped out ASP , JSCRIPT, VBSCRIPT from my platform
2. rebuilt everything
3. added back in ASP , JSCRIPT, VBSCRIPT to my platform
4. rebuilt everything

and now it works.
Thanks for the help!
Mike



"John Spaith [MS]" wrote: