Hi,

I was getting the following error “Invalid domain name. Domain name is either invalid or unreachable” while trying to register a plugin.

Found this kb article

http://support.microsoft.com/kb/948593/EN-US/

So installed update rollup 4.0

http://www.microsoft.com/downloads/details.aspx?FamilyID=0ddf8e83-5d9c-4fe7-9ae6-f2713a024071&displaylang=en

After that on trying to open CRM started getting the could not find GUID error.

Not very sure, but it has something to do with ActiveDirectory i guess.

Anyways uninstalled the Rollup 4 and to my surprise everything started working normally, even i was able to register plugin without any issues!!

Just thought of sharing the same !!

Hi,

Found out two good article to solve the above problem

http://blog.customereffective.com/blog/2009/03/troubleshooting-offline-synchronization-with-microsoft-dynamics-crm-40-for-outlook.html

http://support.microsoft.com/kb/916165

Bye..

Hi,

In callouts in CRM 3.0, for providing configuration information we used to create our own config file.

The naming convention that we used to follow was

AssemblyName.dll.Config

And we used to deploy it at the same location as callout i.e. server/bin/assembly

The structure of the config file used to be

<?xml version=”1.0″ encoding=”utf-8″ ?>
<config>
<crmurl>http://servername:5555/mscrmservices/2006/crmservice.asmx</crmurl&gt;
<loglocation>C:\CrmLog\PluginLog.txt</loglocation>
</config>

To read the config values in the callout we used to have this following code

string assemblyLocation=System.Reflection.Assembly.GetExecutingAssembly().Location;
string crmUrl=GetConfigValue(assemblyLocation,”crmurl”);

The GetConfigValue function

private static string GetConfigValue(string AssemblyName,string KeyValue)
{
string Filename=AssemblyName+”.config”;
XmlDocument xmlDoc = new XmlDocument();
xmlDoc.Load(Filename);
XmlNode crmNode = xmlDoc.SelectSingleNode(“//”+KeyValue);
string tagValue=crmNode.InnerText.ToString();
return tagValue;

}

Actually I was working with callouts after so many months, so thought i should save the above information for future reference!!

Bye…

Hi,

I was occasionally getting this error while trying to open pages within CRM.

This post by helped me solve the issue

http://billoncrmtech.blogspot.com/2008/10/sql-timeouts-in-crm-generic-sql-error.html

Key to change (or add if not there) of type  DWORD

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\OLEDBTimeout

Bye..

Hi,

I got this error while developing a post update callout for CRM 3.0.

The reason for this could be because the Network Service account under which CRM runs may not have appropriate rights for that.

One possible solution is to right click the assembly -> Properties –> Security tab –> Add Network Service account and give it appropriate rights.

That’s it..