In my case, I installed Service Manager Self-Service Portal with the "HTTP" binding and behavior with the custom ports like 446 and 447. The portal was installed successfully but the Data Access Service was not able to run due to default configuration of "HTTPS binding and behavior" configured in the web.config file under the path "C:\inetpub\wwwroot\System Center Service Manager Portal\ServiceHost".
Error while opening the URL "http://scsmportal:446/ServiceHost/Services/DataAccessService.svc"-->
Server Error in '/ServiceHost' Application.
Could not find a base address that matches scheme https for the endpoint with binding CustomBinding.
Could not find a base address that matches scheme https for the endpoint with binding CustomBinding.
Registered base address schemes are [http].
-------------------------------------------------------------------------------
Solution-->
Default Configuration of Web.config file in my case-->
<services>
<!--Data Access service-->
<service behaviorConfiguration="DefaultHttpsServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.DataAccessService">
<!--Data Access service-->
<service behaviorConfiguration="DefaultHttpsServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.DataAccessService">
<!--Note:Recommended bindingConfiguration is DefaultHttpsBinding for production environment.
If bindingConfiguration=DefaultHttpsBinding then behaviorConfiguration should be DefaultHttpsServiceBehavior-->
<endpoint address="" binding="customBinding" bindingConfiguration="DefaultHttpsBinding"
contract="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.IDataAccessService">
</endpoint>
</service>
</services>
If bindingConfiguration=DefaultHttpsBinding then behaviorConfiguration should be DefaultHttpsServiceBehavior-->
<endpoint address="" binding="customBinding" bindingConfiguration="DefaultHttpsBinding"
contract="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.IDataAccessService">
</endpoint>
</service>
</services>
Corrected Configuration of Web.config file in my case-->
<services>
<!--Data Access service-->
<service behaviorConfiguration="DefaultHttpServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.DataAccessService">
<!--Note:Recommended bindingConfiguration is DefaultHttpsBinding for production environment.<!--Data Access service-->
<service behaviorConfiguration="DefaultHttpServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.DataAccessService">
If bindingConfiguration=DefaultHttpsBinding then behaviorConfiguration should be DefaultHttpsServiceBehavior.
If bindingConfiguration=DefaultHttpBinding then behaviorConfiguration should be DefaultHttpServiceBehavior-->
<endpoint address="" binding="customBinding" bindingConfiguration="DefaultHttpBinding"
contract="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.IDataAccessService">
</endpoint>
</service>
</services>
If bindingConfiguration=DefaultHttpBinding then behaviorConfiguration should be DefaultHttpServiceBehavior-->
<endpoint address="" binding="customBinding" bindingConfiguration="DefaultHttpBinding"
contract="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.IDataAccessService">
</endpoint>
</service>
</services>
Hope it helps!
If any improvement is required in this post, please post your comments/feedback so that we can provide much better solutions.
No comments:
Post a Comment