CopyProxy Does Not Make a Copy for Dual Interfaces

This article was previously published under Q197781
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
If you call CoCopyProxy API on a proxy for a custom (automation) interfacethat is marshalled by the automation marshaller (Oleaut32.dll), the APIwill return the following error:

S_OK
However, no copy will be made.

If you build a proxy/stub .dll for the same interface and use it as themarshaller, the API CoCopyProxy() works.
CAUSE
The old code had the assumption that CreateProxy returned a valid interfaceparameter, which is not TRUE for automation proxies. Automation proxiesreturn the interface pointer only after the channel is connected.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Properties

Article ID: 197781 - Last Review: 02/23/2014 01:12:08 - Revision: 4.1

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft BackOffice Server 4.0
  • kbnosurvey kbarchive kbbug kbfix KB197781
Feedback