chillijam.co.uk » BizTalk http://chillijam.co.uk Thu, 28 Jan 2021 10:32:11 +0000 en-US hourly 1 https://wordpress.org/?v=4.0.38 BizTalk EDI Problems http://chillijam.co.uk/2006/01/03/biztalk-edi-problems/ http://chillijam.co.uk/2006/01/03/biztalk-edi-problems/#comments Tue, 03 Jan 2006 13:14:54 +0000 http://playingwithanimport.wordpress.com/2006/01/03/biztalk-edi-problems/ Continue reading BizTalk EDI Problems →]]> I have had a few problems with Biztalk this morning. I’ve been trying to validate an EDI instance file against one of the standard EDI schemas supplied with Biztalk. It was bahaving strangely. Initially, the error I was presented with was :

Could not find file “C:\DOCUME~1\USER1\LOCALS~1\Temp\validins.xml”.

Confused, I tried to use the “Generate Instance” function to try to see what was going wrong. This time, I got another error :

XSD2EDI failed to convert XSD: Compiling repository failed

A quick Google on this turned up this page in Microsoft’s knowledge base. In short, if you are logged on to the BT server with a domain account, and the EDI service is running with a machine-local account, you need to ensure that your domain account is in the “EDI Subsystem Users” group on the BT server.

As it happens, my schema instance failed to validate, but that’s life, I suppose.

Technorati Tags: , , ,

]]> http://chillijam.co.uk/2006/01/03/biztalk-edi-problems/feed/ 0 WMI Out Of Memory issues http://chillijam.co.uk/2005/07/25/wmi-out-of-memory-issues/ http://chillijam.co.uk/2005/07/25/wmi-out-of-memory-issues/#comments Mon, 25 Jul 2005 12:52:42 +0000 http://playingwithanimport.wordpress.com/2005/07/25/wmi-out-of-memory-issues/ Continue reading WMI Out Of Memory issues →]]> I have been working on an automated way of deploying BizTalk assemblies, orchestrations and bindings without having to use NAnt or MSBuild this week. It has thrown up a problem that lots of people must have if they are doing a similar thing.

Many times, my scripts would fail periodically, but not in predictable places. After looking at the logs I generate, I noticed that there were a lot of “out of memory” errors caused by WMI operations. I needed a quick fix, so I came up with this (horrible and hacky) workaround.

Before each section of code, restart the “winmgmt” service. That’s it. The scripts now work flawlessly – or at least, they fail in predictable places now.

**EDIT**

I have just been pointed towards this page which details how to increase the amount of memory available to WMI from its default of 128MB.

]]> http://chillijam.co.uk/2005/07/25/wmi-out-of-memory-issues/feed/ 0