This potential CRM error should typically appear if you had a CRM database, uninstalled it and then tried to reinstall with a different license type. But it can also appear if you used a different license code during the reinstall. You can get confused if you have access to multiple installations and forgot the key you used for a particular instance. But no worries, you can find you key again in SQL -> MSCRM_CONFIG -> ConfigSettings -> LicenseKey. Use that key and it should solve your problem

Symptom: You choose to run a workflow but nothing seems to happen and the new workflow doesn’t appear in the workflow tab.

Theory: If my CRM exam studyage served me right, the Microsoft Dynamics CRM is composed of 3 parts. The application layer producing the business logic, the data layer interfacing with SQL and the async service layer doing stuff like workflows on the background (a bit like SQL agent). If the first 2 break, you won’t get your CRM site at all. When the async service layer breaks, it’s a bit more subtle like in this case.

Diagnosis: The most important part is to intercept at least some form of error output and determine what’s wrong with the system. You need to turn on your tracing function for CRM as described here. The look at your web log and your async log, typically at C:\Program Files\Microsoft Dynamics CRM\Trace.

Possible Causes:

• First, be sure to update your CRM software. At the time of the writing, the Update Rollup 11 is the newest
• Check your IIS web.config file. Make sure critical parts required for the async service are there. Make sure for instance that the <System.Workflow.ComponentModel.WorkflowCompiler> section is there to allow the workflow compiler to use basic CLI classes like String and Object etc.
• If your CRM site is initially installed in port 5555, changing it after in IIS Manager won’t affect the async service. Therefore, if you change it to port 80 or do anything else to change the URL for accessing your CRM site, you won’t be able to access the async service. Check your trace to confirm your initial setting.

I don’t know actually since most of the relevant stuff becomes read-only after filling with data. But my approach is solve this as early on in the process as possible to the entirety of the data and save processing time on a custom loop after.

In other words, your DataGridView is typically bound to a DataTable. That is typically filled with stuff from the database. Make sure your AutoGenerateColumns property is set to true in the DataGridView and select your data to match the type you want to display in the DataGridView. For instance, to get checkboxes,

SELECT ..., CAST(column1 AS bit), ... FROM ...

and change the data type right out of the DataAdapter and DataGridView will figure out the rest automatically

Another quick tip.
Selecting from INFORMATION_SCHEMA.COLUMNS unfortunately returns also every column in views on top of tables. I never use views and definitely don’t need those columns.

To filter them out, use:

SELECT * FROM INFORMATION_SCHEMA.COLUMNS c
JOING INFORMATION.TABLES t ON c.TABLE_NAME = t.TABLE_NAME
AND t.TABLE_TYPE = 'BASE TABLE'

There are too many top Google search results giving the impression that it is impossible to compare 2 DataRows for its value contents and the programmer needs to iterate through everything himself.

Such is no longer true in .NET 3.5 but the blogosphere doesn’t seem to have caught on yet.

It is possible, given 2 DataTables or any other enumerable object types, to compare its contents using LINQ in just one line of code.

I will give an example in VB where I’d want to compare all column properties (description, data type, field length, etc) of all tables in 2 supposedly identical SQL databases.

1. Read into DataTable the SQL command

SELECT * FROM information_schema.COLUMNS
WHERE TABLE_SCHEMA = 'dbo'
ORDER BY TABLE_NAME, COLUMN_NAME

this returns a table of with all the column properties. Do this for your second table you want to compare.

2. To get the difference, you can use the Except LINQ operator on the 2 tables and use a DataRowComparer class to check for value equality instead of reference equality

Dim differenceTable = masterTable.AsEnumerable.Except(subjectTable.AsEnumerable, DataRowComparer.Default)

this will return you a list of DataRows present in masterTable but not in subjectTable. You can also use other LINQ operators such as Distinct, Union and Intersect.

Another quick solution for users of MSSQL Server.

To view the permissions the current logged SQL user has, use the command

SELECT * FROM fn_my_permissions(NULL, 'DATABASE')

or variations to return a list of SQL commands permitted.

For more details, visit the MSDN page