Sharepoint Server 2007 ve Windows Sharepoint Services 3.0 için karşılaştığınız bir problem ile ilgili Microsoft İletişim Hattı ile temasa geçmeden önce aşağıdaki yayınlanmış olan hotfix’leri incelemenizi tavsiye ediyorum. Bu hotfix’lerin tümü Sharepoint SP1 ile toplu olarak yayınlanacak. SP1 ile bu listede yer almayan bazı bug’lar da düzeltilmiş olacak. Bu bug’lar için bir hotfix yayınlanması planlanmıyor.
MOSS – Potential memory leak within our LDAP security provider when using Forms Authentication.
WSS – Invalid link sent in InfoPath12 Form Server workflow email.
WSS – Tool to rename domain named site (Office Live).
SEARCH – Search does not return files with a space in the filename. The filename property is stored with an encoded %20 instead of a space.
MOSS – User Profile doesn’t get updated from AD.
SEARCH – Managed Property created through OM are being recreated when search crawl happens (full or incremental) (MSAP).
WSS – Response.End() after blob streaming causing performance impact on x64 platform.
SEARCH – Duplicate Best Bets should not be allowed (MSIT).
WSS – Content deployment – The file ‘XXXX’ is not checked out… (DHS).
WSS – CDCR:Tool request to automate site collection repartitions (Office Live).
WSS – NAME.DLL wrong versioning causes crash in IE in OWSSUPP.DLL.
WSS – Special character encoding problem during content deployment in combination with variations.
SEARCH – Modified date in search result is shown as yesterday/tomorrow date.
SEARCH – "View by Modified Date" does not work fine after Incremental Crawl.
WSS – One-Time timer jobs cause 2 hour delay in backup and restore when DST in effect.
MOSS – The kpi creation succeeds and shows kpi with green status if the cell has ‘#NAME?’ because of incorrect formula calculation.
WSS – Attachment for item in content approval enabled List disappears after edited.
WSS – Unable to use ‘e-mail as a link’ feature in WSS 3.0.
SEARCH – Cannot search for anything beyond the first slide of a PowerPoint (ppt) presentation.
SEARCH – Search does not index or return results when DB Status is set offline.
WSS – DocLib with > 1000 folders with unique permissions causes error in sitedata webservice.
WSS – Groups on a higher site level will be deleted when subsite was created by an own template and deleted later.
WSS – Cannot delete a field of type "Computed" from the document library.
SEARCH – Define a scope when using the AdvancedSearchWebPart for entering the parameters and the CoreResultsWebPart to execute the search and display the results.
WSS – Track Passport users by their PUID(Office Live).
WSS – CDCR:Request for external blob storage API (Office Live).
WSS – Non-RFC compliant extra ‘:’ in initial Workflow email causes mail to be interpreted as TEXT on non-Exchange systems.
MOSS – Users unable to create MySite.
SEARCH – Unable to search content of protected charts in Excel.
WSS – Check the canary header in addition to the form body (Office Live).
SEARCH – Lists with a null description are not returned when order determined by description field.
SEARCH – Browser Back button in "Advanced Search" hides search criteria in use (also for the following searches).
SEARCH – The word breaker for Traditional Chinese Names in the CHT version of MOSS is not Correct.
SEARCH – Override DB level permissions by using Readers Fields at the document level.
WSS – Need tool to clean up problem sites caused by the inheriting permissions bug OfficeQFE:18616.
SEARCH – Lag time when starting a crawl increases based on number of documents in system.
WSS – Documents do not maintain ‘modified by’ user information after export/import operation using stsadm.exe.
WSS – Inheriting permission causes destructive error : User can never access to the site collection.
WSS – In AD creation mode, Create User sends email even though check box is unchecked.
WSS – Web Part page Relative URL path is broken and result in "File Not found" unexpectedly.
SEARCH – Search queries intermittently timeout.
WSS – Forefront virus scanner generates error causing document upload to fail.
WSS – Removing user from site collection causes content deployment to fail.
SEARCH – Sites that require forms-based authentication or cookie-based authentication are not crawled in SharePoint Server 2007.
SEARCH – The starting of master merge failed on the AnchorProject and left the indexes marked as being already involved in merge. Subsequent merges do not start.
MOSS – You receive the following error message when you search for a GUID in SharePoint Server 2007: An error occurred while retrieving data from AdventureWorksInstanceBad. Administrators, see the server log for more information.
SEARCH – SharePoint Server 2007 cannot index a Microsoft Exchange public folder.
WSS – Issues that may occur when you use the volume shadow copy service (VSS) reference writer in Windows SharePoint Services 3.0
SEARCH – If you set the Hint property of a Full Text Query object to OptimizeWithFullTextIndex and then query the computer that is running Windows SharePoint Services 3.0, the order of the results is sorted incorrectly.
WSS – Error message when you try to install a feature in Windows SharePoint Services 3.0: "The ‘UserSelectionMode’ attribute is not allowed.
WSS – When you run a program that uses the SPWorkflowManager.ForceDehydrateHttpContextWorkflows() event to work with files that are saved in a Windows SharePoint Services 3.0 document library, the expected Web page is not displayed. Additionally, you receive the following error message: Service Unavailable
WSS – When you upload a file to multiple Windows SharePoint Services 3.0 document libraries, an alert creation e-mail message is sent from the document libraries as expected. However, an alert notification e-mail message is sent from only one document library. You would expect an alert notification e-mail message to be sent from all the document libraries to which you uploaded the file.
WSS – When you use the ItemAdding event to add a new file to a Windows SharePoint Services 3.0 document library, the path of the document library folder cannot be found.
WSS – A file that is attached to an e-mail message is not put in a Windows SharePoint Services 3.0 document library
SEARCH – You browse a Windows SharePoint Services 3.0 Web site that contains different language subwebs. When you search one language subweb for an item that does not exist, you receive an error message as expected in that language subweb. However, when you search for an item that does not exist in a different language subweb, you unexpectedly receive an error message in the first language subweb that you searched.
WSS – You run an SQL query to change the properties for a user that you created on a Windows SharePoint Services 3.0 Web site. When you run the PeoplePicker tool to search for a user, the original user is unexpectedly found. You would expect the PeoplePicker tool to use the changes that you made to the user’s properties when it searches for a user.
WSS – You add two List Web Parts to a page of a Windows SharePoint Services 3.0 Web site. The second List Web Part is connected to receive data from the first List Web Part. When you click the option button for an item in the first List Web Part, only that list item appears in the second List Web Part as expected. However, if you sort the results of the first List Web Part and then click the option button for a different item in the list, all list items unexpectedly appear in the second List Web Part.
WSS – The Web File Properties dialog box displays incorrect properties for a document that is saved in a Windows SharePoint Services 3.0 document library
WSS – A default column value is saved to a document regardless of the content type of the document in a Windows SharePoint Services 3.0 document library
SEARCH – No results are returned in the search results when you search for people by site membership in SharePoint Server 2007
WSS – E-mail alerts do not work when the server that is running Windows SharePoint Services uses port translation.
SEARCH – You cannot search Microsoft Excel workbooks in a Windows SharePoint Services document library.
SEARCH – Users receive search error messages and event ID 10038 error messages are logged in the Application log on Web front-end servers
SEARCH – No documents are returned in the search results when a user searches for Lotus Notes content in SharePoint Server 2007
SEARCH – When SharePoint Server 2007 crawls a Microsoft Exchange Server 2003 public folder, the following error message is logged to the gatherer log: “The item could not be accessed on the remote server because its address has an invalid syntax”
MOSS – When you select the Re-encrypt all credentials by using the new encryption key option to reencrypt credentials in a Single Sign-On (SSO) environment, the "IX_SSO_Credentials" index is renamed to "IX_SSO_Temp_Credentials." When the SSO database is queried, the query fails.
MOSS – A URL that contains an extra slash mark may take longer to open on a server that is running SharePoint Server 2007
SEARCH – Complex remote links are not crawled when the links are in the same SharePoint Server 2007 portal
SEARCH – When you use the FulltextSqlQuery object to perform a full-text search of a server that is running SharePoint Server 2007, the search results may be sorted in random order.
WSS – You cannot disable VSAPI scans when you schedule manual scans of content in SharePoint Server 2007 and in Windows SharePoint Services 3.0
WSS – The file name of a file that you download from the Document Center is changed to use UTF-8 canonical format and is missing the file name extension
WSS – You cannot create a content database after you install Windows Internal Database SP2
MOSS – You run a program that uses the SharedWebService.OnlineServerAddresses Web service to determine the URL for its search service. When several requests are made to the same Web service at the same time, a deadlock situation may occur.
WSS – Previously published pages that are no longer published cause duplicate links to appear in the Windows SharePoint Services 3.0 content database.
WSS – You receive the following error message when you try to open a form in Windows SharePoint Services 3.0: "The Page is modified. Please reopen it"
SEARCH – You cannot crawl case-sensitive Web content in SharePoint Server 2007
WSS – One or more custom programs do not finish successfully when you run multiple custom programs that use the BreakRoleInheritance function in the Windows SharePoint Services 3.0 object model.
WSS – When you try to show an error message in a Windows SharePoint Services 3.0 Web site programmatically by using the ItemCheckingIn() event, the custom error message text is not shown. Instead, you receive a garbled error message that may resemble the following error message: 1!.512s!
WSS – You cannot select the values for a custom field when you try to edit the properties on the FldEditEx.aspx page on a Windows SharePoint Services 3.0 Web site.
SEARCH – You cannot perform a search query after you upgrade to Windows SharePoint Services 3.0 on a Windows Small Business Server 2003-based computer.
SEARCH – When you search a Windows SharePoint Services 3.0 Web site and then click View by Modified Date, you receive the following error message: “Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.”
SEARCH – When you perform an incremental crawl on a Windows SharePoint Services 3.0 Web site, the crawl may stop when one or more of the following conditions are true; No changes are found, No new links are found or No new updates are found.
WSS – Changes that you make to the "List View" Web Part are not retained after you save the site as a template in Windows SharePoint Services 3.0.
WSS – When you try to delete a message in Windows SharePoint Services 3.0 programmatically, you receive a null reference exception message.
WSS – Microsoft Windows SharePoint Services 3.0 currently does not comply with daylight saving time (DST) in Western Australia for the years 2006 to 2009.
SEARCH – If the parent farm contains two or more start addresses that contain the same host in SharePoint Server 2007, efforts to provision the content sources fail.
OUTLOOK – When you locate a Windows SharePoint Services 3.0 custom list in Microsoft Office Outlook 2007, CPU usage that is reported in Task Manager may reach 100 percent. Additionally, CPU usage does not decrease until you exit Outlook 2007.
WSS – When you locate a Windows SharePoint Services 3.0 custom list in Outlook 2007, CPU usage as reported in Task Manager may reach 100%. Additionally, CPU usage does not decrease until you exit Outlook 2007.