Posts

Showing posts from October, 2009

msftesql and cisvc services error in MS CRM 4.0

While installing MSCRM 4.0 on Windows Server 2008, having SQL Server 2008 preinstalled, the installation verification fails and displays missing components msftesql and cisvc services. 1) msftesql (the sql server full text indexing service) has a different name against sql server 2008. Just rename the registry key HKLM\System\CurrentControlSet\Services\MSSQLFDLauncher to msftesql to give an illusion to the MSCRM verification phase that services is present in the system so that it does not fail while installation. Now restart the system and run the installation of MSCRM again. After installation rename the HKLM\System\CurrentControlSet\Services\msftesql back to MSSQLFDLauncher. 2) To solve the cisvc services error, right click the MyComputer->Manage, now right click the Roles ->Add Roles and now install the file services role.

Using Disposable Windows SharePoint Services Objects

During my last project on MS CRM 4.0, I had to integrate SharePoint and MSCRM. This majorly involved creation of a web part for data analysis. During the development, I encountered scenarios facing long term retention of share point objects in memory. Memory leak is one of the major problems that can arise due to bad coding practices. Disposing the used SharePoint Objects is one of the best practices while coding in SharePoint. Here, I have explained why, how and when to dispose off the SP Objects in code. The objects in the Windows SharePoint Services 3.0 object model serve as an interface for working with Windows SharePoint Services data. The developers frequently call into the object model to read data from or write new data to the Windows SharePoint Services store. The Windows SharePoint Services object model contains objects that implement the IDisposable interface. One must take precautions when using these objects to avoid their long-term retention in memory in the Microsoft .