by Rene Brauwers | Mar 23, 2013 | BizTalk Community Blogs via Syndication
As most of you, I downloaded the final pieces of BizTalk Server 2013 as soon as it was available on MSDN. Once I downloaded it, I decided to setup a clean BizTalk 2013 Development Machine. This post will highlight the issues I encountered during installation and configuration and how I resolved them.
First of a brief highlight of my machine (Single-Server) configuration
* Windows Server 2012
* SQL Server 2013
* One instance for BizTalk MessageBoxDb
* One instance for all other BizTalk databases
* Visual Studio 2012
* BizTalk Server 2013
* Server Memory 8GB
* Disk Space 40Gb
Below the issues I encountered and how I resolved them.
Issue #1: Installing BizTalk Server
Error encountered: Missing file ‘MSVCP100.dll’
Resolution
- Download and install Microsoft Visual C++ 2010 Redistributable Package (both x64 as x86)
Issue #2: BizTalk Configuration – BAM Tools
Error encountered: Could not install BAM Tools
Resolution
- install SQL Server 2005 Notification Services
x64 – http://download.microsoft.com/download/4/4/D/44DBDE61-B385-4FC2-A67D-48053B8F9FAD/SQLServer2005_NS_x64.msi
x86 – http://download.microsoft.com/download/4/4/D/44DBDE61-B385-4FC2-A67D-48053B8F9FAD/SQLServer2005_NS.msi
- set up database to use database-mail
- configure BAM Alerts
Issue #3: BizTalk Configuration – BAM Portal
Error encountered: Could not install BAM Portal -> error with regards to “BAM Management Web Service User”
Error thrown: “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.”
Actual exception: Log indicated ‘Cannot alter the role ‘NSSubscriberAdmin’, because it does not exist or you do not have permission.’
Resolution
- Manually Add NSSubscriberAdmin DatabaseRole to BAM Alert Application Database
END Result
Well this was a quick post, but I hope that it might help you out; if you encounter the same issues
Cheers
René
by Rene Brauwers | Sep 19, 2011 | BizTalk Community Blogs via Syndication
Last week during the BUILD conference a developer preview of Both Windows 8 and Windows Server 8 was released. Once released I’ve decided to give it a go and install and perform a basic configuration (without BAM / EDI) of BizTalk Server 2010 on Windows 8 (note: not Windows Server 8).
Below a list of issues I encountered and how to resolve these issues.
Prerequisites
Obtain the Windows 8 developer preview build
Obtain Microsoft BizTalk Server 2010
Ensure that you have a dedicated server available with SQL Server 2008R2.
Hook up your Windows 8 to machine to your Active Directory (this way you can use your AD BizTalk service accounts etc.)
Environment
Encountered Issues while installing
Well to be perfectly honest the only issue I encountered during installation of BizTalk Server 2010 was the fact that I got about 10+ windows update screens which all prompted me to go and install the .Net Framework 3.5.1 Features; well I closed all the windows except for one and let windows update continue.
Note: For the BizTalk pre-requisites I simple pointed to the cab file , which I already downloaded previously.
Encountered Issues while configuring
Configuring BizTalk Server 2010 was a bit more of a challenge although everything up to ‘Configuring the BizTalk Server Runtime’ went off without any problems.
However once it was time to configure the runtime it gave me a an exception informing me that the server could not communicate with the SSO and that it might have to do with the Distributed Transaction Coordinator; Well this was not the issue, as I had configured it on both servers (on the SQL Server box and on the BizTalk Box).
So next stop was looking into the windows services and then especially the Enterprise Single Sign On Service; well the service was up and running. So I stopped and started it and tried to configure the BizTalk Server Runtime once again; however I still got the same error.
Next stop going back to the windows services and this time
I tried an elevated account on the Enterprise Single Sign On Service; but hey you guessed it; still got the same error.
So; not giving up I went back to the Enterprise Single Sign On service and put everything back to it’s original state (that is use the dedicated sso service account). Well once I tried to start the service again it suddenly gave me an error indicating that there were some RPC issues… Hmmm, so I went and had a look at that particular service and noticed that it was up and running. Restarting it did not throw any other exceptions and that’s when I noticed that the service ‘RpcLocator Service’ was not running. Bingo! Enabling this service resolved the SSO issue and I was able to further configure BizTalk Server 2010.
Conclusion
BizTalk 2010 can be installed and configured on the Windows 8 Developer Preview Release; however before installing and configuring ensure that
You’ve configured the Distributed Transaction Coordinator on both the SQL Server Box as well as the Windows 8 Box
Ensure that the ‘RpcLocator Service’ is up and running.
Please note: So far I’ve only installed and configured BizTalk 2010 on Windows 8. I’ve not actually played around with sample applications etc.
Screenshots:
BizTalk Administrator ‘Pinned’ to Metro
BizTalk Server Configuration
BizTalk Administrator Console
Cheers
René
