Compaing managment tool

Today me and my team is searching for good CRM with compaign managment feature. none of the good software provides all features related to customer requriment. i think we should go for a custom one.
there are not multi compaign fetures and lot more that we need. i have not idea now wat to do.

BizTalk 2006 is unable to validate the Char data Type of SQL server 2005

we ll i am posting the same bolg again so it will be more short this time

the problem is if you use generated items from SQL adapter for a stored procedure with Char data type as parameter or you use an update gram with char data type of SQL server you will be unable to validate the generated schema. i observed this thing couple of months back so thought to share it with other.

the resolution is to change either the data type of the table field if your table filed is not critical or change the type of Stored procedure parameter. alternatively you can change the data type of schema from Char to xs:string

hope everybody will be able to understand it

MS CRM migration/redeployment to new domain servers

Deploying or redeploying Microsoft® CRM 3.0 to a second system is a multi-step process that involves:

· Several manual procedures

· The use of standard backup and restore procedures and utilities

· A wizard designed specifically for this process

The wizard is the Microsoft CRM Redeployment Wizard. Using this wizard and the processes described in this document, a

system administrator or software developer can copy and use their Microsoft CRM data in another Microsoft CRM

implementation separate from the original system.

The following are some examples of redeployments that you can make using these tools, processes, and procedures.

On a separate Microsoft CRM implementation with its own Active Directory forest and domain that is not connected to

the original Active Directory forest and domain.

Step 1: Back Up the Databases

Make a copy of or back up the Microsoft CRM databases. Perform the following tasks before copying the databases:

Step 2: (Optional) Back Up Customizations, Workflow, and Custom Reports

Important: Customizations, workflow, and customized reports are not redeployed using the Redeployment Tool. If you want your redeployed Microsoft CRM system to have the customizations, workflow rules, or custom reports from your source Microsoft CRM system, you must back them up manually and restore them to your redeployed system manually.

Step 3: Install Servers and Configure Users

Install all server applications for your new implementation, including:

• Active Directory domain controllers

• Microsoft SQL Server

• Microsoft Exchange Server (optional)

Step 4: Restore the Microsoft CRM Databases

Step 5: Complete the Microsoft CRM Redeployment Wizard

Step 6: Install Microsoft CRM

Install Microsoft CRM on the computer in the new system and make sure to select the Connect to existing database option during setup. Each Microsoft CRM implementation must have the appropriate license.

Step 7: (Optional) Import Customizations,

Workflow Rules, and Custom Reports

Known Issues

Microsoft Windows Operating System Additions and Database Triggers

If you want to install any Microsoft Windows® operating system enhancements or “add-on” programs or create or add any

custom database triggers (other than system defaults) to your new Microsoft CRM system, you must install them before

using the Microsoft CRM Redeployment Wizard. If you have installed the “add-on” programs or added any custom

database triggers, you must remove them, complete the redeployment process on the new Microsoft CRM system, and then

re-install them after you have verified that the new Microsoft CRM system is functioning.

The Microsoft CRM Redeployment Wizard Does Not Finish

If, for any reason, the Microsoft CRM Redeployment Wizard does not complete, you will need to do the following:

1. Delete the Organization_MSCRM and Organization_METABASE databases on the Microsoft SQL Server of your

new deployment. These database files should be located in the folder:

:\Program Files\Microsoft SQL Server\MSSQL\Data.

2. Start the redeployment process again at Step 4 in this document.

Installing Microsoft CRM Server always creates a log files that can be reviewed and used for troubleshooting. By default,

the location of the log files is:

:\Documents and Settings\User\Application Data\Microsoft\Microsoft CRM\Logs

Source CD-1 MSCRM server installer Redeployment Guide

RTHDCPL.EXE - Illegal System DLL Relocation

Back after couple of weeks basically i was busy in design sessions with different teams for new project this time come up with a new type of problem


i think Realteck Audio is unable to initialize and throws error some sort of


---------------------------
RTHDCPL.EXE - Illegal System DLL Relocation
---------------------------
The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL C:\WINDOWS\system32\HHCTRL.OCX occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL.
---------------------------
OK
---------------------------


the problem finally resolved by installing a patch mentioned on the follwing page


http://support.microsoft.com/default.aspx/kb/935448/


interestingly Microsoft patch worked this time

Using Windows Fax Service to Send Fax using C#

somebody Asked this question to me and i thought it would be easy to search rather than to dig

so here it is from http://www.binaryspectrum.com/knowledge_bank/send_fax_using_CSharp.htm

In todays world, while building an application you might run into scenarios where you need to send a Fax from the application. And to a certain extent this is very much required, because I would not want take a print out and go to a fax machine to send a fax. Why cant it be sent from my application?

It is very simple to send a fax using Windows 2000 Fax Service in C#. The application makes use of FaxCom.dll that ships with Windows 2000. This dll is usually located in C:\WINNT\system32 folder. Within the VS.NET IDE, adding a reference to this DLL generates the equivalent Interop.

You can than use the following code to send a fax.

FaxServerClass fs = new FaxServerClass();
fs.Connect("mymachine"); //specifies the machinename
object obj = fs.CreateDocument("myfilename");
FaxDoc fd = (FaxDoc)obj;
fd.FaxNumber = "myfax#";
fd.RecipientName = "Tester";
int i = fd.Send();
MessageBox.Show(i.ToString());
fs.Disconnect();

Prior to using this, we must make sure to attach the Fax modem, install its drivers and see if the modem is shown within the Device Manager. This same code will also work on Windows 2003 and Windows XP Operating systems.

Now that you have implemented a system which will send a fax. Well what about if you want to receive a fax. Well writing all that would mean serious trouble keeping in mind the small time frame you will have to develop your applicaiton. Well every Fax Server, receives a fax as an image and stores it in a Folder (You can see the destination folder path in the properties). There is also an option to save a copy of the incoming fax to a specific folder. Just set these changes, and write a code which will display the contents of that folder and thats it. You are done with your Fax Integration for your application.

An exception occurred while trying to synchronize the state of service 'SharePointPSSearch' to Running. The operation will be retried in 4 minute(s).

i think that problem can be resolve only by reinstalling or repairing SPS so i am going for repair option. lets see what happens after that.