[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 192
  • Last Modified:

ISAPI DLL will not execute with Windows XP Professional.

I have a project which runns on Windows 2K, but since changing to windows XP I cannot get the thing to execute.
In both occasions I use IIS.

I have re-compiled the WEB DLL to an EXE, and this works fine.
But with XP I just cannot get the DLL's to run. All I get is "The page cannot be displayed".


Is there a setting on the IIS that I have missed ?
0
chunky1
Asked:
chunky1
1 Solution
 
BlackTigerXCommented:
(from IIS manager) did you set the Execute Permissions to Scripts and Executables in the folder where you dropped your ISAPI DLL?

if you did, then the only other thing to do is use a log file where you write from your ISAPI file all the steps, then you'll be able to see where it "broke"

Other thing you might want to do is in your Internet Options | Advanced, Browsing, check OFF the option "Show friendly HTTP error messages"
0
 
DavidBirch2dotComCommented:
You may need to set the DLL as an 'Allowed Web Server Extension' under the ISS manager, this got my projects up and running.

DAvid
0
 
DavidBirch2dotComCommented:
This file has alot of info related to moving between 2000 and 2003/XP might be of some use
www.microsoft.com/korea/ windowsserver2003/docs/MovingNT4.doc

page 9 looks interesting - have you checked your security measures ?

David
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
BlackTigerXCommented:
for XP you should only need to set the Scripts and Executables permission... for 2003 is where you need to add the "allowed server extension"
0
 
DavidBirch2dotComCommented:
BlackTigerX  > technicalities technicalities, it still might well help - wouldnt it depend on which version of ISS is running ?
0
 
chunky1Author Commented:
In IIS I have the Execute permissions set to 'Scripts & Executables'.

I cannot create a log file from my DLL as it never loaded, This I have prooven by inserting a basic 'beep' statement in the oncreate routine.

I have set my browser configuration to dis-allow any friendly messages, after looging at the log file for the IIS status 500 is returned.

I have tried looking for where I can set the DLL as an allowed Web Server Extension, but I am not sure where this is. I have a setting tab called 'Server Extensions'  but in here I have two options :- 1. Enable Authoring. 2. Don't inherit secuity settings.

IIS is version 5.1

I have also read the interesting article from David but after reading through it and doing some investigating, I dont seem to have a copy of the lockdown wizard.
0
 
BlackTigerXCommented:
you need to put your logging mechanism not inside the class only, but from the DLL, so you can see before it even creates the module
are you using any third party components from that ISAPI DLL? if you are, then that could be the problem if you don't have the necessary DLLs in the other machine

"allowed Web Server Extension" is only required in Windows 2003 (IIS 6), for IIS 5.1 you only need to do the Scripts and Executables
0
 
DavidBirch2dotComCommented:
The IIS look down tool is located here

http://www.microsoft.com/technet/security/tools/locktool.mspx

have you got microsofts ISAPI Filter Enabled? you need that to run any ISAPI dll's, I assume its automaticaly enabled...

David
0
 
DavidBirch2dotComCommented:
A lot of general ISAPI info here, prehaphs somthing there might help

http://www.dataweb.de/en/support/isapi.html

David
0
 
primusmagestriCommented:
Set the security level to low to default web site and your virtual directories (for test only). Set the user that will be used to authenticate with this application (put in a local user on that machine, not the usual IUSR_... :)) Try to debug your application and see where it fails.
From my experience, there should be no problem running an ISAPI dll on wXP if it worked on w2K.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now