Click here to Skip to main content
13,660,862 members
Click here to Skip to main content
Add your own
alternative version

Tagged as

Stats

2.9K views
1 bookmarked
Posted 31 Jan 2017
Licenced CPOL

Master Data Services Insufficient Memory Error

, 31 Jan 2017
Rate this:
Please Sign up or sign in to vote.
Master Data Services Insufficient Memory Error

A business case that requires the usage of Master Data Services finally landed in my desk. As part of delivering this business case, I had to install and configure SQL Server 2014 Master Data Services in production. I had previously installed and configured SQL Server Master Data Services in a test virtual machine environment so I was certain that the production setup would go smoothly. Boy, I was wrong :(.

Everything was going fine until I had to click the Explorer link (shown below) to manage master data and hierarchy relationships.

mds3

As the page was loading, I received the Error message [HttpWebRequest_WebException_Remoteserver] Arguments: NotFound…. as shown below:

mds1

I tried to ignore this message by click the OK button but when the error message went away, I received a blank page as shown below:

mds2

I then tried to access my MDS models by using Excel but I received an error message: The requested service “/service.svc/bhb” could not be activated as shown below:

mds8

With both browser and Excel add-in not allowing me to access my Master Data models, I was forced to futher investigate this issue.

So I tried following different ways to no avail:

  1. Verified Minimum Master Data Services Installation Requirements
  2. I ensured that applicationHost.config contains a location tag element
  3. In Excel, I tried specifying my MDS server with and without default.aspx (i.e., http://localhost:8080/default.aspx)
  4. Verified that IIS Handler Mappings supports *.svc extension

mds7

Finally, I remembered that in a previous lifetime, I used to masquerade as a Windows System Administrator. So, I logged onto the server hosting my MDS instance and went through the application error logs. Immediately, I noticed an error message coming from System.ServiceModel 4.0.0.0.

mds5

As I read through the details of a very-loooooong error message, I noticed an exception along the lines of “Memory gates checking failed because the free memory (1867968512 bytes) is less than 5%” as shown below:

mds6

I cleared the cache and increased total memory and bang! It worked! I could access the Explore page and successfully connect from Excel.

Conclusion

I haven’t yet explored Master Data Services in SQL Server 2016 but I know that Microsoft has made some improvements. I hope that one of those improvements is making sure that SQL Server developers/administrators don’t have to spend hours trying to troubleshoot an error that relates to Windows Server! The least they could do – is display a correct error message in the browser or Excel Add-In. I shouldn’t have to go through the logs to find out that this whole thing was about an insufficient memory.

I am hoping that Master Data Services in SQL Server 2016 easily returns an error message saying “Insufficient memory!”.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Sifiso W Ndlovu
Technical Lead select SIFISO
South Africa South Africa
Sifiso W. Ndlovu is a certified Microsoft professional who holds a Master’s degree in IT Management from the University of Johannesburg. He specializes on a range of enterprise and consumer technologies using open source and proprietary software. He is the member of the Johannesburg SQL User Group wherein he has made several presentations on User Group Meetings and SQL Saturday sessions. He has written for a number of publications including SQLShack.com and SQLServerCentral.com.

You may also be interested in...

Pro
Pro

Comments and Discussions

 
-- There are no messages in this forum --
Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web01-2016 | 2.8.180810.1 | Last Updated 31 Jan 2017
Article Copyright 2017 by Sifiso W Ndlovu
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid