Make sure you test your Content Deployment after installing SP1…

I have been testing WSS/MOSS Service Pack 1 on a large-scale WCM portal for the past couple weeks and I ran into some issues with Content Deployment.  First of all, I do not want to say there’s necessarily a widespread bug with Content Deployment and SP1.  Alright, you are warned 🙂  My goal here is…

7

Central Administration and Alternate Access Mapping (AAM) (issues with Content Deployment and SP1)

A few months ago, I had to debug an issue where Content Deployment was not functioning correctly.  As soon as the Import process was starting, we were either experimenting an HTTP 400 error (Bad Request) or a “…this file type is blocked…” error.  We couldn’t figure out what was going on as everything was functioning…

4

Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. …while installing MOSS SP1

I ran into some issue on a MOSS virtual machine while installing MOSS SP1.  Actually, it was the any SP1 (WSS, MOSS, or one of their Language Pack).  One of my colleague at Orckestra pointed me to a registry setting he had to update while installing a service pack with Team Foundation Server so I…

1

The access control list on 12templatelayoutsweb.config could not be modified when installing 941422

We ran across this while installing the KB941422 hotfix on a brand new farm :   [SPManager] [ERROR] []: The access control list on C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\layouts\web.config could not be modified because the path could not be located in the file system.[SPManager] [ERROR] []:    at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ResetAcl(FileSystemInfo fi, Boolean append)   at Microsoft.SharePoint.Administration.SPServer.ResetAcl(FileSystemInfo fi,…