A timeout occurred while waiting for memory resources to execute the query in resource pool ‘default’. Rerun the query.

A workaround that I have found useful has been to re-run your query after the following commands

1. DBCC FREESYSTEMCACHE(‘All’)
2. DBCC FREESESSIONCACHE
3. DBCC FREEPROCCACHE

This frees up the buffer cache in SQL Server and gives your query the much needed space to execute.

In C# You could check if the exception is raised due to lack of Memory on SQL Server in the catch block and execute the following statement

using (SqlCommand cmd = new SqlCommand("DBCC FREESYSTEMCACHE('All') DBCC FREESESSIONCACHE DBCC FREEPROCCACHE ",con))
{
  cmd.ExecuteNonQuery();
}

You could then use a “Goto” statement to go back to your original query.

Do let me know if you have a better way of handling this.

The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

The solution for the issue is simple.

1. Navigate to Start > Administrative Tools > Remote Desktop Services > Remote Desktop Session Host Configuration.
2. With RD Session Host Configuration selected view under Connections.
3. Right click RDP Listener with connection type Microsoft RDP 6.1 and choose Properties.
4. In general tab of properties dialog box under Security, select RDP Security Layer as the
5. Security Layer.
6. Click OK.

You don’t need a restart for this setting to take effect.

In order to change the URL of the Central Administration follow the steps below.

1. Create an entry of the new Central Administration URL in the Domain Name Server. For this example we will configure the Central Administration to open on http://sharepointconfig.mydomain.com
   
   

   Note : For details on how to add a DNS Entry refer to my earlier post Creating a New DNS Entry : Configuring Application URL

2. In the Central Administration Site go to System Settings> Configure alternate access mappings.
3. Here from the Lists of URL(s), click on the current URL of the Central Administrator.
4. In the “Edit Internal URL” Form change the value of the “URL protocol, host and port” to the new URL that you’d like to configure.
5. Press OK
6. Next Fire up the IIS Manager and select the application running your SharePoint Central Administration Its generally named “SharePoint Central Administration v4”. Click ok Binding as illustrated below .
7. In the Site Binding window that opens up, click on edit. Enter the details as illustrated.
8. Click Ok and do a IISRESET.

That is all it takes, We have successfully configured the central admin to work at http://sharepointconfig.mydomain.com. Congratulations

For that we need to create a alias for the server running the service in the DNS. You need to have the access to the DNS Server as an Administrator to be able to do that.

Lets take a look at how can that be done.

1. Fire up the DNS manager, and expand the node of the DNS Server you want to add the entry to.
2. Next Expand the “Forward Lookup Zone” node .
3. Right click on the node with the name of your Domain.
4. Select “New Host (A or AAAA)” option.
5. Enter the detais as illustrated below
   1. Name : Enter the new name of the URL, for Eg, if you want your service to be accessed via “MyService.mydomain.com”, then enter “MyService” as the Name.
   2. IP address : Enter the IP Address of the Server running the service.
6. Click on Add Host.
7. Next You need to add a SPN of this new URL as a HOST. For that run the following Dos Command.

   setspn -s HOST/newurl.mydomain.com

That’s all there is to it, we have set up a new URL for our application, now all we need to do is configure our application to listen to requests with the address in the HOST-HEADER and respond.

So here it is

1. FQDN : Stands for “Fully Qualified Domain Name”. The more complex and complete definition can be found at Wikipedia. In general terms of Development Environment it is the Name of your computer including the Domain Name. For Eg, if you have a computer caller “Comp1” or a server called “Server1” which are part of a domain called “mydomain.com”, then the FQDN for that computer would be “Comp1.mydomain.com” and that of the server would be “Server1.mydomain.com”.
2. SPN : Stands for Service Principal Names. SPNs was implemented in Kerberos authenticated environment as a security measure to avoid spoofing of network services in a domain. You can find a good read on this topic on Safari Books and on MSDN.
3. Kerberos : This is a domain based Network Authentication Protocol. It is used for mutual Identification of Client and Server applications based on a cryptographic token keys. If you’d like to read more about Kerberos you could do that on Wikipedia and directly from its designers at MIT
4. Daemon : Another name of Background Services, definitely sounds like a primitive nomenclature. Read more about it at Wikipedia.
5. Host Headers : IIS allows you to assign any number of sites to a single IP address and distinguish them by using host headers. When IIS receives a request for a Web page, it looks at the information sent in by the browser. If the browser is HTTP 1.1 compliant (Internet Explorer 3.x and later, or Netscape Navigator 3.x and later), the HTTP header contains the actual domain name requested. IIS uses this to determine which web application should answer the request. Read More about Host Header at IT-Notebook.org.

Well it is always good to have an deployment that goes by the URL of crm.yourdomain.com rather than something like appserver.yourdomain.com. For this you don’t really have to change the “Computer Name” of your Server. Lets see how can we configure such an URL for our Dynamics CRM instance.

Well, first thing we need to prepare the Domain Name that we want to configure for our CRM instance. For that you need to take up the following steps

1. You need to go to the DNS Management Console on your DNS Server and create an entry of the New Domain against the IP address of the Server.
2. Next you need to add 2 Service Principle Names (SPN) for this Domains.
   1. Create an SPN for HOST/CRM.YOURDOMAIN.COM using the following Dos command :
      setspn –s HOST/CRM.YOURDOMAIN.COM
   2. Next create an SPN for the login that your CRM Services are going to be configured with :
      setspn –s HTTP/CRM.YMSLI.COM <yourdomain>\<crmserviceaccount>

Now our URL is ready to be configured. Lets configure the Dynamics CRM instance to use the new URL.

1. Next Step is to go to the Deployment Manager, Right click on the Microsoft Dynamics CRM Node and select properties.
2. Now on the “Microsoft Dynamics CRM Properties” window, goto the “Web Address” tab and change all the URL(s) to your new URL which in our case is crm.yourdomain.com:80.
3. Next you need to configure the IIS binding for the “Microsoft Dynamics CRM” web application.
4. Next a very important thing, you need to configure the change for the Help Catalogue URL in certain builds as there was a bug where the help used to keep pointing at the old “Computer Name” URL even after you change the binding.
   For this you need to open PowerShell and run the following commands on the CRM Server:  
   1. Add-PSSnapin Microsoft.Crm.PowerShell
   2. $web = Get-CrmSetting WebAddressSettings
   3. $web.HelpServerUrl = ""
   4. Set-CrmSetting $web
5. Next do a IISREST.

And that is all you need to do to get a nice memory-friendly (Human Memory is what I mean)  URL for your Dynamics CRM Instance.

If you find this post useful do leave your feedback in the comments section.

Today I fell into a paradox where I wanted to send CTRL+ALT+DEL to my RDP session, and my local machine would keep locking up whenever I pressed the combination.

A bit of Googling around got me to the solution, for Remote Desktop the Combination is

CTRL+ALT+END

Well who, with the most prominent of common sense could have thought of that. Let me know if you are the one ?

Due to some unprecedented issues with my blogging software, my earlier blog was rendered in-accessible to me. That was the reason I was not able to post anything new either. I was trying to gain access to the admin site of my blog for a long time, but failed. Thus I had no choice but to refurbish my blog and re-setup everything from scratch. I have changed my blogging software to WordPress from earlier Joomla CMS.

I will be trying to get back as much of my articles from the earlier blog as I can and hopefully things will remain smooth for some time now, and I will be sharing stuffs more often.