BTSTask can sometimes throw an error relating to .NET versions when you attempt to export or import bindings for ActiveADAPTER send ports and receive locations. Try the following: In your BTSTask.exe.config file (located in your Program Files BizTalk folder), add the following just under <configuration> tag: <startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.0" /> </startup>
If you receive duplicate messages in CHANGES ONLY query and compare mode, the most likely cause is that the query interval you have set is too short for the scope of your query. To diagnose, increase your query interval significantly and see if the duplicates no longer occur. If you absolutely require a short query...
This error is caused if you include an ampersand directly in your query string. If you build queries in ADSIEdit they might look like: (&(objectCategory=user)(sAMAccountName=Jane)) The “&” character is not allowed in XML. Instead use “&” For example: <Directives WhereToBind="LDAP://DC2008R2/CN=Users,DC=test,DC=com" SearchScope="onelevel" Filter="(&(objectCategory=user)(sAMAccountName=Jane))" PropertiesToReturn="distinguishedName"/>
This error most commonly occurs when you are attempting to do something that the server’s security policy forbids. For example, check that you have assigned the user a password in a previous message that complies with any password complexity and history policies you may have in your domain.
This error is often due to security permissions problems. Check if the receive location works fine when pointing to a different container (e.g. the Users container LDAP://CN=Users,DC=test,DC=com). If so:
This can happen if you are using a createobject message and the WhereToBind value in your message or overrides does not match the EqualToValue in your <Target> tag. Check that these both contain a reference to the correct container. For example, to create an object in the Users container of test.com these should be: WhereToBind=”LDAP://CN=Users,DC=test,DC=com”...
This error usually results from a permissions problem. Check the permissions on the account you are using for your BizTalk Host Instance, or in your Authentication Override. To diagnose, try the operation again using an account with administrator permissions.
This error most commonly occurs when the server used in direct server binding cannot be contacted. It can be caused by: