Microsoft Dynamics CRM lets you create trace files that monitor the actions performed by various Microsoft Dynamics CRM components. For example, CRM Async service can create its own trace file, which enables you to troubleshoot error messages or other issues with CRM Async service. Apart from that, these Trace files can be an excellent resource for an experienced CRM Developer to understand what exactly is going on behind the scenes.
CrmXpress TraceHelper helps you to enable/disable tracing for Microsoft Dynamics CRM with few clicks. It also gives you the option to manage the trace files from within a single window.
You can download it from here : http://www.crmxpress.net/Tools/CrmXpress.Win.TraceHelper.zip
Remember: once the settings are applied, IIS must be restarted to take the effect.
It's been a long time since I thought to put this to public. I have used this tool for a quite a long time now. Basically, it allows you to create profiles with username and password. Now being CRM developer many a times you would want to launch CRM Web interface with another user's credentials. Generally, you would do so by using Run As or by creating a shortcut that will ask for credentials when it is clicked OR by disabling automatic logon in intranet zone.
I wanted to come up with a lot easier way to achieve this. That's why I made a simple utility that stores usernames and credentials and set of applications in a profile. You can create as many profiles as you want and add as many applications as you need. Credentials you provided are encrypted and stored with user settings. To add application, all you need to do is drag and drop a shortcut of the application or the application itself on to CrmXpress Run As Gui tool.
You can download it from here : http://www.crmxpress.net/Tools/CrmXpress.Win.RunAsGUI.zip
Your feedback is really important for me to provide feature upgrades/bugfixes.
Kindly note that I have tested this utility on Win7/Server2K8/Server2K8R2 x86/x64 editions with .NET Framework 2.0.
Here are steps to start using this tool.
- Launch CrmXpress.Win.RunAsGui.exe
- Click on Add. It will auto fill current user name and domain/workgroup name.
- Enter password.
- Click on Save. Your default user profile is now created.
- Click on Add again. It will auto fill current user name and domain/workgroup name. Change the name with any other domain/workgroup user name of your choice.
- Enter password for the user name that you have entered.
- Click on Save.
- Now you will have two profiles and you can access them via Profiles drop down list.
- Drag any application shortcut on to the CrmXpress.Win.RunAsGui's User Interface.
- The application will be added to the applications list for a given profile and it will be launched with credentials of whichever user profile you have selected.
- This program is provided as is without any guarantees or warranty.
- Although the author has attempted to find and correct any bugs in the free software programs, the author is not responsible for any damage or losses of any kind caused by the use or misuse of the programs.
- The author is under no obligation to provide support, service, corrections, or upgrades to this free software program.
Here is another strange but interesting issue, I faced almost a month back. One of my acquaintances was trying to import a CRM Organization [They exported the database and were importing the database into an existing CRM installation] which was using a different domain. Everything was going fine until he reached to the point where you are supposed to map existing users with users from destination AD. The moment he reached that stage he was running into an Exception in Deployment Manager add-in [See the screenshot below].
After trying to troubleshoot this problem for a while, I found few pointers regarding empty domainname field in SystemUserbase table. Upon examination of the SystemUserbase table, we found that indeed there were few records with empty domainname field in there. Now INTEGRATION and SYSTEM are valid users of CRM and they do not have domainname mapped to them however, for every other record there must be an associated user from AD i.e. domainname field must be populated. In our case, there were few other users, which had empty domainname field. We filled in those fields with valid domain\username information and voila, import went just fine.
Aha... yet another topic on User Accounts. Just last week or so I was discussing with a colleague of mine here at CrmXpress. It was about Service Accounts. Now we all know that if you are using a Service account [A dedicated account to run services for SQL or MSCRM or maybe even IIS], first thing you must do is during the creation of the service account itself, you MUST mark a checkbox labelled "Password Never Expires" so that the password expiry policies are not applied to this account.
Now in case you did not check this check box and your service account password expires, it will bring down all the dependent components/services/applications. To fix this quickly here are few places you might want to look into in case you end up with a service account with expired password. You can always set the password to what it was however some organizations have a policy against that. So you would want to look into places where you can change the password for a given service account. So here is a list of all the places that you should look into :
- Start -> Run -> Services.msc -> Sort by 'Log On As' column
- Start -> Run -> Inetmgr -> Expand Sites -> Select a web site which is using the service account -> Under Actions Pane -> Click on Basic Settings... -> Click on Connect As... button in the popup Window.
- Start -> Run -> Inetmgr -> Expand Application Pools-> Select an Application Pool which is using the service account -> Under Actions Pane -> Click on Advanced Settings... -> In the popup window -> Navigate to Process Model -> Set Identity Property.
- Check web.config files for encrypted\plaintext impersonation details