Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 875415 - Last Review: July 27, 2006 - Revision: 2.4
Errors: "Render failed," "Historyfield is undefined," or you cannot delete a document in Project 2002 after you apply Office XP SP3
On This Page
SYMPTOMS
When you apply Microsoft Office XP Service Pack 3, Microsoft Project 2002 may behave in one or more of the following ways:
- When you upload a Project 2002 document, you may receive the following error message:
- When you use Microsoft Internet Explorer to locate the document library and then you click Edit, you may receive the following JScript error message:
Error: HistoryField is undefined
- When you try to delete a document from the document library, you may receive the following error message:
Error: If this problem persists, please contact your administrator
CAUSE
These problems occur if all the following conditions are true:
- You are using Project 2002 with Microsoft Windows SharePoint Services.
- You installed SharePoint Services from the Microsoft Project Server 2002 CD or through the Project Server wizard.
- You applied the Office XP Service Pack 3 on a computer where the answer is "yes" to condition 1 and condition 2 in this list.
RESOLUTION
To resolve these problems, follow these steps:
Note You can find all the files in this section on the Project Server 2002 CD in the \Support\PJSharPT folder.
Solve the Render Failed error
- Replace the Fldtypes.xml file that is located in the \Program Files\Common Files\Microsoft
Shared\WebServer Extensions\50\Templates\1033\xml folder with the Fldtypes.xml file that is located on the Project Server 2002 CD.
Solve the JScript error
- Replace the Ows.js file that is located in the \Program Files\Common Files\Microsoft
Shared\WebServer Extensions\50\Isapi folder with the Ows.js file that is located on the Project Server 2002 CD.
Solve the error while you delete a document in the Edit view
- Replace the following files that are located in the \Program Files\Common Files\Microsoft Shared\WebServer
Extensions\50\Templates\1033\Layouts folder with the files that are located on the Project Server 2002 CD.
- Fldedit.htm
- Fldnew.htm
- Formedt.htm
- Listedit.htm
- Lstsetng.htm
- Viewedit.htm
- Viewnew.htm
- Replace the Onet.xml file that is located in the \Program Files\Common Files\Microsoft Shared\WebServer
Extensions\50\Templates\1033\xml folder with the Onet.xml file that is located on the Project Server 2002 CD.
- Replace the following files that are located in the \Program Files\Common Files\Microsoft Shared\WebServer
Extensions\50\Templates\1033\Layouts\DocLib folder with the files that are located on the Project Server 2002 CD.
- Allitems.htm
- Editform.htm
- Schema.xml
- Upload.htm
- Replace the Ows.js file that is located in the \Program Files\Common Files\Microsoft
Shared\WebServer Extensions\50\Isapi folder with the Ows.js file that is located on the Project Server 2002 CD.
- From a computer that is running Project Server 2002 and SharePoint Services, copy the following files to the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\50\Isapi folder on your computer:
- Owssvr.dll 820,640 bytes
- Shtml.dll 26,016 bytes
Note Make sure that the file size is the same as shown in this section.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft Project Server 2002
- Microsoft Project 2002 Standard Edition
- Microsoft SharePoint Team Services
- Microsoft Office XP, All Editions Service Pack 3 (SP-3)
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
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please