Mentioned
In
|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 885874 - Last Review: April 7, 2006 - Revision: 4.2 Description of the SharePoint Portal Server 2001 hotfix package: February 9, 2005Microsoft has released the SharePoint Portal Server 2001 hotfix package for Microsoft SharePoint Portal Server 2001. This article describes the following information about the hotfix package: - Issue that the hotfix package fixes
- Prerequisites for installing the hotfix package
- Information about whether you must restart your computer after you install the hotfix package
- Information about whether the hotfix package is replaced by any other hotfix package
- Information about whether you must make any registry changes to use one or more of the hotfixes in the package
- Files that the hotfix package contains
This article describes the SharePoint Portal Server 2001 issue that is fixed in the SharePoint Portal Server 2001 hotfix package that is dated February 9, 2005. Issue that the hotfix package fixesThis hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article: - When you open a file in a document library after you rename the file name extension of that file, the file is opened in an incorrect program. The file is opened in the program that is associated with the old file name extension instead of the program that is associated with the new file name extension. The following is an example of a scenario where you experience these symptoms:
- You connect to a document library and then check in a Microsoft Word document. Then, you publish the Word document.
- You check out the Word document.
- You check in a Microsoft PowerPoint presentation by using the same name and same file name extension as the Word document that you checked out. Then, you publish the file. For example, you check in a file that is named MyFile.ppt as MyFile.doc. Then, you publish the file as MyFile.doc.
Note Although the MyFile.doc file uses a .doc file name extension, the MyFile.doc file is a PowerPoint presentation. - You connect to the document library by using Web folders. Then, you change the file name extension of the file to a .ppt file name extension. For example, you rename the MyFile.doc file to MyFile.ppt.
If you connect to the document library by using Web folders, and then you open the file, the file opens in PowerPoint as expected. However, if you connect to the document library by using a Web browser, and then you open the file, the file opens in Word. In this scenario, Microsoft Exchange 2000 Server sets the incorrect content type for the file. Then, the Web browser uses the content type of the file to determine which program to use to open the file.
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. PrerequisitesBefore you install this hotfix, the following items must be installed on the server: - Microsoft Exchange 2000 Service Pack 3 (SP3).
For additional information about how to obtain the latest service pack for Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base:
301378Â
(http://kbalertz.com/Feedback.aspx?kbNumber=301378/
)
How to obtain the latest Exchange 2000 Server service pack
- The August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup.
For additional information about how to obtain the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup , click the following article number to view the article in the Microsoft Knowledge Base:
870540Â
(http://kbalertz.com/Feedback.aspx?kbNumber=870540/
)
Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup
Restart informationYou do not have to restart your computer after you apply this hotfix. Hotfix replacement informationThis hotfix is not replaced by any later hotfix. Registry informationYou do not have to create or modify any registry keys to use any hotfixes that this package contains. Hotfix file informationThis hotfix contains only those files that are required to correct the issue that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
-------------------------------------------------------------------------
10-Jun-2004 17:38 12,720 Ctrl_calendarview20.htc
10-Jun-2004 17:38 91,631 Ctrl_calendarview20.js
02-Jul-2004 01:59 6.0.6605.0 851,968 Davex.dll
12-Jun-2004 04:27 6.0.6603.0 53,248 Davexpc.dll
12-Jun-2004 04:23 6.0.6603.0 577,536 Dsaccess.dll
12-Jun-2004 03:35 6.0.6603.0 184,320 Dscmsg.dll
12-Jun-2004 04:25 6.0.6603.0 2,179,072 Ese.dll
12-Jun-2004 04:25 6.0.6603.0 40,960 Eseperf.dll
10-Jun-2004 17:42 6,991 Eseperf.hxx
12-Jun-2004 04:25 391,634 Eseperf.ini
01-Aug-2004 23:28 6.0.6603.1 3,596,288 Excdo.dll
12-Jun-2004 04:23 6.0.6603.0 262,144 Exmime.dll
12-Jun-2004 04:27 6.0.6603.0 143,360 Exodbesh.dll
12-Jun-2004 04:27 6.0.6603.0 57,344 Exodbpc.dll
12-Jun-2004 04:27 6.0.6603.0 200,704 Exodbprx.dll
01-Feb-2005 19:30 6.0.6617.42 2,179,072 Exoledb.dll
12-Jun-2004 04:20 6.0.6603.0 81,920 Exosal.dll
12-Jun-2004 04:27 6.0.6603.0 307,200 Exprox.dll
12-Jun-2004 03:36 6.0.6603.0 143,360 Exschema.exe
12-Jun-2004 03:38 6.0.6603.0 675,840 Exwform.dll
12-Jun-2004 03:12 6.0.6603.0 180,224 Exwin32.dll
12-Jun-2004 04:23 6.0.6603.0 40,960 Jcb.dll
12-Jun-2004 03:12 6.0.6603.0 49,152 Mdbevent.dll
12-Jun-2004 03:31 6.0.6603.0 2,293,760 Mdbmsg.dll
12-Jun-2004 03:14 6.0.6603.0 32,768 Mdbrole.dll
12-Jun-2004 03:37 6.0.6603.0 917,504 Mdbsz.dll
12-Jun-2004 04:23 6.0.6603.0 24,576 Mdbtask.dll
10-Nov-2004 08:55 10.145.7329.5 69,632 Spsqfe.exe
09-Nov-2004 22:19 1,250 Spsqfe.inf
12-Jun-2004 04:22 6.0.6603.0 4,673,536 Store.exe
12-Jun-2004 03:38 6.0.6603.0 3,735,552 Wmtemplates.dll
- For additional information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
For additional information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO- Microsoft SharePoint Portal Server 2001
| kbautohotfix kbqfe kbhotfixserver kbshareptportalsvr2001presp4fix kbhotfixrollup kbfix kbbug KB885874 |
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
|
|
 |
|
 |
|
|
|
| |