Friday, August 04, 2006

BizTalk 2004 on one Virtual machine

While configuring BizTalk 2004 on one Virtual machine (on windows 2003), and SQL Server is located remotely on another VM, I came across this kind of exception, which doesn’t give you much of information, except that the transaction has already been implicitly or explicitly committed or aborted, search on google doesn’t either give you any information, hence I have listed it over here,

Error:
c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btswmi.cpp(266): FAILED hr = c0c025b3

[7:30:26 PM Error BtsCfg] Failed to deploy BizTalk system assembly "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.BizTalk.GlobalPropertySchemas.dll".

Unspecified exception: The transaction has already been implicitly or explicitly committed or aborted.

[7:33:09 PM Info ConfigFramework] Showing MessageBox with text: Failed to deploy BizTalk system assembly "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.BizTalk.GlobalPropertySchemas.dll".
Unspecified exception: The transaction has already been implicitly or explicitly committed or aborted.

Solution:
The Solution is to provide the appropriate domain user accounts for BizTalk configuration wizard, the installer should have access to the SQL Server BizTalk databases. Initially I thought it might be some issue with the MSDTC network clients which were already enabled, how ever it is purely based on the domain accounts which were not yet been created on SQL Server and BizTalk machines..

Error:
Config error: Failed to deploy Biztalk system assembly... DefaultPipelines.dll
When running the config wizard for BizTalk2004 (on windows 2003) the following error occurred:
Failed to deploy Biztalk system assembly "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.BizTalk.DefaultPipelines.dll". Unspecified exception: Unable to generate a temporary class (result=1).
error CS2001: Source file 'C:\WINDOWS\TEMP\dbqvusoe.0.cs' could not be found.
error CS2008: No inputs specified.
Solution:
The solution is to give the 'NETWORK SERVICE' user read and write access to the c:\windows\temp directory.