Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 884412 - Last Review: March 23, 2007 - Revision: 1.2
You may receive the “Build failed†compiler error message in BizTalk Server 2004
When you compile a Microsoft BizTalk solution, you may receive
error messages that are similar to the following. This problem occurs in Microsoft BizTalk Server 2004.
Error message 1Build failed. Compiler for file type '*.xsd' failed. Value cannot be null.
Parameter name: pUnk
Error message 2Build failed. Compiler for file type '*.btp' failed. Value cannot be null.
Parameter name: pUnk
This problem occurs if all the following conditions are true:
- You run a Microsoft Windows Installer package on your BizTalk Server 2004. The Windows Installer package is created by using the BTSInstaller SDK sample.
- The Windows Installer package contains assemblies that are installed as part of BizTalk Server 2004.
- You subsequently run the uninstall routine that was created by using the Windows Installer package.
Note By default, the BTSInstaller SDK sample is installed in the following directory of your BizTalk Server 2004:
\Program Files\Microsoft BizTalk Server 2004\SDK\Utilities\BTSInstaller
To resolve this problem, do not create the Windows Installer package by using the BTSInstaller SDK sample. The BTSInstaller SDK sample contains assemblies that you do not want to use. These assemblies are installed as part of BizTalk Server 2004.
To make sure that the Windows Installer package excludes assemblies that are installed as part of BizTalk Server 2004, follow these steps:
- In Solution Explorer, click BTSInstaller.
- On the View menu, point to Editor, and then click File System.
- In the left pane, click Application Folder.
- Click all files that are listed in the Application folder except the following files:
- Project outputs
- Non-BizTalk product assemblies that are referenced by project outputs
- Other custom assemblies and their dependencies
- Btsicustomaction.dll
- Btsiassemblyorder.dll
- Bindingschema.xsd
- Btstd.xml
- In the Property pane, click to select the True check box in the Exclude box.
Notice that all the files that you select are excluded in the Windows Installer file.
When you use the BTSInstaller utility to add a BizTalk project to the Application folder, the BTSInstaller
utility automatically includes all referenced assemblies. This includes assemblies that you install as part of the BizTalk Server 2004 product in the Windows Installer file. After you deploy the Windows Installer file, you may later decide to uninstall it. The Windows Installer file also uninstalls the BizTalk Server 2004 assemblies. This can cause an inoperative BizTalk Server 2004 environment. If this problem occurs, you can use
Add or Remove Programs in Control Panel to repair your BizTalk Server 2004 installation.
To repair your BizTalk Server 2004 installation, follow these steps:
- Click Start, click Run, type Appwiz.cpl and then click OK.
- In the list of currently installed programs, click Microsoft BizTalk Server 2004, and then click Change/Remove.
- In the BizTalk Server 2004 Installation Wizard window, click Repair, and then click Next.
- After the BizTalk Server 2004 Installation Wizard repairs BizTalk Server 2004, click Finish to close the BizTalk Server 2004 Installation Wizard window.
The BizTalk Server 2004 installation is repaired.
For additional information about using the BTSInstaller utility for assembly deployment, visit the following Microsoft Developer Network (MSDN) Web site:
APPLIES TO
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Standard Edition
- Microsoft BizTalk Server 2004 Partner Edition
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate