The information in this article applies to:
Product: Metastorm BPM Version: 9 Issue
- Metastorm Deployment service does not start if BizTalk Toolkit 2.0 is installed.
Cause
- Metastorm Deployment service uses the Microsoft module Microsoft.Practices.EnterpriseLibrary3.dll that is a merged assembly of the Microsoft.Practices.EnterpriseLibrary.dll. BizTalk Toolkit 2.0 uses the Microsoft.Practices.EnterpriseLibrary DLLs at runtime. These are registered to GAC. When the Metastorm Deployment Service is started, these DLLs are installed rather than the merged enterprise library. This causes the service not to start.
Diagnosis
- The tool used to identify this issue is the Assembly Binding Log Viewer (Fuslogvw.exe.)
![BizTalkImage1.jpg](https://us.v-cdn.net/6030023/uploads/appworks_attachments/3401220.jpg "BizTalkImage1.jpg")
- Click Settings… and the screen below will be displayed.
![BizTalk2.jpg](https://us.v-cdn.net/6030023/uploads/appworks_attachments/3401221.jpg "BizTalk2.jpg")
- Select ‘Log all binds to disk.’
- Check ‘Enable custom log path’ and enter the path to an existing directory that has appropriate permissions enabled.
- Start the Metastorm Deployment service and you should see a screen similar to the one below.
![BizTalk3.jpg](https://us.v-cdn.net/6030023/uploads/appworks_attachments/3401222.jpg "BizTalk3.jpg")
- Investigate the files deployed and the dependencies.
- You can also check the physical files in the GAC – C:\\WINDOWS\\assembly.
Resolution
- Uninstall BizTalk Toolkit 2.0 to remove the DLL dependency.
|