Neil Thompson

BizTalk | .NET | SQL |

  Home  |   Contact  |   Syndication    |   Login
  15 Posts | 20 Stories | 31 Comments | 66 Trackbacks

News

Article Categories

Archives

Post Categories

Fav BizTalk Blogs

BizTalk Server 2004

An error occurred in the File System connector. Check the details.Cant make a connection to <%path to edi pickup here%>. Errormessage: The operation cannot be performed because a network component is not started or because a specified name cannot be used.Foldername: <%path to edi pickup here%>. , Errormessage: The operation cannot be performed because a network component is not started or because a specified name cannot be used.


My team has answered the following problem many times, it seems to be a very common mistake. The problem is that the account that the biztalk host is running under (usually BtsInstanceHost) does not have enough permissions on the directories acting as the send/receive locations for the file adapter.


Myself and a colleague just spent an embarassing amount of time tracking down a very obscure error: 'Microsoft.XLANGs.RuntimeTypes.XmlDocumentSerializationProxy' does not contain a definition for 'LoadXml'


Recently I had some problems creating ports in our Functional Test environment. Like all of us, I use BTS Explorer in development and had a few problems when I tried to use the (Excellent) Administration PowerToy written by Paul Somers


This is pretty basic stuff, but it is a really common mistake. Using .NET classes in the BTS RuleEngine (RE) is pretty simple until you actually try to run them. The problem always seem to come down to creating an instance of the class that you are referencing in the Vocabulary/ Function etc.


Please remember that when you use the expression shape in BTS 2004 you are NOT programming in C#, rather, you are programming in xLang/s. Do whatever you have to in order to remember this, if you don't like calling it Xlang, call it X#, or C# 'lite'.


Debugging BizTalk is pretty simple from within HAT. See HAT BizTalk debugging for further info on that, it should be everywhere. Things get only slightly more complicated when you want to debug a .NET component that is being invoked from an orchestration.


Recently, I had a requirement of generating a very large xml instance (1,000,000 + rows ), and to complicate things I needed to be able to generate unique values over the key feild. True to form, I went to the newsgroups because I was not aware of how to use the "Generate Instance" functionality to ...