Consider the following two scenarios:
You use the SFTP adapter in BizTalk Server 2013.
You create two hosts with host handlers for the SFTP adapter.
You configure a receive location with user and password authentication with one host.
You test the previous situation, and it works well.
You change the host handler to another host.
You import a binding file with no password (vt=1) in the SFTP adapter receive location(s) or send port(s).
Note In the binding file, vt="1" means NULL. To set a password, you should use vt="8" that means string.
In these scenarios, the password will be set to the value NULL, and the CPU usage reaches 100 percent in the second host without any error message. If you manually set the password to blank string (not NULL) or use a wrong password, it won't cause a 100 percent CPU usage. However, it causes the adapter to silently fail with a usual CPU usage. Additionally, no errors are logged, and the receive location is kept active.
Cumulative update information
This issue was first fixed in the following cumulative update of BizTalk Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server.
For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and cumulative update support.