Microsoft KB Archive/224338: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
| Line 12: | Line 12: | ||
<div id="TitleRow"> | <div id="TitleRow"> | ||
= <span id="KB224338"></span>Error message in Word: | = <span id="KB224338"></span>Error message in Word: "800A175D - Could Not Open Macro Storage" = | ||
| Line 55: | Line 55: | ||
== CAUSE == | == CAUSE == | ||
Word is started under a user account whose | Word is started under a user account whose "user hive" is not loaded. By default, only the interactive user and services running from a user account have their User Registry hive loaded. | ||
</div> | </div> | ||
| Line 76: | Line 76: | ||
You must identify under what user account Word is running, and in what context you are developing. For example, if you are automating from a Microsoft Transaction Server (MTS) package, the default user account is IWAM_MachineName.<br /> | You must identify under what user account Word is running, and in what context you are developing. For example, if you are automating from a Microsoft Transaction Server (MTS) package, the default user account is IWAM_MachineName.<br /> | ||
<br /> | <br /> | ||
In this scenario, you can change the user to | In this scenario, you can change the user to "Interactive User" in the Internet Service Manager Microsoft Management Console, right-click your package, click the '''Identity''' tab, and then click '''Interactive User'''.<br /> | ||
<br /> | <br /> | ||
'''Note''' MTS might be involved implicitly when automating from ASP. Such an example is when you set your Web application to run in | '''Note''' MTS might be involved implicitly when automating from ASP. Such an example is when you set your Web application to run in "isolation mode," or when you use '''Server.CreateObject''' in Active Server Pages (ASP) code.<br /> | ||
<br /> | <br /> | ||
In other situations, using the DCOMCNFG.exe utility is appropriate for setting the user under which Word runs. | In other situations, using the DCOMCNFG.exe utility is appropriate for setting the user under which Word runs. | ||
Latest revision as of 13:42, 21 July 2020
Article ID: 224338
Article Last Modified on 5/11/2007
APPLIES TO
- Microsoft Office Word 2007
- Microsoft Office Word 2003
- Microsoft Word 2002 Standard Edition
- Microsoft Word 2000 Standard Edition
- Microsoft Word 97 Standard Edition
This article was previously published under Q224338
SYMPTOMS
You receive the error message 0x800A175D or -2146822307 when you use Microsoft Office Word as an automation server.
CAUSE
Word is started under a user account whose "user hive" is not loaded. By default, only the interactive user and services running from a user account have their User Registry hive loaded.
RESOLUTION
Microsoft advises that automation of the Microsoft Office products in this context is not supported. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
257757 Considerations for server-side Automation of Office
To avoid the error, do one of the following:
- Start Word as the Interactive User.
- Start Word as a user with administrator rights.
- Load the user hive for the user account programmatically, or have a dummy service that runs under the user account.
You must identify under what user account Word is running, and in what context you are developing. For example, if you are automating from a Microsoft Transaction Server (MTS) package, the default user account is IWAM_MachineName.
In this scenario, you can change the user to "Interactive User" in the Internet Service Manager Microsoft Management Console, right-click your package, click the Identity tab, and then click Interactive User.
Note MTS might be involved implicitly when automating from ASP. Such an example is when you set your Web application to run in "isolation mode," or when you use Server.CreateObject in Active Server Pages (ASP) code.
In other situations, using the DCOMCNFG.exe utility is appropriate for setting the user under which Word runs.
REFERENCES
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
158229 Security ramifications for IIS applications
Additional query words: iis 0x800A175D -2146822307 WD2003 WD2007
Keywords: kbautomation kbdcom kberrmsg kbprb KB224338
