John
Fri Jul 29 16:52:38 CDT 2005
[Bruce sent me the full DEBUG log in email. For the record here's what's
going wrong here. Note I'm on vacation for 2 weeks starting in 2 hours so
please don't be offended at lack of response.]
The problem definitely is a RemoteAdmin bug. The key debugmsg's are:
149993 PID:5d6c442 TID:25bece82 RemoteUI: DefaultPage not specified at
HKLM\\Comm\HTTPD\VROOTS\/RemoteAdmin
149993 PID:5d6c442 TID:25bece82 Unknown: DEBUGCHK failed in file
c:\macallan\public\servers\oak\samples\remoteadmin\core\nasisapi.cpp at line
451
So the issue is "defaultPage" isn in HKLM\COMM\HTTPD\VROOTS\/RemoteAdmin.
At first I thought this was because you'd done something to your servers.reg
or project.reg to override it. On further inspection I found this to be an
architecture bug in RemoteAdmin. If you look in
public\servers\oak\files\servers.reg, the only time that the defaultPage is
ever set is when SERVERS_MODULES_RUI_GATEWAYUI or
SERVERS_MODULES_RUI_SMBPRINT is set (in the @CESYSGEN IF block).
The problem is that you are not building a gateway or an SMB Print server,
the defaultPage isn't there and hence you're out of luck.
You have a couple of options here. Unless you require functionality from
RemoteAdmin, it is probably easiest to create a config ISAPI from scratch
and forget about tying into the RemoteAdmin framework. I have a primitive
(but more usable) HTML generator helper in
\public\servers\oak\samples\natadmin\baseisapi (see ISAPIGen.*) and it is
used in \public\servers\oak\samples\http\webadmin. Or you could of course
hard-code your strings in C files if you're looking for something very
primitive.
If you require RemoteAdmin features ... you can try copying + pasting the
relevant portions of RemoteAdmin into a new ISAPI you create also, though
it's so heavily abstracted it may be hard to work this out.
You could also try reading the RemoteAdmin docs on MSDN and understanding
the code to the point where you create your own "defaultPage" and tie into
the existing RemoteAdmin modules. This actually may not be a lot of work,
but the ramp up could be painful. Try looking at the existing defaultPages
(\public\servers\oak\GWAdmin\html) to use as a template.
My apologies for this. I've previously created a bug to rework remoteAdmin
so that it works right out of the box without having to specify one of 2
configs that not everyone in the world is using, but it won't be until our
next major release until this can be addressed.
--
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.
"casner" <casner@discussions.microsoft.com> wrote in message
news:87C2F0FE-01AA-468D-A221-B752ED9101A7@microsoft.com...
>I don't have the "p" set. I do have
>
> [HKEY_LOCAL_MACHINE\COMM\HTTPD\VROOTS\/RemoteAdmin]
> @="\\windows\\remoteadmin.dll"
> "a"=dword:0
>
> and I figured out after posting that it is not downloading the .dll. What
> it sends me is a zero length file named "remoteadmin", no extension.
>
> "John Spaith [MS]" wrote:
>
>> 2) Downloading DLL rather than executing it on the server...
>> What is the value for HKLM\COMM\HTTPD\VROOTS\/RemoteAdmin, "p":DWORD? (P
>> stands for Permissions) It should not be set, though it it were set
>> incorrectly the web server would download the DLL rather than execute it.