|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 928890 - Last Review: August 17, 2011 - Revision: 2.0 Error message when you try to open a publication in Publisher: "Publisher cannot open the file" or "Publisher has detected a problem"Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986Â
(http://kbalertz.com/Feedback.aspx?kbNumber=256986/
)
Description of the Microsoft Windows registry When you try to open a publication in Microsoft Publisher, you may receive one of the following error messages, depending on the version of Publisher that you are running: - Microsoft Publisher 2000:
Publisher cannot open this file. This is not a Publisher file. - Microsoft Publisher 2002 or Microsoft Office Publisher 2003:
Publisher cannot open the file. - Microsoft Office Publisher 2007:
Publisher has detected a problem in the file you are trying to open. To protect your computer, Publisher will not open the file.
To verify the error message that you receive, press CTRL+SHIFT+I. The following number is displayed in the lower-right corner of the error message dialog box:
1100931 Publisher 2000, Publisher 2002, and Publisher 2003This issue occurs in Publisher 2000, Publisher 2002, and Publisher 2003 if the following conditions are true:
- You have installed security update 894540, security update 894541, or security update 894542. These security updates are described in security bulletin MS06-054.
- The publication that you are trying to open contains unexpected data. Alternatively, the publication may be damaged.
Security update 894540, security update 894541, and security update 894542 block publications that seem to be damaged, that are altered in a malicious way, or that contain unexpected data.
Publisher 2007This issue occurs in Publisher 2007 when you try to open publications that seem to be damaged, that are altered in a malicious way, or that contain unexpected data.
To resolve this issue, you must add the PromptForBadFiles registry subkey. This subkey lets you open a publication after a message prompts you to verify that you want to open the publication. Add the PromptForBadFiles registry subkey to one of the following registry keys, as appropriate for the version of Publisher that you are running: - Publisher 2000:
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Publisher - Publisher 2002:
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Publisher - Publisher 2003:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Publisher - Publisher 2007:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Publisher
The values for the PromptForBadFiles subkey are as follows:
- 0 (zero): When this value is set, suspect publications are blocked. By default, the PromptForBadFiles subkey is set to 0 (zero).
- 1: When this value is set, you receive a message that prompts you to verify that you want to open the publication.
To add the PromptForBadFiles subkey to the registry, follow these steps, as appropriate for the version of Microsoft Windows that you are running. Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To have us fix this problem for you, go to the " Fix it for me" section. If you prefer to fix this problem yourself, go to the " Let me fix it myself" section. Fix it for meTo fix this problem automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard. Notes- This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
- If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Then, go to the " Did this fix the problem?" section. Let me fix it myselfWindows XP- Exit Publisher.
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click to select the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\Office_version#.0\Publisher - After you select the key that is specified in step 3, point to New on the Edit menu, and then click DWORD Value.
- Type PromptForBadFiles, and then press ENTER.
- Right-click PromptForBadFiles, and then click Modify.
- In the Value data box, type 1, and then click OK.
- On the File menu, click Exit to exit Registry Editor.
Windows Vista- Exit Publisher.
- Click Start
Collapse this imageExpand this image
, type
regedit
in the Start Search box, and then click Regedit in the Programs list.
Collapse this imageExpand this image
If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
- Locate and then click to select the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Publisher - After you select the key that is specified in step 3, point to New on the Edit menu, and then click DWORD Value.
- Type PromptForBadFiles, and then press ENTER.
- Right-click PromptForBadFiles, and then click Modify.
- In the Value data box, type 1, and then click OK.
- On the File menu, click Exit to exit Registry Editor.
After you add the PromptForBadFiles subkey, you will receive the following message when you try to open a publication:
Publisher has detected a problem in the file you are trying to open. If you are certain that this file came from a trusted source and does not contain harmful information, click OK. If you received this file from another person or machine and are not sure that the contents are safe, click Cancel.
Did this fix the problem?- Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support
(http://support.microsoft.com/contactus)
.
- We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me
(http://blogs.technet.com/fixit4me/)
" blog or send us an email
(mailto:fixit4me@microsoft.com?Subject=KB)
.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
910729Â
(http://kbalertz.com/Feedback.aspx?kbNumber=910729/
)
MS06-054: Vulnerability in Microsoft Publisher could allow remote code execution
894540Â
(http://kbalertz.com/Feedback.aspx?kbNumber=894540/
)
Description of the security update for Publisher 2000: September 12, 2006
894541Â
(http://kbalertz.com/Feedback.aspx?kbNumber=894541/
)
Description of the security update for Publisher 2002: September 12, 2006
894542Â
(http://kbalertz.com/Feedback.aspx?kbNumber=894542/
)
Description of the security update for Publisher 2003: September 12, 2006
APPLIES TO- Microsoft Office Publisher 2007
- Microsoft Office Publisher 2003
- Microsoft Publisher 2002 Standard Edition
- Microsoft Publisher 2000 Standard Edition
| kbofficealertid kberrmsg kbopenfile kbexpertisebeginner kbtshoot kbprb kbpubtypekc kbfixme kbmsifixme KB928890 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
 |
 |
 |
 |
 |
 |
 |
| |