After restarting a server that has MDS on, I could no longer access MDS via the browser. This seemed very strange as I have restarted the server multiple times and it had never done this before.
Turns out the Application Pool had stopped for MDS. So I started it up and then it would stop again, frustrating me further.
Then is occurred to me that it was using my domain details and my password had changed. Then I went into the advanced settings of my MDS Application Pool to update my details under Identity.
And there we go, it works and I can access MDS again via the browser!
Hope this helps someone else with this error.
Recently a colleague and I had a discussion about which method is the best to use for backing up MDS (Master Data Services) for disaster recovery. We came to the conclusion it all depended on the SQL environment version you were recovering to. Below are the 2 different methods for backing up an MDS database.
- Fast to create, can backup specific versions
- Will always be able to deploy a model to a MDS install
- Can be automated via SSIS
- Can be restore to a server version that is +1, 0 and -1
- If you want to save backups of different models, then the models will have to be backed up separately.
- Security is not retained; it will have to be redone. Can take about 2 minutes per user. On a small model this should not be a problem, however, when scaled out it could be very time consuming.
- Saving more than one backup of a model would require a script/maintenance task to remove backups older than X amount of time.
When deploying the model, the option DeployClone must be used, not DeployNew. DeployNew will remove the MUID and therefore will not allow any changes to be deployed to that model at a later stage. DeployClone keeps it all intact and will allow for future updates.
- Security is retained
- Simple to set-up and maintain
- Easy to restore
- Maintenance tasks to clean up old backups
- Cannot be restored to a server version less than the current version.
The database backup for MDS can be scheduled just like other backups. You can use the maintenance wizard to set up the backup and clean up task on a schedule.
If you know what version the disaster recovery environment will be on, for example the same version as the current MDS server version or higher, then it is simpler to use the Database Backup method. If you are uncertain of what version the disaster recovery version will be then you would want to use the Model Backup method in case you have to restore to a version less than the current MDS server version.
Hope this helps you to choose what is best suited for your environment!
Special thanks to Janlo Du Toit for the discussion on these methods 🙂
This is just a high-level overview of the prerequisites that are needed for IIS. You need to have IIS installed on the server you are installing MDS on in order for MDS to work. The easiest way to check if you have all the prerequisites for IIS installed is to open up Master Data Services Configuration Manager.
A warning screen will appear if you do not have all the prerequisites installed for IIS. This warning message will give you a link to check what is needed for IIS.
First you will need to install the Role and Role Services for IIS:
You can use Server Manager, which is available in the Microsoft Management Console (MMC), to install the Web Server (IIS) role, and required role services.
- Internet Information Services
- Web Management Tools
- IIS Management Console
- World Wide Web Services
- Application Development
- .NET Extensibility 3.5
- .NET Extensibility 4.5
- NET 3.5
- NET 4.5
- ISAPI Extensions
- ISAPI Filters
- Common HTTP Features
- Default Document
- Directory Browsing
- HTTP Errors
- Static Content
- [Note: Do not install WebDAV Publishing]
- Health and Diagnostics
- HTTP Logging
- Request Monitor
- Static Content Compression
- Request Filtering
- Windows Authentication
Next you will need to install the features IIS requires in order to run:
You can use the Server Manager to install the below features.
- .NET Framework 3.5 (includes .NET 2.0 and 3.0)
- .NET Framework 4.5 Advanced Services
- NET 4.5
- WCF Services
- HTTP Activation [Note: This is required.]
- TCP Port Sharing
- Windows Process Activation Service
- Process Model
- .NET Environment
- Configuration APIs
Once all the prerequisites for IIS are installed you will see a green tick in Master Data Services Configuration Manager.