TIDBITS on the Microsoft Power Platform

Caring for ASYNC

David Jennaway has a great post on the Asynchronous Service as well. You can read some of it here and link to the rest over on Dave's great CRM blog at http://mscrmuk.blogspot.com/  ================================================================= CRM 4.0 UR 3 brought in a useful feature, the ability to configure the CRM Asynchronous Service to automatically delete records from completed asynchronous operations, and hence keep the size of the asyncoperationbase SQL table down to a reasonable size. This behaviour is configured by the registry values AsyncRemoveCompletedJobs and AsyncRemoveCompletedWorkflows However, I recently met an issue with this behaviour, where the CRM Asynchronous Service appears to get in a state where all it is doing is deleting completed jobs, to the exclusion of all other activity. This can leave the CRM Asynchronous Service to have effectively hung (not responding to service control requests, nor polling for new jobs to process) and not to process any new jobs for a considerable period of time (in one environment, this could be several hours). The main symptoms are: No jobs being processed for a considerable period of time The Crm Asynchronous Service not responding to service control requests (i.e. you cannot stop it through the Services console, so you have to kill the process) No values reported for most performance counters (e.g. 'Total Operations Outstanding', 'Threads in use') If you do restart the service, you see a burst of activity (including performance counters) whilst outstanding jobs are processed, then it reverts to the same behaviour as above If you look at the SQL requests submitted by the Crm Asynchronous Service (I use the SQL dynamic management views sys.dm_exec_requests and sys.dm_exec_sessions) you see just one DELETE request and no other SQL activity At the moment, the only workaround I have is to remove the registry values, and to use a scheduled SQL job to periodically clear out the asyncoperationbase table. Here is an example of such a script.

Read More:

http://mscrmuk.blogspot.com/2010/12/stability-issues-with.html

 

A Little Bit More on ASYNC

Thanks to Matt Wittemann over at ICU MSCRM  

=================

Posted by Matt Wittemann

There have been several KB articles and updates published to help control the size of the AsyncOperationBase table, which can cause your CRM database to grow very large, very quickly. (See here and here.) But just what are all those records anyway?

I pulled the following lists together from the SDK and technet in order to put this info in one place, where it’s a little more user-friendly (at least for me!).

First, the list of AsyncOperationTypes:

READ MORE at

http://icu-mscrm.blogspot.com/2009/12/asyncoperationbase-table-what-are-all.html

Value	Field	Description
1	Event	Specifies a system event.
2	BulkEmail	Specifies a bulk e-mail operation.
3	Parse	Specifies an import file parse operation.
4	Transform	Specifies an operation to transform parse data.
5	Import	Specifies an import operation.
6	ActivityPropagation	Specifies a campaign activity propagation operation.
7	PublishDuplicateRule	Specifies an operation to publish a duplicate detection rule.
8	BulkDetectDuplicates	Specifies a bulk duplicate detection operation.
9	CollectSqmData	Specifies an operation to collect SQM data.
10	Workflow	Specifies a workflow operation.
11	QuickCampaign	Specifies a quick campaign operation.
12	PersistMatchCode	Specifies an operation to update the matchcode.
13	BulkDelete	Specifies a bulk delete operation.
14	DeletionService	Specifies a Deletion Service operation.
15	IndexManagement	Specifies an index management operation.
16	CollectOrgStats	Specifies an operation to collect an organization's statistics.
17	ImportingFile	Specifies an import subprocess operation.
18	CalculateOrgStorageSize	Specifies an operation to calculate an organization's storage size.
19	CollectOrgDBStats	Specifies an operation to collect an organization's database statistics.
20	CollectOrgSizeStats	Specifies an operation to collection an organization's size statistics.
21	DatabaseTuning	Specifies an operation for database tuning.
22	CalculateOrgMaxStorageSize	Specifies an operation to calculate an organization's maximum storage size.
23	BulkDeleteChild	Specifies a bulk delete subprocess operation.
24	UpdateStatisticIntervals	Specifies an operation to update statistic intervals.
25	FullTextCatalogIndex	Specifies an operation to generate an organization full text catalog index.
26	DatabaseLogBackup
27	UpdateContractStates	Specifies an operation to update contract states.
28	ShrinkDatabase
29	ShrinkLogFile
30	ReindexAll	Specifies an index management operation.
31	StorageLimitNotification
32	CleanupInactiveWorkflowAssemblies
38	ImportSampleData

Next, here’s a list of the different state/statuscodes that each of these operation types can be in:

State	Status	Numeric status value
Ready	WaitingForResources	0
Suspended	Waiting	10
Locked	InProgress	20
Locked	Pausing	21
Locked	Canceling	22
Completed	Succeeded	30
Completed	Failed	31
Completed	Canceled	32

Hope this is useful to you! Have fun with it.

http://icu-mscrm.blogspot.com/2009/12/asyncoperationbase-table-what-are-all.html

Dynamics CRM Tools: Advanced Find Search: Where is this damn N:N relationship???

Did you ever have this feeling that something should behave in a way and you can’t figure out why this does not…?

I faced this feeling recently regarding the advanced find search. Here is the scenario: I created a N:N relationship between the account entity and a custom entity called Technology. As this relationship was just a “technical” one, I decided to hide left hand menu for this relationship. Below screenshots were taken for entity “test”.

When I then needed to perform an advanced find search on account related to a specific technology, I wasn’t able to select the N:N relationship in the list of relationships. I even thought that it was perhaps a normal behavior for N:N relationships (yeah, I know, that”s dumb, but I do not required N:N relationship for queries so often).

via mscrmtools.blogspot.com

One of the greatest benefits of extending a developed application is the world wide community of developers and users. Today is a day for sharing posts!