No Master Data Services instance section exists

Question

All,

     After getting in trouble access to my Master Data application (didn't want to let me access the Manage page) I simply decided to perform a fresh cleanup :

• In IIS remove my MDS site
• In IIS remove the MDS Application Pool
• Windows Explorer remove the WebApplication folder
• Re-launch teh Master data service installer
• Select the option Repair
• WebApplication folder is properly recreated
• The MD configuration tool popups and go to the Web Configuration step
• Select "Default Web Site", Create Application "MDS", Select my data base and enable Web Services

   After doing all that (this was working previously) I get teh following error message when I click Apply :

No master Data Services instance section exists.

   Any hints on what that mean and how to solve it.

Thanks

Pascal.

Answer 1

Here we are .... After looking around in the various error message I realize that the MDS web site was created with a Virtual Directory pointing to <C:\Program Files\Microsoft SQL Server\Master Data Services\WebApplication> when in fact my original installation of Master Data Services was on D Drive <D:\PrgFiles\Microsoft SQL Server\Master Data Services>

After changing the Site Virtual Path, things are more or less back to normal ... meaning I can access the Web Application.

However the site can not be found through teh Master data service configuration ....  (it does not appears when I select "Default Web Site" in the config. panel)

Any hints why ?

P.

Answer 2

Hello

did you check in MDS Web.Config if everything seems ok ?

---

Note: Please vote/mark the post as answered if it answers your question/helps to solve your problem. _________________________________________________________ Regards, Xavier Averbouch, Consultant, Avanade France

Answer 3

Xavave,

     I double checked the web.config and everything seems to be fine.  It includes a <masterDataServices> tag with correct info (Cf. below).

     Maybe I still miss something elsewhere but can't figure out. Not such as problem as long as the MDS is working :-)

 <masterDataServices>
  <instance virtualPath="MDS" siteName="Default Web Site" connectionName="MDS2"
   serviceName="MDS2" />
 </masterDataServices>

Pascal.

Answer 4

Pascal,

for information, i've got that:

 

<masterDataServices>
 <instance virtualPath="" siteName="MDS" connectionName="MDS"
 serviceName="MDS1" />
 </masterDataServices>
<connectionStrings>
 <add name="defaultMdsConnection" connectionString="Data Source=(local);Initial Catalog=MDM_Sample;Integrated Security=True;Connect Timeout=3600" />
 <add name="MDS" connectionString="Data Source=MYCOMPUTER;Initial Catalog=MDS;Integrated Security=True;Connect Timeout=3600" />
 </connectionStrings>
<!--The location of the temporary ASP.NET compilation directory will be filled in by the Configuration Manager.-->
		<!--The temporary directory for compilation will reside at the root of the Master Data Services install path.-->
		<compilation tempDirectory="C:\Program Files\Microsoft SQL Server\Master Data Services\MDSTempDir"
...

<system.serviceModel>
		<behaviors>
			<serviceBehaviors>
				<behavior name="mdsWsHttpBehavior">
					<!-- Enable to allow clients to retrieve metadata (WSDL) about the service endpoints. -->
					<!-- If not using SSL (httpGetEnabled="true" httpsGetEnabled="false") to expose service metadata.-->
					<!-- If SSL is being used (httpGetEnabled="false" httpsGetEnabled="true") to expose service metadata.-->
					<serviceMetadata httpGetEnabled="false" httpsGetEnabled="false"/>
					<!-- Enable to allow clients to see service exception details -->
					<serviceDebug includeExceptionDetailInFaults="false"/>
					<serviceThrottling maxConcurrentSessions="400"/>
					<dataContractSerializer maxItemsInObjectGraph="999999999"/>
				</behavior>
			</serviceBehaviors>
		</behaviors>
		<bindings>
			<wsHttpBinding>
				<binding name="mdsWsHttpBinding" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647">
					<readerQuotas maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxDepth="2147483647" maxNameTableCharCount="2147483647" maxStringContentLength="2147483647"/>
					<!-- Non-SSL implementations.-->
					<security mode="Message">
						<message clientCredentialType="Windows"/>
					</security>
					<!-- SSL implementations -->
					<!--<security mode="Transport">-->
					<!--<message clientCredentialType="Windows" />-->
					<!--</security>-->
				</binding>
			</wsHttpBinding>
		</bindings>

<services> <service behaviorConfiguration="mdsWsHttpBehavior" name="Microsoft.MasterDataServices.Services.Service">

 <endpoint binding="wsHttpBinding" bindingConfiguration="mdsWsHttpBinding" bindingNamespace="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09" contract="Microsoft.MasterDataServices.Services.ServiceContracts.IService" />

 </service>

 <service behaviorConfiguration="mdsWsHttpBehavior" name="MDS1">

 <clear />

 <endpoint binding="wsHttpBinding" bindingConfiguration="mdsWsHttpBinding" bindingNamespace="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09" contract="Microsoft.MasterDataServices.Services.ServiceContracts.IService" />
 </service> 
</services>

</system.serviceModel>

 

---

Note: Please vote/mark the post as answered if it answers your question/helps to solve your problem. _________________________________________________________ Regards, Xavier Averbouch, Consultant, Avanade France

Answer 5

Xavier,

 

   Thanks. Indeed I have similar fuile content (except a few names there and there specific to my instance, disk etc ..)

   At this stage I'm not looking forwad to fix it as everythings seems to work properly despite the UI configuration problem, and I do not want to take the risk to break everything one more time :-)

 

P.

---

---- ----------- Pascal. ---------------