I was trying to add those functoids by browsing the exact dll, but I could not find what is the DLLs name. But I got back all the functoids, after I clicked the Reset button in the Customize Toolbox dialog box. It must have reset all the changes in the other tabs as well.
Wednesday, November 28, 2007
Functoids in Toolbox Empty?
Couple of day ago, I stumbled up with this problem: Functoids are not there in the toolbox while I was creating a BizTalk Map. When I right-clicked the toolbox and selected add items, I found the Functoid tab of the Customize Toolbox dialog box is empty.
Monday, November 5, 2007
Problem with FileSystemWatcher generating FileCreated event
Problem with FileSystemWatcher generating FileCreated event:
I have a windows service which picks up a file from a folder-Request, then does some processing and writes to another folder-Response. I have implemented FileSystemWatcher component in the windows service to watch for new files in the Request folder and in FileCreated event handler, I wrote the code to process the file. It works perfectly fine when I manually drop the test file in the Request folder. But when my BizTalk application writes the same file in the Request folder, the windows service fails to process the file.
This seems to be an issue I could not find any documentation from Microsoft. The exact problem, what I could guess, is: either the FileSystemWatcher generates the FileCreated event at the time of File handler is created but the file is still being written and yet to be closed. Or the file is written but lock is yet to be released.
After some experimentation, I could find a work around: Use a few seconds delay in the first line of the FileCreated event handler:
System.Threading.Thread.Sleep(3000);
This gives enough time to release the file lock, and Windows service can pick up the file and process successfully.
I have a windows service which picks up a file from a folder-Request, then does some processing and writes to another folder-Response. I have implemented FileSystemWatcher component in the windows service to watch for new files in the Request folder and in FileCreated event handler, I wrote the code to process the file. It works perfectly fine when I manually drop the test file in the Request folder. But when my BizTalk application writes the same file in the Request folder, the windows service fails to process the file.
This seems to be an issue I could not find any documentation from Microsoft. The exact problem, what I could guess, is: either the FileSystemWatcher generates the FileCreated event at the time of File handler is created but the file is still being written and yet to be closed. Or the file is written but lock is yet to be released.
After some experimentation, I could find a work around: Use a few seconds delay in the first line of the FileCreated event handler:
System.Threading.Thread.Sleep(3000);
This gives enough time to release the file lock, and Windows service can pick up the file and process successfully.
Thursday, November 1, 2007
The method “Start” of the BizTalk Server WMI provider class “MSBTS_HostInstance”
I am still wondering why I get this error message when I try to start an orchestration using Visual Studio. In your BT explorer when you right click on an orchestration and select start from pop-up menu, you will get BisTalk Express – Start dialog box where all the check boxes are selected by default.
Unable to update BizTalk Host:
Failed to execute method “Start”.
The method “Start” of the BizTalk Server WMI provider class “MSBTS_HostInstance” cannot be executed because of a failure to retrieve the class.
Not Supported.
Failed to execute method “Start”.
The method “Start” of the BizTalk Server WMI provider class “MSBTS_HostInstance” cannot be executed because of a failure to retrieve the class.
Not Supported.

I suspect Windows WMI engine not able to execute the scripts which are made available in the BizTalk folders C:\Program Files\Microsoft BizTalk Server 2004\SDK\Samples\Admin\WMI\
But you can start your orchestration if you unselect the BizTalk Host check box, in the get BizTalk Express – Start dialog box. This will not restart your host, but you can restart the Host later.
But you can start your orchestration if you unselect the BizTalk Host check box, in the get BizTalk Express – Start dialog box. This will not restart your host, but you can restart the Host later.

And you can restart your BizTalk Host by using Service Window.

If any one knows it better, pls. let me know why this problem occurs.
Subscribe to:
Comments (Atom)