Come sempre i Service Packs tutti sanno che servono a qualcosa… si pensa solitamente alla soluzione di qualche bug trovato dopo il rilascio del prodotto.
Microsoft ha da qualche mese due SP per SharePoint 2003, uno per i WSS (Windows SharePoint Services) ed uno per SPS (SharePoint Portal Server).
In particolare gli SP1 di cosa si occupano? E’ questa la domanda che mi ha fatto un cliente ieri, menre ero nella sua azienda peruna consulenza, finalizzata alla realizzazione di un’infrastruttura di document management basata su WSS.
La risposta spontanea è solitamente: “Il service pack risolve alcuni problemi e ottimizza le performance di diverse funzionalità, bla bla”… ma, volendo entrare più nel dettaglio, ho recuperato un paio di informazioni in giro (per i dettagli consultare i corrispondenti articoli sulla KB di MS):
“Cannot connect to server at this time. Your list cannot be published.” error message when you import a Microsoft Office Excel 2003 spreadsheet to use as a basis for a new list
Microsoft Internet Explorer stops responding (hangs) when you try to upload multiple documents to a document library [Ed. Chinese and Korean only]
You receive a “List does not exist” error message (sub-area only thus not standard WSS)
The custom list was created in another subarea in Windows SharePoint Services.
“System.OutOfMemoryException” exception in the W3wp.exe process in Windows SharePoint Services
Worker process recycles when you change a recurring meeting request in Windows SharePoint Services
Deadlock condition may occur when you call SPFileCollection.Delete and SPListItem.Update at the same time in Windows SharePoint Services
“The page cannot be found” error message if the path of the document is more than 128 characters in Windows SharePoint Services
Incorrect error codes are returned from SPFileCollection.Delete and SPFileCollection.Update in Windows SharePoint Services
When you set the permissions of your Windows SharePoint Services Web site with a Windows NT domain security group, the Members Web part presence indicator does not appear.
If you create multiple personal views of a document library and then try to export each view to a spreadsheet, you can only export the first view that you created.
When you insert a server-side script to a remote data source on your Web page, accented characters that are contained in the URL are removed.
When you add a file that contains an attachment to a list that is contained in a List template, the attachment file is added to the list.
This issue occurs even if you clicked to clear the Include content check box when you created the List template.
When you copy a file to a document library that uses a quota template, the file is copied to the portal site. Additionally, you do not receive a warning message if the quota for the portal has been exceeded.
When you try to sort the values that are contained in the master Web part that is connected to a second Web part on a different Web page in the portal, the values are not sorted, and the Web page that contains the second Web part is opened.
When you try to export the data from a Web part that contains accented characters in the URL, the data is not exported, and you receive the following error message:
‘The requested Web Part could not be found or has been deleted from this page by another user or in another session since the page was last refreshed.’
When you try to provision a Windows SharePoint Services portal or to open the home page of the portal in Microsoft Internet Explorer, you receive the following error message:
‘Microsoft Internet Information Services has encountered a problem and needs to close. We are sorry for the inconvenience.
To see what data this error report contains, click here.’
After you convert a List View Web part that is contained in a document library to Extensible Stylesheet Language Transformation (XSLT) Data View and then change the regional options of your portal to a different language, the format of the numbers may appear incorrectly in the list. For example, the number 11.11 may appear as 1,111,000,000,000.
When a Microsoft SharePoint Portal Server (SPS) crawls a Windows SharePoint Services (WSS) site, error message 0x80042613 is logged in the SPS Gather log, and the site is not indexed. This issue may occur when a role is removed from the SPS site and when an invalid site role security identifier (SID) remains in the Access Control List (ACL).
You cannot specify alternate text for an image when you add an Image Web Part
When you click a list item after you remove a filter from the view, the image for that list item is not displayed, and then you receive a “No image available” error message
The value of the Turkish Lira is not displayed in the old TL format and in the new YTL format. (Fix only for Turkish and English versions of WSS)
The Stsadm.exe command-line tool incorrectly reports that the restore operation was completed successfully
A blank, white page is displayed in your Web browser when you attach a document to an announcement
You cannot delete a Windows SharePoint Services Web site that contains more than 2 gigabytes of data
No option to update a user’s logon name in Windows SharePoint Services after you make changes to the user account properties in Active Directory directory service
Performance of Windows SharePoint Services may decrease in certain environments when you enable usage analysis processing
E-mail notifications display the name of the user who deleted a document in a document library as “Unknown”
Multiple versions of a document are listed after you copy a document to the document library in Explorer view or by using Web folders (and multiple e-mail notifications are generated).
Users intermittently cannot access the portal site for periods of time
The status of Microsoft Office documents in a document library incorrectly appears as “Pending” after you restore a Windows SharePoint Services Web site from backup
891512 (WSS in SPS 2003 only)
After XSLT Data View conversion “The user information link of list items do not connect you to the public view of the My Site personal site of the user as expected.”
Users can still add content to a Web site in Windows SharePoint Services even after the storage quota limit for the Web site collection is reached
You receive a “The user does not exist.” error message when you try to delete a user from the Web site collection.
(“This problem occurs if the logon name of the user in Active Directory directory service contains one or more single straight quotation mark characters (‘)”. e.g. O’Reilly)