Feb 18, 2008

IIS 6.0 - HTTP Error 401.1


On this week I had a strange problem when working with Asp.Net site on IIS 6.0, Win 2003.
I defined an application pool to run under
domain user account and Web site is configured to use Integrated Windows authentication only.
Just for the record the I gave the domain account administrators permissions on the server.
I tried to consume the web site with the same user from the server but get the following error :

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.

I managed to workaround this issue by setting the web site to work with digest authentication.

Please consider the security issues before doing it, I worked on a test environment on the organization intranet.

Another issue was when I tried to consume the web site from different pc with
other domain account which was defined as a member of the user group on the server.
I get the user/password dialog box.
I manage to fix the problem by this Microsoft KB article http://support.microsoft.com/kb/871179/

Because I worked on a test environment and need a fast solution I went on the workaround section and It do the job.


To work around this behavior if you have multiple application pools that run under different domain user accounts, you must force IIS to use NTLM as your authentication mechanism if you want to use Integrated Windows authentication only. To do this, follow these steps on the server that is running IIS:
1.Start a command prompt.
2.Locate and then change to the directory that contains the Adsutil.vbs file. By default, this directory is C:\Inetpub\Adminscripts.
3.Type the following command, and then press ENTER:
cscript adsutil.vbs set w3svc/NTAuthenticationProviders "NTLM"
4.To verify that the NtAuthenticationProviders metabase property is set to NTLM, type the following command, and then press ENTER:
cscript adsutil.vbs get w3svc/NTAuthenticationProviders
The following text should be returned:
NTAuthenticationProviders       : (STRING) "NTLM"

Feb 12, 2008

Biztalk 2006 MQSC adapter


In this post I will explain the benefit of the MQSC (WMQ native api client adapter) over MQS (COM+ server adapter).

When working with wmq and Biztalk on multi server environment I suggest to work with the MQSC adapter and not with MQS adapter.

Because of the following arguments:
  • MQSC Support clustered MQSeries Queue Managers.
    • The MQS adapter make subscriber for each clustered queue, even if it is the same
      queue, but on different qmgr. Creates duplication of messages.
  • MQSC Support clustered BizTalk servers.
  • You can't difine with the MQS adapter a dynamic recieve loaction. Works only with local Qmgr on the biztalk application server.
  • The COM+ level overhead of the MQS adapter.
  • Can define by WMQ channel table file a simple fail over mechanism, using the wild char "*" in the qmgr name.
You can get the inforamtion about the MQSC adapter here :
When using the MQSC adapter it is very important to set the transaction mode on (default off ) when integrating with WMQ queus. Otherwise duplication of messages can occur.

WMQ CSD Install problem- File in use


When you try to install csd for wmq on an existing running WMQ qmgrs almost in every case the installation will fail because of dlls being in use.
No matter if you already stopped the qmgr and the wmq service.
So if it is your problem then do the following :
  1. extract the csd.
  2. open cmd window.
  3. run in the csd directory amqicsdn -a MQPINUSEOK=1.
Alex Linder.