By default, .dll extension is not mapped to ASP.DLL, so that is user
misconfiguration that needs to be accounted for.
The "Script Engine" option determines whether one needs "Scripts" or
"Scripts and Executables" Execution permission to allow an Application
Mapping to handle that extension. In other words, suppose .asp is
mapped to ASP.DLL - if "Script Engine" is checked, then you only need
"Scripts" Execute Permission for IIS to allow ASP.DLL process .asp .
Otherwise, you'd need "Scripts and Executables" Execute Permission, and
IIS will return 403 errors for those denials because "Execute"
permission is required but not set.
//David
http://w3-4u.blogspot.com
//
Mercurius.ter.Maximus@[EMAIL PROTECTED]
wrote:
> Thanks for that, I think you fixed it (the 403's prevent total
> confirmation).
>
> There was an IIS Application Mapping for .dll's to be handled by
> asp.dll. Removing the 'Script Engine' option changed nothing.
> Removing the mapping altogether did not change the fact it still
> returns 500, but the IIS logs now read totally differently; they
> changed to re****ting a Biztalk error saying no Receive Location was set
> up. And setting up a Recieve Location in Biztalk quashed that too.
>
> David Wang wrote:
> > I don't know how Biztalk's ISAPI works, but the IIS log line seems to
> > indicate an ASP error that whatever page it is trying to load is
> > malformed because of "Missing_close_of_script_delimiter".
> >
> > Is the IIS Application Mapping for the .dll (or .*) extension
> > configured to be handled by asp.dll ? It means that ASP is mistakenly
> > trying to open the BTSHTTPReceive.dll file (to parse it for ASP code)
> > and upon not finding a %> anywhere in the DLL file, it complains about
> > it with that log entry? Because I find it very weird for access to a
> > Biztalk ISAPI to be writing a log entry like ASP.DLL, unless one
> > happened to misconfigure ASP.DLL to handle that resource extension
> >
> > 403s and 401s can usually be debugged just by looking at the IIS log
> > entry. They both come with sub-error status codes which usually
> > indicate exactly what is wrong (and thus look up the proper remedy to
> > fix it).
> >
> >
> > //David
> > http://w3-4u.blogspot.com
> > //
> >
> >
> > Mercurius.ter.Maximus@[EMAIL PROTECTED]
wrote:
> > > Any hints or tips you have for this C++ programmer in a mire of IIS
and
> > > networking are very much appreciated :D
> > >
> > > I can't debug why I am getting 500's when trying to access, through
a
> > > virtual directory using Internet Explorer, C:\Program
Files\Microsoft
> > > BizTalk Server 2004\HttpReceive\BTSHTTPReceive.dll. According to
the
> > > MSDN link below I should be getting a blank page, with entries in
the
> > > Event Viewer for Biztalk.
> > >
> > > I have previously had days of hassle with 403's and 401's trying to
get
> > > this working. For the 500 I get no errors in the Event Viewer. The
IIS
> > > log reveals nothing to me, it reads (using an existing virtual
> > > directory, then one I created) :
> > >
> > > 2006-10-24 04:09:25 W3SVC1 MyServer 127.0.0.1 GET
> > > /hwsmessages/BTSHTTPReceive.dll
> > > |440|ASP_0116|Missing_close_of_script_delimiter 80 - 127.0.0.1
HTTP/1.1
> > >
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322)
> > > ASP.NET_SessionId=ytnfuq45fyyweu55jgg1dziz - localhost 500 0 0 615
377
> > > 15
> > >
> > > 2006-10-24 04:09:35 W3SVC1 MyServer 127.0.0.1 GET
> > > /newhttprec/BTSHTTPReceive.dll
> > > |440|ASP_0116|Missing_close_of_script_delimiter 80 - 127.0.0.1
HTTP/1.1
> > >
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322)
> > > ASP.NET_SessionId=ytnfuq45fyyweu55jgg1dziz - localhost 500 0 0 614
376
> > > 15
> > >
> > >
> > > Following instructions from...
> > > ms-help://BTS_2004/SDK/htm/ebiz_sdk_samples_yzhk.htm
> > >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS_2004WP/html/ffda72df-5aec-4a1b-b97a-ac98635e81dc.asp
> > > ( Setting Up HTTP Receive)
> > > and general googling I have triple checked that
> > > - Administrator is a member of all the Biztalk and Internet related
> > > groups
> > > - The IIS Application Pool Identity, Web Sites' Anonymous Access and
in
> > > Windows Component Services the IIS COM+ services all use the
> > > Administrator ID.
> > > - IIS has Web Services extensions allowing access to that .dll. I
> > > additionally allowed access to everything.
> > > - All related NTFS permissions seem fine
> > > - In the Local Policies I have enabled Success and Failure auditing
for
> > > both Logon options.
> > >
> > > I think I tried everything except resetting the server and
> > > throwing it out the window.
> > >
> > > Thanks in advance :)
|
