Importing organisation in MS CRM 4,0

Task: Import organisation with existing database to CRM 4.
Solution: The solution is obvious - restore existing database in SQL Server and then import organisation via Deployment Manager. Also there are a lot of articles, which can help you accomplish this task. One of them is http://www.tribridge.com/Blog/crm/default/2011-06-14/How-to-Migrate-CRM-4-SQL-2005-32-bit-to-SQL-2008-64-bit-Environment.aspx.

SharePoint 2013: RelatedItems column in WebPart

Task: Show related items in the web part like the image bellow:

Resolution:

CRM 4: Create custom button in associated list view menu

Have you ever tried to remove "Add existing button" or add your new custom button to associated list view menu like the image bellow?

Ok, by few lines of JS you can do this. Here is how:

SharePoint 2013: Approve and Reject buttons on DispForm.aspx of task

Task: Create custom view form, which will contain 2 buttons allowing to accept and reject task  (Set TaskOutcome field) in view mode.
Something like this:

Steps you need to check when hosting Silverlight on IIS 6

When you are hosting a Silverlight application on ISS, you need at first check the following things:

1. .svc file type is mapped to the aspnet_isapi.dll. If it is not, then you`ll see the following screen, when opening your .svc in web browser:

Host Silverlight Application on IIS 6

When hosting silverlight application on IIS6 you can get the following error message:

SQL error when trying to insert data returned from Linked server procedure

Query:

DECLARE @TABLE TABLE ( StatusFlag int, StatusText varchar(150), run_date varchar(150), run_time varchar(150), run_duration varchar(150) )
insert into @TABLE
EXECUTE  [CRM_OUT].[dbo].[GetLoadStatus]
SELECT * FROM @TABLE

Error: 

OLE DB provider "SQLNCLI10" for linked server "Server..." returned message "The partner transaction manager has disabled its support for remote/network transactions.".
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "ServerB" was unable to begin a distributed transaction.

Solution:
Run the following script on the server, where you wrote a select request:

EXEC sp_serveroption @server = 'SRV-crm-sql-02',@optname = 'remote proc transaction promotion', @optvalue = 'false' ; 

Thanks to http://www.sqlservercentral.com/Forums/Topic1102122-146-1.aspx