Hi Larry,
All the best to you in the new year!
"Do I spawn the process with some kind of special permissions set or do I
create the pipe with appropriate permission?"
[WenJun]
You can verify this via some debug utilities like Process Explorer.
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExp
lorer.mspx
To check:
1. Open Process Explorer.
2. Locate to your spawned process.
3. In the below Object list, named pipes will be displayed as File type
objects and generally with a name like \Device\NamedPipe\<Pipe Name>
4. Find the pipe you created and double-click it to check the permission
set of it in Security tab.
"In either case, do you have a sample that would show the appropriate
creation of the object?"
[WenJun]
No, I don't have a specific sample which applies to your scenario in hand.
However if you are willing to send your problematic project to me, I will
be glad to try reproducing the problem and assist on the test &
troubleshooting.
To clarify more of the issue, my understanding of the problem is:
1) Spawning an process from your ISAPI extension code which is executed by
IIS.
2) The spawned process creates a name pipe in it.
3) Try to connect to the named pipe from another external process(get an
Access Denied error).
Also if the process in step #2 isn't spawned by ISAPI, the step #3 will
succeed.
Could you please confirm if this above catches the issue exactly? If so, as
I mentioned before, the first key point is to check the process in step #1
is spawned with which account. Is it the anonymous IUSR_<machinename>
account (IUSR's permission is very weak and limited)? Please check this in
Task Manager(or by adding User Name column in Process Explorer view).
Also I wonder the result when disabling anonymous access and launching the
ISAPI extension with Basic authenticaiton(login with your administrator
account). Or you can temporarily add IUSR_<machinename> account to local
Administrators group to test.
If the process does run with IUSR account and the code can work with Basic
auth (or granting IUSR with admin permission), we can narrow down the issue
is due to IUSR lacks for some particluar permission.
Named Pipe Security and Access Rights
http://msdn2.microsoft.com/en-gb/library/aa365600.aspx
Look forward to your update.
Sincerely,
WenJun Zhang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>> Stay informed about: Access denied, trying access a named pipe. from inside IIS.