I have nearly 20% free space in my development VM

SharePoint 2010 is complaining about drives running out of space and also listed as critical error.

I don’t know why this nagging error is displayed at home page of the central admin. But I figured out to clear out the error temporarily. 

Go to central admin –> monitoring

click review rule definition

Select the check box and click the edit button from the ribbon.

 

uncheck the enabled option.

Go to the health reports and clear out the error.

Select the checkbox and delete it from ribbon.

 

My system Configuration: Intel Xeon Processor 64 bit with Windows 2008 R2.

When I try to install SQL server 2008, the following error message was displayed.

Then I realized that, only SQL Server 2008 SP1 can be installed on Windows 2008 R2.

Download SQL Server 2008 SP1, and follow the method mentioned in this article to slipstream SQL Server 2008 SP1

Note: If you want to use the SQL server 2008 with SharePoint 2010, you also need CU2 for Sp1 which can be found here (http://support.microsoft.com/kb/970315)

Select “Run Program” and rest of the screen shots are self explanatory.

select installations and then select SQL server Standalone edition.

 

Enter Product Key and Accept License Agreement.

Then install setup support files…

 

Fix any issues..

Select the required components from the next screen.

Select the location for SQL server files

Select an account name for each service. you can also use the button at the bottom of the screen to assign one account for all the services. It is easy some time to use local system account.

Select the authentication method and assign at least one administrator to the server.

On the FILESTREAM tab of the Database Engine Configuration page, select the
options for Enable FILESTREAM for Transact-SQL access and Enable FILESTREAM
for file I/O streaming access. FILESTREAM can also be enabled later, if you don’t know whether this option is required or not.

 

On the Analysis Services Configuration page, specify an administrator as an
Analysis Services administrator by clicking the Add Current User button at the bottom
of the page

 

Select the Install the native mode default configuration on reporting services configuration section. The report server will be usable after the configuration.

Now you are ready to install and make sure the slipstream is defined properly as shown below.

If everything goes well, you should see success screen as shown below.

Pre-register today and get notified when SharePoint 2010 Beta becomes available in November. ​ Follow the link to pre-register http://sharepoint2010.microsoft.com/try-it/Pages/Trial.aspx

 

Also Microsoft just released documents (Visio files) about SharePoint 2010 System requirements and upgrade process (from SharePoint 2007).

Microsoft SharePoint Server 2010 Upgrade Planning

It includes

• Upgrade requirements
• Hardware, operating system, and database Upgrade process
• Specific steps to follow before, during, and after the upgrade

 

Microsoft SharePoint Server 2010 Upgrade Approaches

It helps you understand the in-place, database attach, and hybrid approaches to upgrading from Office SharePoint Server 2007 to SharePoint Server 2010

 

Microsoft SharePoint Server 2010 — Services Upgrade

It covers the unique issues of upgrading services by using either the in-place or database attach approach are discussed.

 

Microsoft SharePoint Server 2010 — Test Your Upgrade Process

It explains the methodology for testing the upgrade process before upgrading from Office SharePoint Server 2007 to SharePoint Server 2010.

How to: Create an Event Handler Feature with VSeWSS1.3

Prerequisites:

Read the following to understand about Event model and Feature in SharePoint.

· Event Fundamentals

· Working with Features

· Solutions Overview

Software Environment:

· VM with MOSS 2007 SP2

· Visual Studio 2008 Professional

· VSeWss 1.3

Object Model:

SharePoint Object Model exposes several event classes inherited from Microsoft.SharePoint assembly. There are four important classes:

· SPItemEventReceiver Class

· SPListEventReceiver Class

· SPWebEventReceiver Class

· SPFeatureReceiver Class

Building the Feature:

It shows how to add a simple event handler that prevents items from being added to a list. Two procedures are involved in this task:

· Creating an event handler in Microsoft Visual Studio

· Adding the event handler as a Feature in Windows SharePoint Services

1. Create a new project in Visual Studio by clicking File, pointing to New, and then clicking Project.

Select Empty project from the SharePoint template list and give a name to the project

2. Select GAC from the Trust Level ( Event Handlers must be deployed only in GAC)

3. In Solution explorer, Right click on the project, and Add a new Item to the project

Select SharePoint category and select the ‘event receiver’ template.

Select ‘Document Library’ from the list

4. This would have created set of files for ItemEventReceiver and ListEventReceiver, as shown below. Depending on the situation you can delete either one of the EventReceiver.

5. Open the ItemEventReceiver.cs file and add code to the ItemAdding event as shown below. The code will prevent adding new item to the list.

6. Similarly add code to the ListEventReceiver as shown below. The sample code will prevent adding new column to the list.

7. Select Project Properties and enter the URL location of website where you want to deploy the EventReceiver.

8. Next step is to create solution to deploy these two Features. Click on ‘WSP View’ (or press Ctrl+W,I), you can see list of files required for the Solution with two Features.

9. Open the ‘feature.xml’ under ItemEventReceiver and change the title to meaningful one. If required add ‘Description’ also.

10. DO the same for the other Event receiver.

11. Press F5 to compile and deploy the solution. Also this would create a WSP file under bin/debug directory. You can use this WSP file to deploy this in different website.

12. Go to SharePoint website, SiteActions->Site Settings->Site Feature and check that the two Features are deployed and activated properly.

13. Open the Document Library within the website and try to add an Item / a column. This should generate a custom error like this.