Unable to find script library '/aspnet_client/system-web/1-1-4322/webvalidation.js'

One of the common errors that may occur when publishing your application to live server is is:
"Unable to find script library '/aspnet_client/system-web/1-1-4322/webvalidation.js'"

This would occur particularly if you are using validation controls in your application. The aspnet_client folder contains the WebUIValidation.js which is required to handle the asp.net validation controls.
If the aspnet_client folder is missing in the IIS virtual directory listing, you may encounter the above error. To resolve this, you may need to run the following from command prompt:
%windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -c

This will install the aspnet_client folder to the default virtual directory website.
If you are using a sub-virtual directory you need to have this aspnet_client folder in your root directory as well. To do this, you can manually copy the folder to your root directory.

BizTalk HTTP Receive Adapter does not work after upgrading from BizTalk Server 2004

Here is an interesting thing that may catch your attention, the BizTalk HTTP Receive Adapter will not work after you have upgraded your server(s) from BizTalk Server 2004 to BizTalk Server 2006.

I ran into this issue a couple weeks ago and the fact that the HTTP Receive adapter was not responding after the upgrade seemed odd, considering it was working perfectly fine with the 2004 version of BizTalk.

After a bit of investigation, I found out that the upgrade process does not apply for the HTTP Receive Adapter and the settings in IIS Manager were pointing to old paths and old assembly locations.

Here are the extra steps that you need to make:
- On the server(s) where you have the HTTP Receive Adapter configured use your IIS Manager and:

• On the BizTalk HTTP Receive Handler Web Service Extension change the path to the BTSHTTPReceive.dll to point to the new location. If you have configured your BizTalk Server 2006 with the default settings this path is: C:\Program Files\Microsoft BizTalk Server 2006\HttpReceive\BTSHTTPReceive.dll
• Change the Local path of the BizTalkHTTPReceive Virtual Directory to its new location. If you have configured your BizTalk Server 2006 with the default settings this path is:
  C:\Program Files\Microsoft BizTalk Server 2006\HttpReceive

Important: If you have multiple servers in your BizTalk Group(s) and/or Cluster(s) you will need to apply changes to all servers that had the BizTalk HTTP Receive Adapter configured prior to the upgrade process.

K2.net 2003 with Kerberos Delegation and Protocol Transition

If you have had the pleasure working with K2.net and made a bold attempt to set it up to work with Kerberos authentication, you may have stumbled upon a few issues like myself.

One of the recent challenges that I have encountered with K2.net was security.

Here is the scenario:

• Windows Server 2003 Active Directory
• Ms SQL Server 2005 - Server A
• K2.net Server 2003- Server B
• IIS/Windows SharePoint Services- Server C
• Kerberos Authentication configured

The business requirements asked for users (each user had an account configured on the AD domain) to be able to access their K2.net Workspace from the anywhere on the Internet. From a glance does not seem to be that complicated, but the complexity was introduced when Kerberos authentication was not working when accessing from the workspace from the Internet, however when users were accessing the workspace from the within the internal domain (where the K2.net infrastructure was implemented) the Kerberos authentication was working without any issues.

User authorization by the K2.net Server can only take place if the K2.net server receives the correct credentials of the user who is accessing K2.net resources.
These resources can be reports and Worklist items in the K2.net Workspace or any other K2.net Integrated Web Form. For this reason you must configure your environment for Kerberos Delegation.

You need to configure the Kerberos Delegation by using a Kerberos Extension called Protocol Transition. The protocol transition extension allows a service that uses Kerberos to obtain a Kerberos service ticket on behalf of a Kerberos principal to the service without requiring the principal to initially authenticate to the Kerberos Key Distribution Center (KDC) with a credential. An example of this scenario might be a user who needs to access K2.net resources from a Public Computer on the Internet.

The steps below will help you configure your platform to be available from the Internet, in the event that your workflow users will need to access the workspace from "the outside world" rather than Internal network.

1. Follow steps required to configure Kerberos Authentication for your K2.net Infrastructure.
2. If your users will access the Workspace from the Internet the following extra steps will be required:


a) Use SSL to encrypt HTTP traffic between users and the IIS server (optional but highly recommended)
b) Setup Protocol Transition/Constrained Delegation, this requires that you raise the Domain Functional level to Windows Server 2003 (use Active Directory Users and Computers)
c) Configure Delegation for the K2Workspace Application Pool Identity(use Active Directory Users and Computers):

· Locate the service account under which the Application Pool where Workspace resides is running.
· In the Delegate tab select the "Trust this user for delegation to specified services only" radio button.
· Select the "Use any authentication protocol" radio button.
· Click the Add button and locate/add:

-The 'K2Server2003' service type for the K2 service account.

-The 'HTTP' service type for the Workspace Application Pool service account.

e) Add the K2workspace Application Pool Identity service account to Domain\Windows Authorization Access Group
f) Use the Local Security Policy editor on the IIS server and the K2workspace Application Pool Identity service account and grant the “Act as part of the operating system” privilege


Reference Documentation

Kerberos Protocol Transition and Constrained Delegation
http://technet2.microsoft.com/WindowsServer/en/library/c312ba01-318f-46ca-990e-a597f3c294eb1033.mspx?mfr=true

How To: Use Protocol Transition and Constrained Delegation in ASP.NET 2.0
http://msdn2.microsoft.com/en-us/library/ms998355.aspx

How To: Use Impersonation and Delegation in ASP.NET 2.0
http://msdn2.microsoft.com/en-us/library/ms998351.aspx

Basic Guide to enabling a K2.net® 2003 Implementation to use Kerberos Authentication
http://kb.k2workflow.com/Articles/KB000123.aspx

BizTalk Server 2006 Comparative Adapter Study

The whitepaper describes the results of a comparative adapter study—a set of tests that compared each adapter that ships with Microsoft® BizTalk® Server 2006 against its BizTalk Server 2004 SP1 counterpart under identical conditions.
Also included are performance test results for the POP3 and Windows® SharePoint® Services adapters, which were not available for BizTalk Server 2004 SP1. The resulting data proves interesting from a solution design standpoint because understanding the performance of each adapter is critical when deciding which adapters to select to meet performance requirements. The test techniques used to arrive at the maximum sustainable throughput (MST) are described in detail, and recommendations for using and configuring specific adapters are provided.

Download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=FDAE55DB-184B-4D93-AD79-A113B5268EE2&displaylang=en

UK SDC BizTalk 2006 Documenter RELEASED

If you are looking for an automated tool that will help you in documentening your BizTalk Solution stop looking, the BizTalk 2006 Documenter will do the job.

The BizTalk 2006 Documenter Creates compiled help files for a given BTS 2006 installation. This tool can be run on an ad-hoc basis using the UI or from the command line as a post build/deploy task to create a compiled help file describing a BTS 2006 installation. It will compile: BTS Host configuration, Send/Receive port configuration, Orchestration diagrams, Schema and Map content, Pipeline process flow, Adapter configuration, Rule engine vocabularies and policies, More… and publish them as compiled help files. Optionally you can embed custom HTML content and custom descriptions for all BTS artifacts to produce a more customized look and feel to the CHM output.

The tool is publicly available and can be dowloaded from from http://www.gotdotnet.com/codegallery/codegallery.aspx?id=0690616f-838c-4583-a4c5-cecc5ac04dac

BizTalk Server Restore Script for BizTalk 2006 Standard Edition

This script is needed for replacement of BizTalk Servers running BizTalk Server 2006 Standard Edition after they encounter an irrecoverable failure.

Read the BizTalk Server product documentation on Disaster Recovery for BizTalk servers for more details on usage of the script.

Download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=e298d070-2504-4645-a651-4a2e52b2fcdb&DisplayLang=en

"The following entry in the [strings] section is too long and has been truncated"

Windows Server 2003 GPO error

When trying to edit a GPO you I was getting the following error message:"The following entry in the [strings] section is too long and has been truncated"

This error message could appear when you try to modify or to view GPOs in Windows Server 2003, Windows XP Professional, or Windows 2000Microsoft acknowledged the problem:SYMPTOMSWhen you try to modify or to view Group Policy objects (GPOs) on a computer that is running Microsoft Windows Server 2003, Microsoft Windows XP Professional with Service Pack 1 (SP1), or Microsoft Windows 2000, you may receive an error message that is similar to the following:The following entry in the [strings] section is too long and has been truncated.Some text may be displayed after this error message, and this text varies in different scenarios. Additionally, if you click OK in the error message window, a similar error message may be repeated. Each error message that is repeated has different text that is displayed after the error message.

This problem occurs because older versions of the Group Policy editor cannot interpret some string types that include more than 255 characters. These string types are included in parts of .adm files that are meant to be excluded by the "IF VERSION" construct.Typically, the problem occurs when you try to view or modify a GPO that has been viewed by a different workstation, and that workstation contains .adm files that use the "IF VERSION >=5" construct. When an administrative workstation views a GPO, the workstation automatically updates that GPO with the latest version of the .adm files. If the workstation's .adm files are newer than the files that are contained in the \Adm folder of the domain GPO, the template files are updated. If the template files contain the "IF VERSION >=5" construct, when an administrative workstation tries to modify or to view the GPO, and the workstation does not have this hotfix installed, the errors occur.NoteAdministrative template (.adm) files that use the "IF VERSION >=5" construct are included in Microsoft Windows XP Service Pack 2 (SP2). This construct prevents unexpected behavior in some Group Policy settings when the settings are modified by older versions of the Group Policy editor.

There is a patch available for download!!!

Download patch

Server Performance Advisor V1.0

Service Performance Advisor is a server performance diagnostic tool developed to diagnose root causes of performance problems in a Microsoft® Windows Server™ 2003 operating system, particularly performance problems for Internet Information Services (IIS) 6.0 and the Active Directory® directory service. Server Performance Advisor measures the performance and use of resources by your computer to report on the parts that are stressed under workload.Other server roles include system overview (hot files, hot TCP clients, top CPU consumed), print spooler, context switch data and preliminary File Server trace data.

You can download the tool from:http://www.microsoft.com/downloads/details.aspx?FamilyID=61a41d78-e4aa-47b9-901b-cf85da075a73&displaylang=en