PRB: Security May Prevent Creation of Client Installation .Exe

Last reviewed: October 10, 1997
Article ID: Q170835
The information in this article applies to:
  • Microsoft Transaction Server, version 1.0 Service Pack 2a

SYMPTOMS

Microsoft Transaction Server 1.0 Service Pack 2a introduced a new feature in its Package Export utility that creates a client installation executable file. This client installation executable file may not be created if Authorization Checking is enabled on the System package. Instead, Microsoft Transaction Server will log the following error in the event log:

   Client not authorized to make the call.

CAUSE

Microsoft Transaction Server 1.0 Service Pack 2a adds a new component, MTS.ClientExport.1, to the System package. However, it does not authorize any role to use the ClientExport component. Therefore, if Authorization Checking is enabled on the System package, nobody will be able to use the ClientExport component until a role is authorized to use it.

RESOLUTION

Perform the following steps to authorize the Administrator role to use the ClientExport component:

  1. In Microsoft Transaction Server Explorer, select the System package and then the MTS.ClientExport.1 component.

  2. Open ClientExport's Role Membership.

  3. On the File menu, click New.

  4. In the Select Roles dialog box, select the Administrator and click OK.

  5. In Microsoft Transaction Server Explorer, select My Computer.

  6. On the Tools menu, click Shutdown Server Processes.

REFERENCES

For more information, visit the following Web sites:


Additional query words: mts
Keywords : kbprg kbusage TSrvDeploy
Version : 1.0 SP2
Platform : WINDOWS
Issue type : kbprb
Solution Type : Info_Provided


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.