An assembly file name is truncated to 128 characters in the DCS Admin Console when the assembly is added from the workflow task edit form in Customer Care Framework 2009

Gjelder: Microsoft Customer Care Framework 2009

Symptoms


When an assembly file name is added from the workflow task edit form by using the Microsoft Distributed Connectivity Services (DCS) Admin Console in Microsoft Customer Care Framework 2009, the assembly file name is truncated to 128 characters if its length exceeds 128 characters. Additionally, a similar issue may be experienced when a new DCS service is deployed that has an assembly file name that exceeds 128 characters.

Resolution


To resolve this problem, apply this hotfix. After this hotfix is installed, the assembly file name is limited to 256 characters. This includes the file name extension of the assembly file name.

The full file name of the assembly must be 256 characters or less, as in the following example:
C:\Repository\wwwroot\bin\Assembly_Name.dll

More information about this hotfix

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must apply this hotfix to a computer that is running the following:
  • Distributed Connectivity Services (DCS) Service Pack 1 (SP1)
  • DCS Service Pack 1 (SP1) Business Logic Visual Studio Extensions

Restart information

You do not have to restart the computer after you apply this hotfix. However, you must restart the Internet Information Services (IIS) service.

Installation information

  1. Apply this hotfix to a computer that hosts the DCS management services, DCS-based Business services, and the DCS Management console.
  2. Update the following variables in the “128CharacterIssue_AssemblyName.bat” file to actual values:
    SET SERVERNAME="DCS-64BIT-01\SQLEXPRESS"
    SET SQL_FILE_1=".\ CFF_InsertTask.sql"
    SET SQL_FILE_2=".\ CFF_UpdateTask.sql "
    SET SQL_FILE_3=".\ CFF_EnableServerCacheRefresh.sql "
    SET DLLPATH =".\ Microsoft.ConnectedIndustry.ProcessExecution.Entities.dll"

    Update the DCS installation path for the following variable:
    SET DCS_PATH=C:\Program Files\Microsoft CIS

    Update the DCS VS extension installation path for the following variable:
    SET DCS_EXT_PATH=C:\Program Files\Microsoft CIS

    Update the Visual Studio installation path for this variable:
    SET VS_PATH=C:\Program Files
  3. Exit all running instances of Microsoft Visual Studio.
  4. In the MMC, close all open DCS snap-ins.
  5. As an administrator, run the “128CharacterIssue_AssemblyName.bat” file in a Visual Studio command prompt.

The batch file modifies the dbo.InsertTask and the dbo.UpdateTask that are stored procedures in the DCSManagementDB database, and the batch file replaces the Microsoft.ConnectedIndustry.ProcessExecution.Entities.dll file in the following locations:
  • C:\Program Files\Microsoft CIS\DCS\V1.0\Bin
  • C:\Program Files\Microsoft CIS\DCS Business Logic Visual Studio Extensions VS2008\DeploymentTool
  • C:\Program Files\Microsoft CIS\DCS Business Logic Visual Studio Extensions VS2008\ ProxyBuilder
  • C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies

Additionally, the batch file also adds the Microsoft.ConnectedIndustry.ProcessExecution.Entities.dll file to the Global Assembly Cache (GAC).

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTime
128characterissue_assemblyname.batNot Applicable5,49512-Aug-201008:17
Cff_enableservercacherefresh.sqlNot Applicable6,29912-Aug-201008:15
Cff_inserttask.sqlNot Applicable3,14411-Aug-201007:46
Cff_updatetask.sqlNot Applicable3,15511-Aug-201007:45
Microsoft.connectedindustry.processexecution.entities.dll1.5.0.138195,32813-Aug-201003:31
Read me.docNot Applicable44,03231-Aug-201003:59

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.