Fix for error Sql server 2005 reporting service add-in setup interrupted

 

To use Report Viewer web part in SharePoint 2007 64-bit environment, you need to install SQL Server 2005 Add-in. I downloaded the setup from Microsoft site and ran the MSI - “SharePointRSx64”.msi. The setup failed with the error as “sql server 2005 reporting service add-in setup interrupted”.  If you are having this issue, follow these steps:

1. Open the command window (Start>Run type cmd and press enter)
2. Navigate to the path where the installer (SharePointRSx64.msi) is stored
3. Execute SharePointRSx64.msi SKIPCA=1 
4. CD to %temp%. Look for rsCustomAction.exe. If not found, browse to the parent directory
5. Execute rsCustomAction.exe /i  to auto-configure the installed files.

Once the installation will finish, you will be able to see the Reporting Integration section in Central Administration.

Presentation on Service Applications in SharePoint 2010

 

Check the slide show presented by me to Melbourne SharePoint user group on Service applications in SharePoint 2010

Presentation Link

 

Running Hyper-V Disk Images on Windows 7

 

On Windows 7 you could install Virtual PC 64 bit but unable to run a 64 Bit guest operating systems. This is quite frustrating as you could not use Hyper-V VHD provided by Microsoft on Windows 7. The lack of Microsoft virtualization application lead us to use Sun VirtualBox.

VirtualBox includes support for 64-bit guest operating systems and applications. VirtualBox supports Windows 7 as a host OS. It also has no licensing costs as it is freely available as Open Source Software under the terms of the GNU General Public License. Another important feature is that VirtualBox natively supports Microsoft Hyper-V virtual disk image files (.VHD). This feature allows us to take a virtual machine built with Hyper-V and use it on a portable machine such as a laptop or desktop computer.

 

Download VirtualBox Binaries

Sun VirtualBox is available via download from the site http://www.virtualbox.org

Create a VirtualBox Virtual Machine

Creating a new virtual machine (VM) is performed by launching the New Virtual Machine Wizard.

• Name the VM and select the OS Type as appropriate. The OS Version selected must indicate (64 bit). If you are unable to select a version with (64 bit), this likely means the CPU in your host is not 64 bit. You will not be able to run a 64 bit guest if the host CPU is not 64 bit. If you are running Windows 2008 R2 guest, select Windows 2008 (64 bit).

• Select an appropriate memory allocation. The recommendation for a SharePoint 2010 server is 4096. Be sure to leave adequate memory for the host OS.

• When configuring the disk, you need to specify the existing .VHD file. Click the icon to launch the Virtual Media Manager and add the existing .VHD.

• After completing the wizard, click Settings to make a few adjustments:

• Select the appropriate Network setting – see the VM Guest Network Configuration section below for guidance

• It is suggested to disable Audio

Start the VM and Install the Guest Additions

After first starting the VM guest, it is strongly recommended to install the VirtualBox Guest Additions to improve performance and enable mouse/keyboard transitions between host and guest.

• Click Start to launch the VM guest

• Login to the VM (the CTRL + ALT + DELETE key sequence is RIGHT CTRL + DELETE)

• If you need to release the mouse, press RIGHT + CTRL

• At this time, ignore error messages indicating failure to load device drivers (installing the Guest Additions will take resolve these failures)

• When prompted to restart the computer to apply changes, click Restart Now

• Login again

• Install the Guest Additions by clicking Devices, Install Guest Additions… (or pressing RIGHT + CTRL + D). When prompted, select Run VBoxWindowsAdditions.exe. Accept all defaults and accept prompts to install Sun Microsystems device drivers.

• Restart when prompted

• Login again

• If desired, adjust the display resolution

• If you have Internet connectivity, run Windows Update and install the latest security updates

• Adjust the time zone as appropriate

Office 2010 and SharePoint 2010 planned for launched on 12th May

Watch Stephen Elop, President of the Microsoft Business Division, announce the launch of Office 2010 and SharePoint 2010 on May 12, 2010 at 11 a.m. EST. The live keynote focuses on the next wave of productivity that delivers:

End user productivity across the PC, phone and browser
IT choice and flexibility
A platform for developers to build innovative solutions
Join the virtual launch event with Microsoft executives, product developers, partners and customers to:

Find out how peers and partners are already seeing benefits to their business by leveraging the next wave of productivity.
Submit your questions through live Q&A.
Participate via blogs, tweets, social media networks, commenting, and more.
View on-demand breakout sessions showing how Office 2010 and SharePoint 2010 meet the unique challenges people and businesses are faced with today, and provide the solutions they need for tomorrow.

http://sharepoint.microsoft.com/businessproductivity/proof/pages/2010-launch-events.aspx#fbid=DI4gkPybuyL

Application variables empty in classic ASP when deployed on IIS 7.0

 

Last week, I went back in time when one of my friend asked me to help on his site developed in classic ASP. He wanted to deploy this on IIS 7.0 and was getting all his Application variables empty. First, I thought there will be one more global.asa in one of parent directory. But there was no other global.asa file and the worst part was all session variables were working. Finally, I was able to fix this by converting the site from Virtual directory to an Application in IIS 7.0.

So, to make your classic ASP site which is using Application variables work with IIS 7.0, deploy it as an application and not virtual directory. Glad ASP.NET came :-)

Microsoft SharePoint 2010 Products Preparation Tool

 

This tool assist you in the installation of the software prerequisites for SharePoint Server 2010. Ensure that you have an Internet connection, because some of these prerequisites are installed from the Internet.

To Run this tool:

• Download SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkId=168780) from the product installation location, and then double-click the OfficeServer.exe file.
• Accept the license and check the prerequisites

This tool checks if following prerequisites exists:

• Web Server (IIS) role
• Application Server role
• Microsoft .NET Framework version 3.5 SP1
• Microsoft "Geneva" Framework
• Microsoft Sync Framework Runtime v1.0 (x64)
• Microsoft Filter Pack 2.0
• Microsoft Chart Controls for the Microsoft .NET Framework 3.5
• Windows PowerShell 2.0 CTP3
• Microsoft SQL Server 2008 Analysis Services ADOMD.NET
• ADO.NET Data Services v1.5 CTP2

Feature Activation Error : Office SharePoint Server Publishing Infrastructure

 

If you get error denied while activating this feature, you have not activated the dependent feature called “PublishingResources”.

Fix:

Activate the “PublishingResources” feature using stsadm command

stsadm -o activatefeature -name PublishingResources -url http://YOUR_WEBSITE
(change the URL)

Now, Activate the Office SharePoint Server Publishing Infrastructure feature.

Error: “The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress”

 

Check you don’t have duplicate XML tag in the machine.config file on the server reporting error. It was Index server for me.

Free Microsoft Office 2010 Book

 

Download the free e-book “First Look: Microsoft Office 2010” from here

http://blogs.msdn.com/microsoft_press/archive/2009/12/09/free-e-book-first-look-microsoft-office-2010.aspx

The current farm uses database from the following SQL server(s) whose versions are not supported.

 

While upgrading from MOSS 2007 to SharePoint 2010, you might get the following error-

 

The current farm uses database from the follwoing SQL server(s) whose versions are not supported. SharePoint requires these SQL server(s) to be upgraded to minimum supported version before you can continue. Refer to the log file of this configuration wizard for more information about the minimum supported SQL versions and download instructions.

 

To fix this you need to install cumulative updates for SQL Server 2008 SP1
http://support.microsoft.com/kb/970315

Steps to change Virtual Directory Local Path for a MOSS WebAppications and Central Admin site

 

One of easiest way to move Web Application virtual path is to delete the Web application(only IIS site) from Central Administration and recreate them again using new path. But you cannot move Central Admin site using this approach.

After goggling for sometime, I found this nice article which describes the steps to move SharePoint sites including Central Admin

The link is http://www.mattjimison.com/blog/2009/02/26/how-to-change-the-iis-path-for-a-sharepoint-web-application/\

Install SharePoint 2010 on Windows 7(64-bit):

 

SharePoint 2010 provide functionality to install SharePoint 2010 on Windows7. Follow these steps to install on Windows7(64-bit):

1.      Install SQL Express 2008 from "http://www.microsoft.com/express/sql/download/”

2.     Download SharePoint 2010 Beta from http://technet.microsoft.com/en-us/evalcenter/ee388573.aspx. Copy the exe to the folder C:\SharePointFiles

3.      Open Command prompt and run

c:\SharePointFiles\ en_sharepoint_server_2010_beta_x64_x16-19249.exe /extract:c:\SharePointFiles

4.      Open the file using notepad “c:\SharePointFiles\files\Setup\config.xml”

5.      Add <Setting Id="AllowWindowsClientInstall" Value="True"/> to the Configuration section

6.      Install the Filter Pack from C:\SharePointFiles\PrerequisiteInstallerFiles\FilterPack\ FilterPack.msi

7.      Install the following softwares:

• Sync Framework (http://go.microsoft.com/fwlink/?LinkID=141237)
  
• Microsoft Geneva Framework Beta 1 Runtime for x64(http://download.microsoft.com/download/F/3/D/F3D66A7E-C974-4A60-B7A5-382A61EB7BC6/MicrosoftGenevaFramework.amd64.msi)
  
• SQL Native Client(http://go.microsoft.com/fwlink/?LinkId=123718)
  
• Microsoft SQL Server 2008 KB 970315 x64(http://support.microsoft.com/kb/970315)
  
• Microsoft .NET Framework 4 Beta 2(http://www.microsoft.com/downloads/details.aspx?FamilyID=ded875c8-fe5e-4cc9-b973-2171b61fe982&displaylang=en)

 

8.      Run following command to Install Windows Features(IIS and other related)

 

start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures; IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors; IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility; IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-HealthAndDiagnostics; IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging; IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication; IIS-RequestFiltering;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic; IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-IIS6ManagementCompatibility; IIS-Metabase;IIS-WMICompatibility;WAS-WindowsActivationService;WAS-ProcessModel; WAS-NetFxEnvironment;WAS-ConfigurationAPI;WCF-HTTP-Activation; WCF-NonHTTP-Activation

 

9.      Run “c:\SharePointFiles\Setup.exe” to install SharePoint

10.   On “Choose the installation you want page”, click Standalone

11.   Choose default settings and complete the installation

12.   Now, run RegEdit and browse to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS”

13.   Change “ServerRole” value from SINGLESERVER to WFE

14.   Start the “the SharePoint Products and Technologies Configuration Wizard” and follow the steps to install SharePoint 2010

Sandboxed Solution in SharePoint 2010

 

SharePoint 2010 comes with a great feature – Sandboxed Solution. This is type of solution which could be deployed to a site by a site administrator. A site administrator don’t need to be a farm administrator to deploy the solution. The solution have full access to the site where it is deployed but limited to other sites and resources for security reason.

This would be ideal for SharePoint Online services where you could create multiple sites and give user permission to manage and upload custom code to their site without needing assistance from farm administrator

To create a sandboxed solutions:

1. Create a new SharePoint project in VS 2010
2. On SharePoint Customisation Wizard, enter your Site URL. Select “Deploy as a sandboxed solution” as trust level
3. Click Finish and start adding your artifacts to the project
4. Build the solution and create WSP package
5. Browse to your site
6. Open Site Actions – Site Settings
7. Under the Galleries section, select solutions
8. On the Solution page, upload the solution

Now, you could add your artifacts(web parts, activate features) specific to your site

Safe List object from SPWeb in SharePoint 2010

 

If MOSS 2007, the code to read the list object use to be

SPWeb web;
SPList list = null;
try
{
list = web.Lists[“Pages”] }
catch(Exception ex)
{
// List not found
}

The reason to have a try-catch was because SharePoint would throw an exception if the list does not exist

Glad to see that in SharePoint 2010, this issue is fixed. The code in SharePoint 2010, would be

SPWeb web;
SPList list = web.Lists.TryGetList(“Pages”)

TryGetList returns the list with the specified title from the list collection, but returns null if its not found. No more more error handling is required

Using Linq To SharePoint in 2010

 

SharePoint 2010 comes with SpMetal tool that auto-generate entity types based on a list definition. It uses the SharePoint Lists web service to get the schema of a list.

This tool is located at c:\program files\common files\microsoft shared\web server extensions\14\bin

The syntax is

spmetal.exe /web:SITE-URL /namespace:YOUR_NAMESPACE /code:CLassName.cs

Microsoft.Sharepoint.Linq Assembly

 

This is not installed in GAC and hence would not be visible in .NET assembly tab when adding a new reference to project. This is located under at “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI”

Data View Web Part in SharePoint 2010

 

This web part have been replaced by XSLT List View Web part in SharePoint 2010. The old Data View Web part is still supported in SharePoint 2010 but not recommended to use.

Developer Dashboard in SharePoint 2010

 

SharePoint 2010 comes up with great tool to check the performance and process steps(same like ASP.NET trace). This would enable the following information to be displayed:

· The SQL queries they have and their timings.
· Web Part Events Offsets for testing performance against custom web parts.
· Trace information, usually only found in the ULS logs, now available on the page.
· A tree view of all controls on the page.
· Session and Cookie information

To enable it, follow these steps:

• Enable Developer Dashboard- Run this command “stsadm.exe" -o setproperty -pn developer-dashboard -pv OnDemand”
• Do IISReset
• Activate Developer dashboard by clicking on the icon in the top right corner of the browser window of your site
• This will refresh the browser and display the tool bar at the bottom of the page. Click on the Show or hide additional tracing information link at the bottom for detail trace information

Update Parent Content Type

 

When you update a parent content type, the following consideration need to be taken account:

1. Settings of child content type column would be overridden by setting of parent content type column
2. If you make some changes in parent content type and don’t push them down to child content type, these changes would not be pushed to child content type on later stage.
3. If you delete any column in child content type, they are not created again when you push changes from Parent content type
4. Read-only and Sealed child content type will not be updated and an error would raise

Error “Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode"

 

This error occurs when you are trying to create a 64 Bit operating system VMware.

To fix this, restart your machine and enter your system BIOS. Look for Virtualization property and enable it. This is disabled by default.