CRM Blog

June 2008 - Posts

Increasing the CRM 4.0 Attachment Size Limit
by Jeremy Hofmann 06.05.08

Comments    1 Comment(s)
The default attachment file size limit in Microsoft Dynamic CRM 4.0 is 5 MB.  There is good reason for this - as a general rule you should be placing some restrictions on the amount of file data that can enter CRM so that the database can maintain a reasonable size and so that performance is optimized. However, your business may find the need to increase this size a little in order to handle larger file attachments.  Here are the instructions to increase the file size limit to 10 MB.  You can go larger than this, but pay close attention to the table size and performance over time as you want to keep CRM running as well as possible. Note - even though the System Settings option looks like this it would apply to email attachments only, it does apply to "notes" type attachments as well.  Finally, this procedure to change the max attachment size is not an officially published recommendation, so use this at your own risk. How to increase the max attachment size in CRM 4.0:

 

1.           Open the application web.config (C:\Inetpub\CRM\web.config).

 

2.           Locate the <httpRuntime> key within the <system.web> element and change the values to the following:

<httpRuntime executionTimeout="9999" maxRequestLength="10240"/>

3.           Locate the <httpRuntime> key within the <system.web> element of the <location path='MSCRMServices"> element, and change it to the following:

<httpRuntime maxRequestLength="10240"/>

4.           Save and close the web.config.

 

5.           Open the CRM web application (http://crm).

 

6.           Navigate to Settings | Administration | System Settings.

 

7.           Click the E-mail tab.

 

8.           Change the maximum file size (in kilobytes) field to 10240.

 

9.           Click Ok to save the changes.

 

10.        Perform IISReset. 

 

Filed under:
Enterprise CRM - What to Look for in a CRM Admin
by Jeremy Hofmann 06.04.08

Comments    No Comments

Depending on your company’s size and installed number of users, you may or may not need a dedicated CRM admin.  Microsoft Dynamics CRM is a product that lends itself to a power user for day to day maintenance and administration.  However, if you have a larger number of users, say greater than 200, and especially if these users are spread out across geographic regions or branches, have independent needs, or a large amount of data to manage, then a full time admin may be your best bet.

 

But what should you look for in a CRM admin?  It can be a challenging position to define.  On the one hand, you need someone who can handle the business requirements, managing scope, timelines, and user expectations, but also someone who can deliver much of the work or coordinate the various technical departments in order to maintain and modify the system along with the growing needs of the business.

 

In essence, you need someone with a 50/50 mix of business and technical skills.

 

In particular, the ideal CRM admin should be able to:

 

·        Meet with user groups (departments) to understand and define requirements

·        Coordinate solutions and resolve differences among the departments

·        Schedule resources and maintain timeline and budget

·        Be able to perform system configuration work

·        Understand what each area of the system offers and a basic understanding of how it works: sales, customer service, and marketing functionality, workflows, duplicate detection, and the Outlook client, to name a few

·         Understand the core architecture of CRM and server topology: web servers, SQL server

·        Keep up with the latest CRM industry news, Microsoft Dynamics CRM news, and community newsgroups for the latest information and patches

·         Be an advocate for CRM within the company

 

Big bonus points for any candidate that can also:

 

·         Program Microsoft Dynamics CRM using the SDK

·         Write SQL Reporting Services Reports

·         Write complex and other data mining queries against the system

·         Write client-side JavaScript code

 

So, the next question is – how to find such a person?  While this can be a difficult task, it is not impossible.  Here are a few suggestions to get you going:

 

·        Hire from Within – Hiring from within means you don’t have to train that person on the core business and begin to use them more immediately.  Often times the challenge and visibility that comes from being the CRM “go to” person benefits the employee by increasing their value and security within the organization

·        Consult to Hire – If you don’t have the skills on the ground to get going, consider hiring a consultant with the option to hire after a fixed period.  This is a great way for both parties to “try each other out” before making a final decision.

·        Place Ads on All the Major Boards – Be sure to be honest about the skills that are needed.  Conduct technical screens on all candidates and find out their mix of business / technical skills.

·        Check with Your Implementation Partner - Often times consulting companies and candidates are not a good match due to the high travel commitments required at consulting companies, even though the candidates skill set is ideal for CRM.  Check with your implementation partner to see if they can pass along some resumes of candidates who may still be looking for a position. And lastly…

·        Don’t Give Up!  The right person is out there.  It’s just a matter of searching in the right places, being careful about the skill set balance, and integrating that person into your organization.

 

Issues Upgrading Implementations using Host Headers to CRM 4.0
by Luke Simpson 06.03.08

Comments    No Comments

When upgrading a CRM 3.0 implementation using host headers, a tricky little bug may occur that is very difficult to diagnose.  The bug exists within the actual installation package of CRM 4.0, where the installation will use the machine name of the CRM server instead of the host header name.  So the former address of http://<hostheader>/  will now be replaced with http://<servername>/, which of course doesn't exist..  What is more interesting, and what causes this to be hard to troubleshoot, is that when this happens the web UI will operate just as it should after the upgrade.  You will be able to type in http://<hostheader>/ and it will direct you to your upgraded 4.0 implementation.  Where CRM will "break" is when you attempt to run workflow's or configure the Outlook client.  At this point, it will throw an error that states that the CRM server cannot be reached, and that it may be down.

The fix for this is very straightforward, although unsupported since it requires direct updates to the MSCRM_CONFIG database.  Simply open up the DeploymentProperties table within this database and change the entries for AsyncSdkRootDomain, ADSdkRootDomain and ADWebApplicationRootDomain to reference your host header.  Or, if you don't like making manual modifications to your database, you can run this script:

USE MSCRM_CONFIG
DECLARE @HostHdr VARCHAR(250)
SET @HostHdr = 'hostheader'
Update DeploymentProperties SET NVarCharColumn = @HostHdr WHERE ColumnName = 'AsyncSdkRootDomain'
Update DeploymentProperties SET NvarCharColumn = @HostHdr WHERE ColumnName = 'ADSdkRootDomain'
Update DeploymentProperties SET NvarCharColumn = @HostHdr WHERE ColumnName = 'ADWebApplicationRootDomain'
GO

Just change the value of the @HostHdr variable to whatever you need it to be, and run the script.

After that, all you need to do is run an IISReset, and restart the CRM Async service and you will be good to go.  As a friendly reminder, this is unsupported and should be considered informational only.

Filed under: