Microsoft KB Archive/297217

= OLE Interfaces That Use the Formatetc Structure May Not Work with Terminal Services =

Article ID: 297217

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server

-



This article was previously published under Q297217



SYMPTOMS
OLE interfaces that use custom clipboard formats may not work when calling across Terminal Server sessions.

Some OLE interfaces, such as IAdviseSink, use the Formatetc structure. This structure contains a cfFormat value that is a clipboard format. There are standard clipboard formats (such as CF_TEXT), or programs can define custom clipboard formats by calling the RegisterClipboardFormat function.

If a program uses these OLE interfaces with a custom clipboard format while calling across Terminal Server sessions, the cfFormat value does not have the correct value. An example of calling across sessions is when an OLE client process is run in a Terminal Server session and connects to an OLE server that runs as a system service.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English-language version of this fix should have the following file attributes or later:   Date      Time   Version           Size       File name --  08/16/01  11:34  2000.2.3483.0       166,160  Catsrv.dll 08/16/01 11:34  2000.2.3483.0       575,248  Catsrvut.dll 08/16/01 11:34  2000.2.3483.0        96,016  Clbcatex.dll 08/16/01 11:34  2000.2.3483.0       509,712  Clbcatq.dll 08/16/01 11:34  2000.2.3483.0        37,648  Colbact.dll 08/16/01 11:34  2000.2.3483.0       193,296  Comadmin.dll 08/16/01 11:34  2000.2.3421.3483    341,776  Comsetup.dll 08/16/01 11:34  2000.2.3483.0     1,422,096  Comsvcs.dll 08/16/01 11:34  2000.2.3483.0       625,936  Comuid.dll 08/15/01 12:34  2000.2.3483.0       818,432  Dtcsetup.exe 08/16/01 11:34  2000.2.3483.0       236,816  Es.dll 08/16/01 11:34  2000.2.3483.0       681,744  Msdtcprx.dll 08/16/01 11:35  2000.2.3483.0     1,121,040  Msdtctm.dll 08/16/01 11:35  2000.2.3483.0       145,680  Msdtcui.dll 08/15/01 12:41  2000.2.3483.0       151,312  Mtstocom.exe 08/16/01 11:35  2000.2.3483.0        52,496  mtxclu.dll 08/16/01 11:35  2000.2.3483.0        23,824  mtxdm.dll 08/16/01 11:35  2000.2.3483.0       104,208  Mtxoci.dll 08/16/01 11:34  5.0.2195.3881       940,816  Ole32.dll 08/16/01 11:34  5.0.2195.4109       427,792  Rpcrt4.dll 08/16/01 11:34  5.0.2195.3881       185,104  Rpcss.dll 08/16/01 11:34  2000.2.3483.0       391,952  Txfaux.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.



MORE INFORMATION
For additional information about the availability of the update that is described in this article, click the article number below to view the article in the Microsoft Knowledge Base:

302845 INFO: Post Windows 2000 Service Pack 2 COM+ Rollup Hotfix Pkg 14

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Additional query words: kbIISCom kbWin2000preSP3COM Rollup14Fix

Keywords: kbbug kbfix kbwin2000presp3fix kbqfe kbwin2000sp3fix kbhotfixserver KB297217

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.