Coskun Cavusoglu SharePoint

 Yesterday the SharePoint Team blog posted an announcement on a bug they recently found. It's not that major but it's still something you need to take care of. Jeff Teper, Corporate Vice President, SharePoint says that

The Bug:
"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"

Fix for the Bug:
They say that they will post a new KB article (Currently not active) in the next 2 days that will help you fix this issu.
The work around is to re-enter the Product ID number (PID) on the Convert License Type page in Central Administration.

 Yesterday the SharePoint Team blog posted an announcement on a bug they recently found. It's not that major but it's still something you need to take care of. Jeff Teper, Corporate Vice President, SharePoint says that

The Bug:
"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"

Fix for the Bug:
They say that they will post a new KB article (Currently not active) in the next 2 days that will help you fix this issu.
The work around is to re-enter the Product ID number (PID) on the Convert License Type page in Central Administration.

 If you haven't already you should definitly consider installing Microsoft SQL Server 2005 Service Pack 3, because it provides various updates including updates to how items are fetched using the SharePoint object model. It seems to bring 30 to 50% less latency after the SP3 is installed. Here is the link to the document released by Microsoft that lists all of the new features and improvements that are included in SQL Server 2005 SP3 -  What's New document.

Below is the bit from the document that talks about what they have improved on SSRS with SharePoint integrated mode.
In SharePoint integrated mode, reports typically run slower than the same reports run in native mode. The main cause of this latency can be attributed to SharePoint object model calls that are made. In SQL Server 2005 SP3, the number of SharePoint object model calls that SQL Server 2005 Reporting Services (SSRS) makes are optimized. This optimization reduces some of the latency when you compare report performance with native mode.

 If you haven't already you should definitly consider installing Microsoft SQL Server 2005 Service Pack 3, because it provides various updates including updates to how items are fetched using the SharePoint object model. It seems to bring 30 to 50% less latency after the SP3 is installed. Here is the link to the document released by Microsoft that lists all of the new features and improvements that are included in SQL Server 2005 SP3 -  What's New document.

Below is the bit from the document that talks about what they have improved on SSRS with SharePoint integrated mode.
In SharePoint integrated mode, reports typically run slower than the same reports run in native mode. The main cause of this latency can be attributed to SharePoint object model calls that are made. In SQL Server 2005 SP3, the number of SharePoint object model calls that SQL Server 2005 Reporting Services (SSRS) makes are optimized. This optimization reduces some of the latency when you compare report performance with native mode.