OLE32 Unmarshal Fails for BizTalk Server Schedule Client (317932)
The information in this article applies to:
- Microsoft COM+ 1.5, when used with:
- the operating system: Microsoft Windows XP
This article was previously published under Q317932 SYMPTOMS
When a late binding COM+ or Distributed Component Object Model (DCOM) client (such as a BizTalk Server schedule client) calls a COM+ or DCOM server, the COM+ or DCOM server returns error 0x8004D091 (CALLFRAME_E_COULDNTMAKECALL).
CAUSE
This problem occurs because the ICallFrame::Unmarshal method does not completely fill out the MIDL_STUB_MESSAGE structure that the method passes into the Network Data Representation (NDR) functions. Therefore, under a particular marshalling path, the stub may believe that there is not enough information in the buffer to unmarshall a type. This causes the bad stub data exception.
RESOLUTION
To resolve this problem, obtain Microsoft XP COM+ Hotfix Rollup 1.
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
317926 INFO: Availability of Windows XP COM+ Hotfix Rollup Package 1
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows XP service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
|---|
| Keywords: | kbbug kbfix kbQFE KB317932 |
|---|
|