Approve and Reject buttons do not appear on a page for Approvers

I came upon that little bug the other where Approvers couldn’t see the Approve and Reject buttons on a page (that was waiting for approval).  The setup is the following: Active Directory (2003) users The users are part of a global security group in Active Directory The Active Directory group is part of the Approvers…

0

Required firewall ports for importing Active Directory profiles with MOSS

In very secure environments, your Active Directories may not be completely available to your MOSS machine, especially if you have AD trusts involved.  I had a particular case where MOSS was installed in a Win2k3 forest that trusts a very secure Win2k forest “one way”.  What I mean by very secure is that MOSS only…

3

Incremental content deployment completes successfully with errors mentioning that the name is already is used

I often get the question as to why we have this error when using an incremental Content Deployment:  The specified file is already in used.   Simply, that message appears if the authors have created a file, deleted it, and recreated another file with the same name.  All that before a single incremental content deployment…

3

Content Deployment does not fix links (at import) when the source has been deployed with features

I ran into this last week when making a spot check on the “content deployment destination”, the links and images that were supplied by authors in the Publishing Html fields were still pointing at the “source”.  It turns out that Content Deployment doesn’t work correctly when using features.   Here’s a quick rundown of the…

2

Slow Content Deployment transportation / TCP connection was forcibly closed

We were having issues with slow Content Deployment for the transporting phase and it was sometimes failing with this error: Publishing: Content deployment job failed. Error: ‘System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed…

2

BlobCache woes, how to work (clean) correctly with it, and what to expect when using it with SharePoint features

I ran into an issue with BlobCache lately where it was sending incorrect Http headers.  Basically, all files were sending 2 http headers: Exires : (15 days behind) cache-control: private, max-age=0   Yes, “exires”, not “expires”, so not only we have a bug but also a typo 🙂  Anyway, this was ensuring that all static…

1