0x81020030: Invalid file name

I'm using the approach as described here to create a folder in SharePoint. For some reason I do get the following error message every now and then.

0x81020030:Invalid file name.
The file name you specified could not be used. It may be the name of an existing file or directory, or you may not have permission to access the file.

Apparently this does not have to do anything with an existing file or directory, or permissions to access the file. What in my case does cause this error, is the fact that the sharepoint listname has a length of larger than 50 characters.

Since this was not mentioned on the web according to my biggest friends Google and Bing, I thought it might help somebody else as well.

CRMAsyncService using 100% CPU v2

A while ago I wrote an article around how to handle the situation that the CRMAsyncService is consuming 99 to 100% of the CPU of the CRM Server. That solution has been written around the scenario that there are basically no workflows running. Obviously, there is the possibility as well that the amount of workflows is causing such behavior.

CRM is tested to be capable of handling thousands of active workflows. This of course does require a minimum set of hardware. If you are having a heavy load on the CRMASyncService due to the amount of workflows in combination with a relatively small server, then you'll need to change default settings of CRM to make sure that your system will remain active.

The default settings for workflow are set to a minimum of 1000 active workflows and maximum 2000 active workflows. This is fine for a system of at least 8GB ram, preferably even more. If you are running a server with for instance 4GB ram, then you should consider lowering these settings. Experience has learned that a setting of 100 for the minimum and 200 for the maximum setting is a good setting for a 4GB server. The server then isn't busy all the time with looking at too many workflows which causes timeouts, but instead only looks at a few and is able to finish these workflows in time.

Here's a small SQL script which you can run on your server to change this setting.

USE MSCRM_CONFIG
UPDATE DeploymentProperties SET IntColumn=100 where ColumnName = 'AsyncItemsInMemoryLow'
UPDATE DeploymentProperties SET IntColumn=200 where ColumnName = 'AsyncItemsInMemoryHigh'

ExactTarget Error: No results were received from the ExactTarget API

If you are working on extensive integration with ExactTarget from Dynamics CRM, then you might come accross this error message:

"Error during send processing." "ExactTarget.MSCRM4.BusinessLogic.Connector.ExactTargetSendException: No results were received from the ExactTarget API. Send status is unknown. ---> ExactTarget.MSCRM4.BusinessLogic.Connector.ExactTargetSendException: No results were received from the ExactTarget API. Send status is unknown.
at ExactTarget.MSCRM4.ConnectorService.v2.Sends.Crm4SendRequest.SendToExactTarget(Send send, Int32 recipientCount)
--- End of inner exception stack trace ---
at ExactTarget.MSCRM4.ConnectorService.v2.Sends.Crm4SendRequest.SendToExactTarget(Send send, Int32 recipientCount)
at ExactTarget.MSCRM4.ConnectorService.v2.Sends.Crm4SendRequest.Execute()
"

This error occures if you are creating an et_exacttargetjob (Exact Target Send) record by using a system user who is not an ExactTarget user. Make sure you are setting the owner attribute of the Exact Target Send record to the correct user.

It's just a short tip, but since by the time of posting this can't be found by any popular search engine, I'm sure that this will help you, or myself in the future.