To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

1. Stop the Timer service. To do this, follow these steps: a. Click Start, point to Administrative Tools, and then click Services. b. Right-click Windows SharePoint Services Timer, and then click Stop. c. Close the Services console.
2. On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
3. In Windows Explorer, locate and then double-click the following folder: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUIDNotes o The Drive placeholder specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C. o The GUID placeholder specifies the GUID folder. o The Application Data folder may be hidden. To view the hidden folder, follow these steps: 1. On the Tools menu, click Folder Options. 2. Click the View tab. 3. In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.o In Windows Server 2008, the configuration cache is in the following location: Drive:\ProgramData\Microsoft\SharePoint\Config\GUID
4. Back up the Cache.ini file.
5. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt. Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
6. Double-click the Cache.ini file.
7. On the Edit menu, click Select All.
8. On the Edit menu, click Delete.
9. Type 1, and then click Save on the File menu.
10. On the File menu, click Exit.
11. Start the Timer service. To do this, follow these steps: . Click Start, point to Administrative Tools, and then click Services. a. Right-click Windows SharePoint Services Timer, and then click Start. b. Close the Services console. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
12. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
13. Click Start, point to Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
14. Click the Operations tab, and then click Timer job status under Global Configuration.
15. In the list of timer jobs, verify that the status of the Config Refresh entry is Succeeded. This may show “Aborted” as the status. Ignore this and check in 10 mins (you can tell if the process has completed successfully on each server that displays “aborted” by the CPU utilization (when the timer job is reconfiguring the CPU will be at 100%).
16. On the File menu, click Close.

You still may run into this error when deleting the web applicaton that has no content database (DBA accidently deleted it). Just deselect the “delete database” option in the Central Admin when deleting the database and you should be able to remove the web application.

With this simple solution you can arrange it on every single page of your choice.

1. Site Settings > Edit Page
2. Add a Content Editor Web Part anywhere in the page.
3. Open tool pane of Content Editor Web Part by clicking “Modify Shared Web Part” option from top right drop down of web part.
4. Click on “Source Editor” button inside tool-pane and in “Text Entry” window paste the following lines.

<style>
.ms-navframe{
display:none;
}
</style>

<style>
.ms-recyclebin {
display:none;
}
</style>

<style>
.ms-quicklaunchheader{
display:none;
}
</style>

5. Click Save
6. Expand Layout section inside toolpane.
7. Check the Hidden checkbox and click OK.

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled. ( HttpStatusCode Unauthorized The request failed with HTTP status 401: Unauthorized. )

After some searching, I found the solution:

So you need to disable the LoopBackRequest in registry. To do this, just follow my instructions:

1. Go to command window and type regedit.exe
2. Once opened the registry editor, just navigate to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa”
3. Right click on “Lsa” and create a new 32bit DWORD value
4. Rename it as “DisableLoopbackCheck” (Note: you cannot rename it actually. so, once created the DWORD value, directly paste/type as “DisableLoopbackCheck”.
5. Then again modify the value of “DisableLoopbackCheck” as “1″
6. Close the registry editor.
7. Now start to crawl the content.

1. Open up your sites web.config, and make the standard custom errors edit.  You want it to be  < customerrors mode=”Off”/>
2. Then, search for the CallStack=”False” and change it to CallStack=”True”, you should find this in the “<safemode>” node.

Voila, your error message will be more detailed.

Add-PSSnapin Microsoft.SharePoint.PowerShell –erroraction SilentlyContinue

## setup our output directory
$dirName = “c:\wspexport”

Write-Host Exporting solutions to $dirName
foreach ($solution in Get-SPSolution)
{
$id = $Solution.SolutionID
$title = $Solution.Name
$filename = $Solution.SolutionFile.Name

Write-Host “Exporting ‘$title’ to …\$filename” -nonewline
try {
$solution.SolutionFile.SaveAs(“$dirName\$filename”)
Write-Host ” – done” -foreground green
}
catch
{
Write-Host ” – error : $_” -foreground red
}
}

FAST Search Server 2010 for SharePoint Add or Remove an Index Column
Microsoft System Center Configuration Pack for Microsoft Office SharePoint Server 2007 Service Pack 2
System Center Operations Manager 2012 Release Candidate
Security Update for Microsoft SharePoint Server 2010 (KB2553132)
Active Directory Rights Management Services at Microsoft
Microsoft SharePoint Server 2010 Technical Library in Compiled Help format
Microsoft SharePoint Foundation 2010 Technical Library in Compiled Help format
Microsoft Search Server 2010 Technical Library in Compiled Help format
Microsoft FAST Search Server 2010 for SharePoint Technical Library in Compiled Help format
Update for Windows SharePoint Services 2.0 (KB2596977)

Server Administrator for SharePoint gives you maximum insight into your SharePoint server and farm configuration and customizations to optimize manageability, performance, availability and security. 

• Server Reporter – Gain insight into SharePoint and its underlying platforms including hardware, Windows, SQL Server, IIS, .Net, asp.net, WSS, MOSS, Search and Excel with reports on their current configuration. Also compare settings and configurations between servers and farms to identify disparities.
• Risk Locator (see screenshot below) – Know what configurations, settings and customizations are affecting the availability, security, performance and manageability of your SharePoint environment. Identify risks based on best practices with ratings (critical, high, medium and low) so you understand the severity of each risk and can take appropriate action.
• Configuration Advisor – Analyze the configuration of your entire SharePoint environment and view reports on best practice violations, server health, performance and security issues. Reports explain each issue in detail along with recommendations to resolve them, ensuring optimum availability, security, performance and manageability.
• Rule Maker – Create your own best practice rules for availability, security, performance and manageability in your environment using PowerGUI to build PowerShell scripts that can be loaded into the main product.
• Discover – Understand your SharePoint environment by identifying all SharePoint server configurations, settings and customizations across your network and explore details using the tree view within the console.
• Upgrade Checker –Be sure your existing SharePoint 2007 environment is ready to upgrade to SharePoint 2010. The built-in graphical reports show what is ready to upgrade and what is not across all SharePoint farms, along with a rating so you know what’s critical to correct before you make your move to SharePoint 2010.
• Support for SharePoint 2007 and 2010 Technologies – Supports Microsoft Office SharePoint Server (MOSS), Windows SharePoint Services v3 (WSS v3), SharePoint 2010 and SharePoint Foundation 2010.

Download Server Administrator for SharePoint freeware today here (registration required!): http://communities.quest.com/community/sharepointforall/management/server-administrator

More info about this gift: here

Because there is still much use of SharePoint 2007, I added not only the best practices for SharePoint 2010, but also those of SharePoint 2007

SharePoint Server 2010:
http://technet.microsoft.com/en-us/sharepoint/hh189420 

SharePoint Server 2007:
http://technet.microsoft.com/en-us/office/sharepointserver/bb736746