You may have read that there was an issue with the previously released version of the WSS August CU. Well, Microsoft has now released a new version of the update that appears to not have the same problem.
You can find all the information here: http://blogs.msdn.com/joerg_sinemus/archive/2009/10/01/new-build-available-for-august-cu.aspx
There is a very useful post by Penny Coventry, author of Office SharePoint Designer 2007 Step By Step, on the books website. It allows you to translate the SharePoint version number to the actual patches that have been applied.
Thanks Penny!
You may have heard that the WSS 3.0 and MOSS 2007 August CU is now available. It is, and can be found here:
WSS:
973400 The full server package for WSS
http://support.microsoft.com/default.aspx?scid=kb;EN-US;973400
MOSS:
973399 The full server package for MOSS
http://support.microsoft.com/default.aspx?scid=kb;EN-US;973399
However, there is an issue with the update that causes you not to be able to attach databases of earlier versions. This means that if you are doing an upgrade or server migration you should not install this update on the destination server unless it has already been applied to the incoming content databases.
Microsoft’s current solution is as follows:
If you are running SharePoint Server 2007 or WSS 3.0 on Windows Server 2003 SP1 or later you will run into authentication issues if you are trying to access a SharePoint site using host headers from the server itself (i.e. host file has portal.mydomain.com pointed to 127.0.0.1). This issue manifests itself as the result of a loop back security check that Microsoft built in to Windows Server 2003 SP1 and later. The purpose of the loopback check is to eliminate denial of service attacks however it causes issues with access SharePoint sites locally from the server. In a typical production environment this is typically not a problem since you rarely access SharePoint sites (besides central admin) from a front end web server itself.
You can read the detailed KB article at http://support.microsoft.com/kb/926642 & http://support.microsoft.com/kb/896861.
Here is a rundown of how to fix the problem. I typically disable the loopback check in development scenarios; however, this is not recommended for production server environments.
Method 1: Disable the authentication loopback check
Re-enable the behavior that exists in Windows Server 2003 by setting the DisableLoopbackCheck registry entry in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry subkey to 1. To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.
Note: You must restart the server for this change to take effect. By default, loopback check functionality is turned on in Windows Server 2003 SP1, and the DisableLoopbackCheck registry entry is set to 0 (zero). The security is reduced when you disable the authentication loopback check, and you open the Windows Server 2003 server for man-in-the-middle (MITM) attacks on NTLM.
Method 2: Create the Local Security Authority host names that can be referenced in an NTLM authentication request
To do this, follow these steps for all the nodes on the client computer:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
3. Right-click MSV1_0, point to New, and then click Multi-String Value.
4. In the Name column, type BackConnectionHostNames, and then press ENTER.
5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.
Note: Type each host name on a separate line.
Note: If the BackConnectionHostNames registry entry exists as a REG_DWORD type, you have to delete the BackConnectionHostNames registry entry.
7. Exit Registry Editor, and then restart the computer.
I was combing through the event logs on a server I set up recently when I ran across an Warning event occurring exactly every hour.
|
After much research to no avail I had almost given up and decided it didn’t actually matter as there was nothing in the SSP that I actually needed to search. However, it finally dawned on me that the issue was that there was no root site for the SSP Web Application, just the /ssp/admin. I created an empty root and the issue immediately went away.
Also, I slept much better knowing that my event logs were nice and clean. :-)
This is a test with Microsoft’s offline blog editing tool Windows Live Writer.
I do not like blogspot’s online editor and, working at a Microsoft Gold Partner, figured I would see what Microsoft has to offer.
So, here we go….
There are times we want to manage Web parts on a SharePoint page but could not use "Edit Page" option, such as unhandled exception occurs in code and an error page is shown. In this case we normally use the Web part management page. SharePoint usually provides this link on the error page, but sometimes doesn't. So remembering the page will be helpful.
This is an application page called SPContnt.aspx. It takes one parameter url in the query string. So It would look something like
http://server/site/_layouts/spcontnt.aspx?url=http://server/site/default.aspx
This brings you to a page that will allow you to Close, Reset, and Delete Web Parts from the page.
