Embedding YouTube video on a SharePoint site

On the particular day, Client requested to show a YouTube video on a SharePoint site. I did a quick research and followed these steps:


On the SharePoint Site, add a 'Content Editor Webpart'. 

Next, choose 'Source Editor' from the right pane.

Now, go back to the YouTube site and find the video you want to add on the SharePoint Site. There is an Embedded button on the YouTube site, click on that to get the Embedded codes.

Now, Copy these embedded codes.

Open the Source Editor, and paste the already copied text, Save, apply and OK. 

That's all guys!!!

Fixing issue "Your queue job CreateWssSite failed. Please contact your administrator for assistance"

While working on the Microsoft Project Server 2007, you might encounter an issue "Your queue job CreateWssSite failed. Please contact your administrator for assistance" This error shows in an email and normally sent to the Administrator. 


The root cause of this error is, when you are publishing a Project from the Microsoft Project Professional, the Project Workspace URL is asked. There are several validation associated with this workspace URL, like Total length, invalid characters etc. Now, when you are trying to publish your project programmatically, the above mention error showed.


On the Project Server you can view the project workspace URL the following way:

Please use the following setting in the "Project Workspace Provisioning Settings". This setting will stop creating project workspace as soon as you published a project. Now user create the project workspace site manually if he got the permission. 

Converting office documents into a web page in SharePoint

While working on SharePoint I was looking a facility to see the uploaded documents as a web page. Then the users does not require a sophisticated office system only to view the documents.


Steps:


1) Go to Central Administration - > Operations - > Services on the Server page.

• "Document Conversions Launcher Service"
• "Document Conversions Load Balancer Service" should be Started.

2) Central Administration -> Application Management -> Document Conversation

3) Select the site where you want to use the Document Conversion service and Click on OK.
Please note that, this service only works on a "Publishing Site".

4) Now, go back to your site where the Document Conversion service is enabled. Hover on a document, then select "Convert Document" next, "From Word Document to Web Page". 

5) Specify the Title and URL

6) Following page shows if any errors/warning occurs at the time of conversion.

7) View the document as a web page

Limitation:

• This service only works in a Publishing Site
• Converts only Office 2007 documents, does not support .doc files
• Sometimes images does not show properly on the web page.
• Does not work if MOSS is installed on a Domain Controller.

Project Server Backup and Restore

Backup:

Step 1: Create the Backup location

 

Step 2: From the “Central Administration” click on “Perform a backup”

 

Step 3: Select “Farm” option and click on “Continue to Backup option”

Step 4: Specify the backup location and type as “Full”

Step 5: Wait for the entire “In Progress” task to be completed

Step 6: Check the creation of backup file.

 

Restore Process:

Step 1: From the Central Administration, Operations, and click on “Restore from backup”

Step 2: Specify the backup location

 

  Step 3: Select the backup and click on “Continue Restore Process”

Step 4: Next, select “NetappSharedService” from the selection, as we are restoring only the Project Server specific data. Click on “Continue Restore Process”

Step 5: Select “Same configuration” and ignore the warning message

 

Step 6: Provide the password for database access

 Step 7: Please wait for “In progress” and “Not started” tasks to be finished.

Step 8: verify the PWA site for all the data and configuration restored or not.

Project Server Site (PWA) cannot be edited using SharePoint Designer

While developing on the Project Server (PWA) , I got a requirement to change some design (UI) of the site. Therefor I tried opening the site with the SharePoint Designer (SPD). But to my surprise I got the following message.

After doing some research I learnt that, on the site definition level, Microsoft disabled the editing in SPD. On the "ONET.xml" file the following key does the disabling act.







Now,the tricky part is if you remove this key on the site definition file, there is a huge possibility that your site might break and Microsoft does not recommend this modification on the ONET.xml file.

DisableWebDesignFeatures="wdfopensite"

This discussion thread has some more details. 

Re-publish an InfoPath Template to an existing list

Recently I made a goofed-up in a SharePoint list where an InfoPath form was published. As we all know that, if we publish an InfoPath form to a library, the next time onwards the publishing wizard remember everything and you only have to click next.


But when I try to re-published a similar template from a different site to an existing library, the metadata of that list are gone. Also I have figure out that the internal names of  "Promoted Properties" are also changed. Say, earlier we have a field called "Request" now it becomes "Request1".


To avoid these type of problem, you need to map the column when published. 

Using WSP Builder for creating and deploying a Solution

The WSP Builder is an excellent tool for creating Solution package automatically, and I am using this for a long time, so thought to write about it.

This tool is created by Carsten Keutmann and can be installed on bot VS2005 and VS2008. First you have to download from the codeplex then install.

Earlier, we had to create a "CAB Project" from the "Setup and Deployment" section on the Visual Studio. Then add the other project as resources to this CAB Project, Build the project and rename the output file extension to WSP, looks like lots of steps and efforts!!! WSP Builder is a single step creation.

Only thing need to to is Right Click on the Project of the Solution Explorer, WSPBuilder -> Build WSP

This step will generate the log that shows the components added in the WSP file created.

Important: Please verify very closely the output logs generated and check all the required DLLs are added in the WSP or not.

Once you have successfully built the WSP, now its time to deply it using STSADM commands. For this you have to navigate to the \12\BIN\ directory.

1st Command: AddSolution

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>STSADM.EXE -o addsolution -filename "E:\Project Server\Server Data\GenerateFormReceiver\EventReceiverBinder\EventReceiverBinder.wsp"
 

2nd Command: DeploySolution

STSADM.EXE -o deploysolution -name EventReceiverBinder.wsp -immediate -allowGacDeployment -url http://somu/pwa

Gotcha: The above command will give you an error "This solution contains no resources scoped for a Web application and cannot be deployed to a particular Web application."
At this point you might think there is problem in the Features.xml file, where you are trying to re-defining the scope property.

But the trick is, the DeploySolution cammand should not use a deployment scope, means the "url" switch at time moment. Therefore the solution will be globally deployed.

STSADM.EXE -o deploysolution -name EventReceiverBinder.wsp -immediate -allowGacDeployment

voilla!!! you successed.

3rd Command: ActivateFeature

STSADM.EXE -o activatefeature -name EventReceiverBinder -url http://Somu/PWA -force

And you are done.

Uninstalltion script:

Deactivate The feature:

STSADM.EXE -o deactivatefeature -name EventReceiverBinder -url http://Somu/PWA -force

Retracting the Solution:

STSADM.EXE -o retractsolution -name EventReceiverBinder.wsp -immediate

(Wait for couple of seconds...)

Deleting the Solution:

STSADM.EXE -o deletesolution -name EventReceiverBinder.wsp

 if you have not wait for the period, might encounter the following error.

The solution "EventReceiverBinder.wsp" has been deployed in the farm. Please retract the deployment before removing the solution.You can also use the -override parameter to forcibly remove the solution, but you will not be able to retract the solution deployment.