Antivirus scanning exclusions for WSS / SharePoint on Windows 2008 / R2

Microsoft’s KB952167 (Folders may have to be excluded from antivirus scanning when you use a file-level antivirus program in Windows SharePoint Services 3.0 or in SharePoint Server 2007) provides information on files & folders that need to be excluded by antivirus scanning. However, this article contains references to Windows 2003 paths, which are different from Windows 2008 paths.

Here is a list of paths I have created for Windows 2003 and Windows 2008 / R2:

 

Windows 2003	Windows 2008
C:\Program Files\Common Files\Microsoft Shared\Web Service Extensions\	C:\Program Files\Common Files\Microsoft Shared\Web Service Extensions\
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\	C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\	C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\
C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\	C:\ProgramData\Microsoft\SharePoint\Config\
C:\Windows\Temp\WebTempDir	C:\Windows\Temp\WebTempDir
C:\Documents and Settings\MOSSFarmService\Local Settings\Temp\	C:\Users\MOSSFarmService\AppData\Local\Temp\
C:\WINDOWS\system32\LogFiles	C:\WINDOWS\system32\LogFiles
C:\Documents and Settings\Default User\Local Settings\Temp	C:\Users\Default\AppData\Local\Temp
C:\Documents and Settings\MOSSFarmService\Local Settings\Application Data	C:\Users\MOSSFarmService\AppData
C:\Documents and Settings\MOSSFarmService\Local Settings\Temp	C:\Users\MOSSFarmService\AppData\Local\Temp
C:\Documents and Settings\SPSSPAppPool\Local Settings\Application Data	C:\Users\SPSSPAppPool\AppData
C:\Documents and Settings\SPSSPAppPool\Local Settings\Temp	C:\Users\SPSSPAppPool\AppData\Local\Temp
C:\Documents and Settings\SPAppPool1\Local Settings\Application Data	C:\Users\SPAppPool1\AppData
C:\Documents and Settings\SPAppPool1\Local Settings\Temp	C:\Users\SPAppPool1\AppData\Local\Temp
C:\Documents and Settings\sqlsrv\Local Settings\Application Data	C:\Users\sqlsrv\AppData
C:\Documents and Settings\sqlsrv\Local Settings\Temp	C:\Users\sqlsrv\AppData\Local\Temp
C:\Documents and Settings\SPCAAppPool\Local Settings\Application Data	C:\Users\SPCAAppPool\AppData
C:\Documents and Settings\SPCAAppPool\Local Settings\Temp	C:\Users\SPCAAppPool\AppData\Local\Temp
C:\Program Files\Microsoft Office Servers\12.0\Data	C:\Program Files\Microsoft Office Servers\12.0\Data
C:\Program Files\Microsoft Office Servers\12.0\Logs	C:\Program Files\Microsoft Office Servers\12.0\Logs
C:\Program Files\Microsoft Office Servers\12.0\Bin	C:\Program Files\Microsoft Office Servers\12.0\Bin
C:\Windows\Temp	C:\Windows\Temp

Post-SP2 updates for SharePoint 2007 released

Microsoft has released the bi-monthly (June ‘09) Cumulative Updates for MOSS and WSS3.0.

Fixes for MOSS

Notes: An “uber-package” for MOSS has not been released yet. Either install all MOSS fixes or wait for the single-install package. “Language specific” fixes have to be installed for each language installed on your system.

KB972569 Global http://support.microsoft.com/default.aspx?scid=kb;EN-US;972569

Issues resolved: In Microsoft Office SharePoint Server 2007, you start an out-of-the-box approval workflow and set a due date. As soon as the due date passes, you edit the workflow and then delete the due date. Immediately a task overdue e-mail is sent out to the approvers with the original due date. The approvers continue to receive a task overdue e-mail (referencing the original due date) weekly until the workflow is canceled, a future due date is set or the workflow is approved.

 

KB970948 Global http://support.microsoft.com/default.aspx?scid=kb;EN-US;970948

Issues resolved: When you try to a create a Key performance indicator (KPI) item by using the "Indicator Using data in Excel Workbook" option and the Excel workbook has Unicode characters, you receive a "File not found" error message. When you click a link to a Report Center Dashboard page in your My Site page, you receive the following error message:  An unexpected error has occurred. When you use the spelling checker on words that do not include accented characters, the spelling checker does not suggest corrected words to include the accented characters. For example, you use the spelling checker to check the spelling of "telefono" in Spanish, and it results in no suggestions. The correct suggestion should be "teléfono" to include the accented "é." If you enable binary large object caching on a site collection intermittently you receive "File not found" errors when you open already cached files during the BLOBCache automatic background cleanup procedure. After you install this update, the probability of "File not found" errors caused by this race condition is minimal. If you copy some text into a Rich Text Edit control in Internet Explorer 8, click Save as in the File menu, and then click Cancel, you find that the text is pushed down the page. After you install this update, you can use the RichTextEditorShortcutEnabled property to control all rich text edit boxes. This includesthe AboutMe rich text edit box in My Site. For example: stsadm.exe -o setproperty -url http://portal/MySiteURL -pn "richtexteditorshortcutenabled" -pv "no" A federated search location can be configured to use "Common Cookie Authentication." However when this location is used on a site through the Federated Search Results Web part, the Web part is not shown. You use UserA account to create a page and then click Check In to Share Draft. Then, you delete the UserA account. After that, if you change to the All Draft Documents in the Manage Content and Structure page, you receive the following error message:  Unknown Error A search alert is added to inform you of any new results for a particular query term. However, after crawling a content source that contains many changed or new documents by using that query term, you find that the resulting alert e-mail only contains results for 10 of these newly crawled documents. You are never notified of the other document

 

KB970947 Language specific http://support.microsoft.com/default.aspx?scid=kb;EN-US;970947

Issues resolved: Consider the following scenario: You copy text that contains smart tags from a document that is created in Microsoft Office Word 2007 or an earlier version of Word. You paste the text into a Content Editor Web part in Microsoft Office SharePoint Server 2007. You use the Remove Inline Styles feature to remove the inline styles. In this scenario, the text that is associated with the smart tags is removed

 

KB972562 Language specific http://support.microsoft.com/default.aspx?scid=kb;EN-US;972562

Issues resolved: In a slide library, you have a slide that contains more than two commas in the file name. When you click Copy Slide to Presentation, PowerPoint 2007 does not start. Additionally, there is no error message.

 

KB972564 Forms Server Global http://support.microsoft.com/default.aspx?scid=kb;EN-US;972564

Issues resolved:  Consider the following scenario. You use Microsoft Office SharePoint Server 2007. You design an InfoPath form that contains an ordinary rich text control and a read-only rich text control. The controls are linked to the same data source. You enter text that represents a URL to the ordinary control. The read-only control is updated with the same content. You open the form by using SharePoint, and notice that the URL in the read-only control is also hyperlinked. You click the link in the read-only control. In this scenario, the Web page that the URL points to is open in the control instead of in a new Internet Explorer window. Note This problem does not occur in the ordinary control.

Fixes for WSS

Notes: no information about the actual fixes has been released yet

KB971538 uber package


http://support.microsoft.com/default.aspx?scid=kb;EN-US;971538

KB970946 Global


http://support.microsoft.com/default.aspx?scid=kb;EN-US;970946

Source: MSDN Blogs

Fix released for SharePoint SP2 Trial License Conversion

As we  reported before, Service Pack 2 of Microsoft Office SharePoint Server 2007 converts the license to a 180-day trial installation.

Microsoft has just released a fix for this problem; the fix resolves the problem that causes Office Server products to expire 180 days after Service Pack 2 is installed.

Update for 2007 Microsoft Office Servers (KB971620), 32-Bit Edition

Download the Download the Update for 2007 Microsoft Office Servers (KB971620), 32-Bit Edition package now.

Update for 2007 Microsoft Office Servers (KB971620), 64-Bit Edition

Download the Download the Update for 2007 Microsoft Office Servers (KB971620), 64-Bit Edition package now.

For information about how to deploy this update, please see the Microsoft TechNet article on deploying server updates: http://technet.microsoft.com/en-us/library/cc263467.aspx.

This update applies to the following products:

• Microsoft Office SharePoint Server 2007
• Microsoft Office Project Server 2007
• Microsoft Search Server 2008
• Microsoft Search Server 2008 Express
• Microsoft Office Forms Server 2007

Source: Microsoft Download Center

Interactive Stsadm Technical Reference for SharePoint Server 2007

Microsoft Office SharePoint Server 2007 includes the Stsadm tool for command-line administration of SharePoint Server 2007 servers and sites.

Microsoft has just released an interactive STSADM application that lets you easily browse & search through STSADM commands and options. Continue to Technet to use the interactive application (based on Silverlight).

Source: Technet

Technorati Tags: microsoft,sharepoint,stsadm

(Updated) SharePoint SP2 converts license to Trial!!!

During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users.

We are working to release a hotfix to automatically fix this issue. A manual work-around is currently available and involves customers re-entering their Product ID number (PID) on the Convert License Type page in Central Administration.  For more information and detailed steps please read this KB article. (The KB link is not currently active, it will be available within the next 48hrs)

Update: Microsoft has released a hotfix that resolves this issue. More information and download links can be found here.

Source: MSDN Blogs

New Microsoft SharePoint site at microsoft.com, based on MOSS 2007

Lights… Camera… Action!

Today, we launched the SharePoint marketing website on SharePoint Server 2007.  First the home page, it is brand new and we’re using Silverlight enabled web parts to keep the interface simple, elegant and dynamic thus enhancing the overall usability of it.  You can watch customer videos, learn about events, download trial versions of the software and a lot more on the home page now.  Since the site is powered by MOSS, we are taking advantage of the publishing feature and list driven content.

Visit the new site at http://sharepoint.microsoft.com

Source: SharePoint on SharePoint: Launch of new website

Installation of Infrastructure Update for Microsoft Office Servers fails if GroupBoard Workspace 2007 is installed

After applying the Infrastructure update on a MOSS 2007 Server with 'GroupBoard Workspace 2007' installed the 'SharePoint Products and Technologies Configuration Wizard' would fail at step 2, with the following error messages logged in the Event Viewer:

The schema version (3.1.3.0) of the database v3_MOSS_SPSUPGRADE_PORTAL_80_CONTENT on VM-SQL\SQL2005 is not consistent with the expected database schema version (3.1.5.0) on SPSUPGRADE. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.

Database 'SharePoint_AdminContent_9ff3db24-91c8-4b79-9d71-9a8b0e0323bf' on SQL Server instance 'VM-SQL\SQL2005' is not empty and does not match current database schema.

Failed to initiate the upgrade sequence.
Failed to upgrade SharePoint Products and Technologies. Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_9ff3db24-91c8-4b79-9d71-9a8b0e0323bf Parent=SPDatabaseServiceInstance Name=SQL2005 has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_9ff3db24-91c8-4b79-9d71-9a8b0e0323bf Parent=SPDatabaseServiceInstance Name=SQL2005 has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)
at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Workaround:
Uninstall 'GroupBoard Workspace 2007' and re-run the 'SharePoint Products and Technologies Configuration Wizard'.

More information:
http://support.microsoft.com/?id=941678 (The SharePoint Products and Technologies Configuration Wizard does not finish successfully on a computer that also has GroupBoard Workspace 2007 installed)