FTP - "Root element is missing"

After some problems with remote FTP and disk quota on login user, I started receiving some errors "Root element is missing" on the send port, but the send port was set to pass through...

I stopped the orchestration and send port, sat sent pipeline to xml and apply. And back to pass though and apply. Started the ports and orchestration and I works again ;-)

Build hangs

Suddenly I had a problem with build from Visual Studio. It hangs!

But If I hide or close the "output" window during builds - its working - but why?!?!?!

FTP adapter error - "parsing the remote folder listing"

Be aware NOT to specify the File Mask without any mask.

I had a receive location with transport type FTP, where the File Mask was a specific filename.

The receive location kept shutting down with the error:

"The adapter "FTP" raised an error message. Details "A failure occurred when parsing the remote folder listing. "."

When I added an "*" before the filename - It worked :-)

Port exception in orchestrations

How to handle transmission errors on a port in an orchestration ?!

I added a send port (FTP) to an orchestration and after the send port I updated a log. But the orchestration continued even the send port failed (i.e. FTP server down).

The solution was to add a scope shape including a generic exception handler, around the send port. But it did not work - the exception was newer through.

What I forgot was to change Delivery Notification on the send port to "Transmitted".

That did the trick :-)

Encoding - pipelines

Did you know that pipeline-files (*.btp) is XML files ?

I had to change Target charset on a outgoing pipeline. Our problem was to send out files in Dos format (also known as ibm850). But I couldn’t choose codepage 850 in the pipeline designer I Visual Studio.

Strange – In the pipeline designer you can only choose about 20 charsets, but in fact BizTalk is supporting the same charsets as .NET. That means a lot more !

The solution is to open the .btp file in ex. Notepad. Then replace the value under TargetCharset and TargetCodePage. For example:







It worked! Afterwards the right Target charset was showing in the Pipeline designer J

Huge transaction log

I had some problems with a huge transaction log on BizTalkMsgBoxDb – 32 Gb !

Backup was taken directly of the data files, but even if I created a transaction log backup of the database, the file kept growing, The problem was that BizTalk never stopped using the database, sow there was no space to shrink the base after the backup.

The solution was to change the backup job. I added a new step after the backup step: “DBCC SHRINKFILE (BizTalkMsgBoxDb_log, 0)"

But why ?

Hi! - Purpose with this blog is to collect my experiences with BizTalk 2004 and 2006 over the last couple of years. I hope it be helpful to someone!

Best regards-Jørn