Microsoft KB Archive/326144

= PRB: &quot;Permission Denied&quot; Error Message When You Start Orchestration Designer =

Article ID: 326144

Article Last Modified on 6/4/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition
 * Microsoft BizTalk Server 2002 Standard Edition

-



This article was previously published under Q326144



SYMPTOMS
When you try to start the BizTalk Orchestration Designer, you may receive the following error message:

Problem in General.startVisio

Error Number: 70

Error Description: Permission denied

After you click OK to dismiss this error message, you receive the following error message:

BizTalk Orchestration Designer cannot start Microsoft Visio.

Check your Visio installation and try starting BizTalk

Orchestration Designer again.

After you click OK to dismiss this error message, the BizTalk Orchestration Designer closes.



CAUSE
This problem occurs if the user who is trying to start the BizTalk Orchestration Designer does not have the &quot;Allow Access&quot; permission for Distributed COM (DCOM) applications.



RESOLUTION
To resolve this problem, add the user who is trying to start the BizTalk Orchestration Designer to the list of users who are permitted access to applications that do not provide their own settings. To do this, follow these steps:
 * 1) Click Start, click Run, type DCOMCNFG, and then click OK.
 * 2) On the Default Security tab, click Edit Default.
 * 3) In the Names list, click the user, the users, the group, or the groups.
 * 4) In the Type of Access list, click Allow Access.
 * 5) Click OK to close the Dcomcnfg.exe utility.



STATUS
This behavior is by design.



MORE INFORMATION
By default, the list of users who can access applications that do not provide their own settings is blank in the Dcomcnfg.exe utility. When this list is blank, only the SYSTEM and Principal users are granted the &quot;Allow Access&quot; permission. As soon as an entry is added to the list, the &quot;Allow Access&quot; permission is restricted to only those entries that are listed.

This problem occurs when an application adds an entry to the list that was previously blank, which then limits access to only that entry.

Additional query words: launch exits

Keywords: kbprb KB326144

-

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

© Microsoft Corporation. All rights reserved.