Microsoft KB Archive/246057

= BUG: RemoteServerName Cannot be Changed in COM+ Explorer for an Application Proxy =

Article ID: 246057

Article Last Modified on 2/21/2002

-

APPLIES TO


 * Microsoft COM+ 1.0

-



This article was previously published under Q246057



SYMPTOMS
When you export a COM+ application as an application proxy on a client computer and you change the RemoteServerName (RSN), the COM+ Explorer displays an error message stating that the Microsoft Messaging Queue Server (MSMQ) is unavailable and logs an error report in the event log.



RESOLUTION
To work around this issue, perform one of the following:

 Change the application proxy (for example, Myapp.msi) RemoteServerName (RSN) to computer XYZ, and then run the following command from the MS-DOS command prompt:

Msiexec /I myapp.msi RemoteServerName=XYZ

-or-

 Specify the server directly by calling the CoCreateInstanceEx function, and then change the server name in the COSERVERINFO structure.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
When you export an application in COM+ as an application proxy, and then install it on a client computer, a COM+ application corresponding to that proxy appears in the COM+ Explorer.

This allows you to edit the RemoteServerName (RSN) for an application proxy. If you change the RSN, subsequent activations of the component take place on the new server that you specified.

When you change the RSN on a client computer, the COM+ Explorer displays the following error message:

An unexpected error was returned by the MSMQ API function indicated. The following error message was retrieved from MSMQ.

MQPathNameToFormatName : The queue pathname specified is invalid.

Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235}

Server Application Name: System Application

Error Code = 0xc00e0014 :

COM+ Services Internals Information:

File: .\msmqrt.cpp, Line: 320

NOTE: This error message is logged as an error report in the event log.

If queuing is enabled on the server application before you export it as an application proxy, COM+ tries to change the MSMQ information to the new RSN specified on the client computer. If MSMQ is not available on the client computer, the error message appears.

Currently, this error message occurs even if queuing is not enabled in the server application.

Steps to Reproduce the Behavior:

 * 1) Create a new COM+ application in Component Services Explorer.
 * 2) Install a new component in the application.
 * 3) Export this application as an application proxy to a client computer running Windows 2000.
 * 4) Install the proxy on this client computer.
 * 5) On the client computer, open the proxy application in Component Services Explorer.
 * 6) Right-click the installed proxy application, and then click Properties.
 * 7) Click the Activation tab, and then change the RemoteServerName.
 * 8) The COM+ Explorer displays an error message stating that the MSMQ is unavailable.

Additional query words: MSMQ, export, application proxy, RSN

Keywords: kbbug kbsysadmin kbclientserver kbpending KB246057

-

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

© Microsoft Corporation. All rights reserved.