I've (fortunately) ended up with a new notebook recently and had to reinstall everything. One problem I ran into was with Master Data Services. The config program seemed happy but it shouldn't have been. What threw me was that it seemed to have a dependency check for IIS 7, etc. while configuring MDS. That led me to think I'd already configured IIS appropriately. I hadn't and when I tried to use the site, I got the above error. IIS needed to have the following:
Common HTTP Features
· Static Content
· Default Document
· Directory Browsing
· HTTP Errors
· .NET Extensibility
· ISAPI Extensions
· ISAPI Filters
Health and Diagnostics
· HTTP Logging
· Request Monitor
· Windows Authentication
· Request Filtering
· Static Content Compression
· IIS Management Console
Plus NET Framework 3.0 Features
· WCF Activation
· HTTP Activation
· Non-HTTP Activation
Plus Windows PowerShell
Plus Windows Process Activation Service
· Process Model
· .NET Environment
· Configuration APIs
I'm sure that'll be covered in a "readme" somewhere (that sadly we often neglect to read each time we install) but I was lulled into a false sense of security by the dependency check in the installer. It would be great to see it upgraded to fully test for dependencies.
4 thoughts on “SQL Server 2008 R2: MDS setup HTTP Error 500.19 – Internal Server Error – Error Code 0x80070021”
Sorry that you encountered this issue when configuring MDS, and thank you for your feedback on how to make this better in the product.
As you found, the IIS check in Master Data Services Configuration Manager is to verify that the version of IIS is supported, not that the individual features and role services are installed. You might find the following section of SQL Server Books Online helpful to understand the requirements and process (particularly the Web Application Requirements topic): http://msdn.microsoft.com/en-us/library/ee633752.aspx.
Also, check out the product team blog for updates and info about MDS: http://sqlblog.com/blogs/mds_team/default.aspx.
Have you checked that the web app can access the area where mds web site is located?
you could try to give all users access to the "master data services" under ProgramFiles and rerun the configuration wizard
It's working fine for me. I'm just noting it on the blog in case someone else has the problem. I was surprised that the dependency check worked with so many things not configured. It seems to just check that IIS7 is there but not whether things like ASP.NET are even enabled.
Beautiful, beautiful post, Greg. Saved me a ton of time — although the above comments sound like the MS documentation covers these requirements somewhere, I certainly didn't find an answer there, after quite a bit of looking. Luckily, I ran across yours … Working great now.