Geeks With Blogs
Nigel Parker BizTalk 2004 Developer - Auckland, New Zealand,

This one will get you when you start working with large schema's like XCBL... http://www.xcb.org don't get me started on those recursive imports... Windows WMI isĀ used to enlist orchestrations when you use the BizTalk administration window on a server or a Nant build thanks Scott Colestock http://www.gotdotnet.com/workspaces/workspace.aspx?id=d66e1651-98e5-4ef4-9158-ac030a9b8a32... By defalult WMI is set to use a memory quota of 128MB and when you try to enlist an orchestration that uses more memory than this “Ka Boom” you will not be able to deploy your solution on the server ever again! OK so it's not that bad here is the solution....

1) Run "wbemtest" on cmd prompt
2) Connect to the "root" namespace (not "root\default", just "root")
3) Select Open Instance, and specify "__ProviderHostQuotaConfiguration=@"
4) Check "Local Only" for easier readability and you will see the threshold values
5) Change the MemoryPerHost value to something greater - eg. Double it (256 MB)
6) Save Property
7) Save Object
8) Exit

And to be on the safe side - restart :)

Posted on Saturday, October 16, 2004 4:08 AM BizTalk Bugs And Pitfalls | Back to top


Comments on this post: On Enlistment in BizTalk 2004 the WMI process is using more than the default memory quota of 128MB...

# re: On Enlistment in BizTalk 2004 the WMI process is using more than the default memory quota of 128MB...
Requesting Gravatar...
GREAT! I had this problem and your solution worked!

Many thanks for placing it online!

Ciao Ronald
Left by Ronald on Dec 14, 2006 5:05 AM

Your comment:
 (will show your gravatar)


Copyright © Nigel Parker | Powered by: GeeksWithBlogs.net