05-10-2011, 06:33 AM
Error (0x800A175D) means "Could not open macro storage."
Which is an error created when trying to "extract" the information from word.
Try using a different document, the one you're using could be corrupted.
Now the following I may be way off but read it over...
I looked in msdn and I found 2 possibility :
1 - normal.dot is corrupted
The Normal.dot template file used by Word might be corrupt. If you are encountering one of the errors described in the Summary section, you can temporarily rename the Normal.dot template to determine if it is the cause of the problem.
Renaming the Normal.dot template resets several options back to their default settings, including custom styles, custom toolbars, macros, and AutoText entries. It is strongly recommended that you rename the Normal.dot file rather than deleting it, so that you can restore these settings if the template is not corrupt.
Certain installations of Word may yield more than one legitimate Normal.dot file. These situations include multiple versions of Word running on the same computer or several user profiles on the same computer. In these situations, pay special attention so that you rename the correct copy of Normal.dot.
To rename the Normal.dot file follow these steps:
Quit all instances of Word, including WordMail.
On the Windows taskbar, click Start, point to Find, and click Files or Folders.
In the Named box, type Normal.dot.
In the Look In box, select your local hard disk drive (or an alternate user template location if you are running Word from a network server).
Click Find Now to search for the file.
For each occurrence of Normal.dot that appears in the Find dialog box, right-click the file. Click Rename on the shortcut menu. Give the file a new name, such as OldNormal.dot or Normal-1.dot.
Minimize the find dialog box.
Restart your automation client to start Word.
2 - problem of permission
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.
Which is an error created when trying to "extract" the information from word.
Try using a different document, the one you're using could be corrupted.
Now the following I may be way off but read it over...
I looked in msdn and I found 2 possibility :
1 - normal.dot is corrupted
The Normal.dot template file used by Word might be corrupt. If you are encountering one of the errors described in the Summary section, you can temporarily rename the Normal.dot template to determine if it is the cause of the problem.
Renaming the Normal.dot template resets several options back to their default settings, including custom styles, custom toolbars, macros, and AutoText entries. It is strongly recommended that you rename the Normal.dot file rather than deleting it, so that you can restore these settings if the template is not corrupt.
Certain installations of Word may yield more than one legitimate Normal.dot file. These situations include multiple versions of Word running on the same computer or several user profiles on the same computer. In these situations, pay special attention so that you rename the correct copy of Normal.dot.
To rename the Normal.dot file follow these steps:
Quit all instances of Word, including WordMail.
On the Windows taskbar, click Start, point to Find, and click Files or Folders.
In the Named box, type Normal.dot.
In the Look In box, select your local hard disk drive (or an alternate user template location if you are running Word from a network server).
Click Find Now to search for the file.
For each occurrence of Normal.dot that appears in the Find dialog box, right-click the file. Click Rename on the shortcut menu. Give the file a new name, such as OldNormal.dot or Normal-1.dot.
Minimize the find dialog box.
Restart your automation client to start Word.
2 - problem of permission
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.