Could not save the list changes to the server. This list cannot be deleted.

When SharePoint 2010 list becomes unavailable to delete.

error message: Could not save the list changes to the server. This list cannot be deleted.

solution: run powershell command as administrator type-in the ff:

$web = Get-SPWeb http://yourserver
$list = $web.Lists["MyList"]
$list.AllowDeletion = $True
$list.Update()

Now go to your list settings again and you'll see the delete command or you can just run the line below:

$list.Delete()

hope that helps!

saving it is not permitted because the changes you have made require the listed tables to be dropped and re-created.

Problem: Saving always warns you that it is not permitted because the changes you have made require the listed tables to be dropped and re-created.

Solution: In SQL Management menu go to Tools menu, click Options, expand Designers, and then click Table and Database Designers. Select or clear the Prevent saving changes that require the table to be re-created check box.

Cheers!

How to enable developer dashboard

This is will display helpful information regarding the call stack, database query times, exception information in error messages, and loading events for web parts during page rendering and will appear at the bottom page view.

stsadm -o setproperty -pn developer-dashboard -pv OnDemand (Recommended Setting)
stsadm -o setproperty -pn developer-dashboard -pv on
stsadm -o setproperty -pn developer-dashboard -pv off

It can be enabled via STSADM or PowerShell.
The property value set OnDemand will provides you the ability to toggle the dashboard on and off.

How to add role DC using Windows Server 2008 R2

been lazy to write an article about creating a DC role in win2008R2 so here is a helpful link with step by step snapshot of actual installations:

Running Windows Server 2008 R2 Installing DC

Dreaded 503 After SP2010 Installation

after a 'successful installation of SP2010' application pool for 'Central Administration v4.0 is stopping due to WAS error: 5059, this happen when a domain group policy is implemented. There are tons of solutions you can easily found by googling this error and probably would suggest editing of applicationhost.config or even adding of service account in 'login as batch', however these might or might not solve your issue.

Specially when you don't have the privileged to edit the GPO or even the local policy is locked because the 'Domain Group Policy' supersede the local policy.

Note: I used my standard domain account that has full privileged to both SQL Server and Local Server.

Changing Application Pool Identity to Network Service will run OK but will encounter Database connection failure, even if you give the identity dbcreator or sysadmin server role.

To make the story short:

Solution that works for me is to use local account in the SP configuration(I wouldn't advice this unless for testing purposes only). Yeah I was aware that local account is for stand alone only and SP GUI wouldn't allow local account to be used as Database Access, but there is a clever workaround here.

POWERSHELL is you friend!

After installing SharePoint 2010 do not run the Config wizard yet. make sure that there are no created SharePoint Admin and Config database, if so just delete it and application pools as well.

Note:

Run the "SharePoint 2010 Management Shell" by using Administrator rights. Click the Icon and select 'run as administrator', otherwise you'll encounter registry write error. Don't make me say I told you so! :P

Type and execute the command below:

PS> C:\Users\ New-SPConfigurationDatabase

cmdlet New-SPConfigurationDatabase at command pipeline position 1
Supply value for the following parameters:
DatabaseName: SharePoint_Config
DatabaseServer:
FarmCredentials
Passphrase:
-

after a successful creations of SharePoint Admin and Config databases. Run the SharePoint Confguration GUI wizard again and connect the created databases.


Update: 4/29/2011

THIS WILL WORK ONLY IF YOU'LL USE LOCAL ACCOUNTS (Farm and Complete installations)

For real solutions is to add ISS_IUSRS in 'logon as batch' when
global policy is implemented.

For reference:

Sharepoint 2010 'Missing Dependencies' error

Sharepoint 2010 Problems and Solutions

Error: After a fresh installation of Sharepoint 2010 you will notice this error under configuration stating 'Missing Dependencies' etc.

Solution: To remove this error just simply browse these pages.

SearchAdministration.aspx
SearchFarmDashboard.aspx

In Central Administration
go to General Application Settings -> Farm Search Administration -> Search Service Application.

On the upper left corner or side menu, under 'Administration Section' just click and b browse 'Search Administration' and 'Farm Search Administration'

go back and click the issue report again and run the 'Reanalyze Now"

and waaalah! (the error should disappear in the health analyzer report).

another solution is by just enabling the search services.

Sharepoint 2010 Igniter

got the privilege to attend Sharepoint 2010 Ignite Training for Developers in CED-IT cebu, Philippines. Hopefully I could blog partially the impressions later on. excited? horaa..take a breath.

Awesome Experience with the GURU's of SP

Free eBooks you @ SharingThePointAsia2011 Rocks!!!SharingThePointAsia2011

SCripts For Sharepoint Farms and Services Apps

MS STPASIA event

Paul Swider Development Strategies

Sharepoint Blank

Sharepoint 2010 Virtual Lab

for those who can't mess around Sharepoint 2010 'cause of system requirements limitation such as 64bit, 4G/8G, etc.. check this link out:

Sharepoint Virtual Lab

whaala! enjoy!