SharePoint 2007 WSS 3.0 Service Pack 2

Several of my clients have installed SP2 for MOSS 2007. Aside from a glitch which puts the farm in trial mode--which has been fixed before the 180 days expiration--I have heard nothing good or bad about this release.

I did some timings (based solely on logs) on the length of incremental crawls, content deployment, backups, etc. I don't really notice a difference, but I didn't set this up scientifically by keeping the content of my farm static. Quite contrary, I merged a site collection then split another. I also added some new content.

So what are some other stories out there with the success or failure of SP2 for MOSS / WSS?

Please leave comments. I will edit this post if I find any new tidbits.

Comments

Post a Comment

Popular posts from this blog

ADMT fails to migrate SID History

If you ever get the error:
ERR2:7111 Failed to add sid history for auser to auser. RC=1378 

Look on the source domain for membership in a domain localgroup called DOMAIN$$$ where "DOMAIN" is equal to the NetBIOS name of your domain.  Remove the source account from that group and migrate again.
Read more

Exchange 2010 event errors 2601, 2604, 2501

In a recent migration from Exchange 2003/2007 to Exchange 2010, I ran into an issue where I had 2601, 2604, and 2501 errors.


Log Name:      Application
Source:        MSExchange ADAccess
Date:          4/8/2013 12:02:20 PM
Event ID:      2601
Task Category: General
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Exchange10.domain.org
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1268). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account - Error code=8007077f. 
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.


and


Log Name:      Application
Source:        MSExchange ADAccess
Date:          4/8/2013 12:02:20 PM
Event ID:      2604
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     Exchange10.domain.org
Description:
Process MSEXCHANGEADTOPOLOGY (P…
Read more

Robocopy Error 31 A device attached to the system is not functioning

I was migrating Windows file shares to NetApp CIFS shares using Robocopy. I was unable to copy owner information or NTFS Security (/COPY:DATSOU) without getting this Error:

ERROR 31 (0x0000001F) Copying NTFS Security to Destination Directory F:\PATH
A device attached to the system is not functioning.

I thought it may be the zone information on may of these files. I used the Sysintenals Streams utility to remove that information. It did not help.

In the end, I was forced to copy without NTFS information (/COPY:DATU)

When I viewed the properties of any share, folder, or file, the length of time to enumerate and display the permissions was exceedingly slow. I tried disabling anti-virus, etc. In the end, I had to manually re-create the permissions after the initial data copy. File ownership information was lost.

UPDATE: I ran a CHKDSK /F and following a reboot this robocopy functioned fine.


Read more