You’re offline. This is a read only version of the page.
I am setting up a test system for Dynamics SL 2015. At the point of install the Web Apps, page 10 of the installation documentation does not match what I am actually seeing.
On the Configuration Console, the third tab on the left is Web Service Information asking for site name, physical location, whether you want https, port number and certificate. Where as the documentation lists it as the Web Service Selection and a bunch of check boxes and server name and system database name.
So trying to configure this, I am getting an error. Here is the configuration:
Site Information: SLWebServSite, C:\inetpub\wwwroot\slwa, https. port 444 with a wildcard ssl certificate
AppPool Info: SLWebServAppPool, created a domain user for the identity and registered it in the Trusted Web Service Account Maintenance in SL.
Web Service Info: Location https://sl.domain.com, port 808, use defaults protocols is checked.
Once I get to Verify, Everything checks out except for Can the Microsoft Dynamics SL Web Services be contacted and Are the Microsoft Dynamics SL Web Services of the correct version.
A verification Issue box opens with 9 lines of:
A needed Microsoft Dynamics SL Web Service could not be contacted. Please check all the configured addresses. Error - The remote server returned an error: (404) Not Found.
Followed by: A needed Microsoft Dynamics SL Web Service could not be contacted. Please check all the configured addresses. Error -No Connection could be made because the target machine actively refused it 192.168.100.16:808
Last line was: There was an error with the version of one of the Microsoft Dynamics SL Web Services. Exception has been thrown by the target of an invocation.
Any suggestions?
*This post is locked for comments
Is port 808 open for incoming traffic on the firewall for the server hosting the Web Service?
Additional information. Checking the Event Viewer, there are 10 Errors displaying:
WebHost failed to process a request.
Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/54957317
Exception: System.Web.HttpException (0x80004005): The service '/microsoft.dynamics.sl.webservices.quickqueryservice.svc' does not exist. ---> System.ServiceModel.EndpointNotFoundException: The service '/microsoft.dynamics.sl.webservices.quickqueryservice.svc' does not exist.
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.HandleRequest()
at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.BeginRequest()
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result)
Process Name: w3wp
Process ID: 2080
where the .svc is the only difference and cannot locate it.
In the browsers window, this is displayed:
Server Error in '/' Application.
The remote server returned an error: (404) Not Found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The remote server returned an error: (404) Not Found.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[WebException: The remote server returned an error: (404) Not Found.]
System.Net.HttpWebRequest.GetResponse() +8548300
System.ServiceModel.Channels.HttpChannelRequest.WaitForReply(TimeSpan timeout) +234
[EndpointNotFoundException: There was no endpoint listening at sl.domain.com/microsoft.dynamics.sl.webservices.session.loginforms.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.]
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +14483202
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +622
Microsoft.Dynamics.SL.Mobile.CommonModel.LoginFormsServiceReference.LoginFormsService.GetCompanyIDs(GetCompanyIDsRequest request) +0
Microsoft.Dynamics.SL.Mobile.CommonModel.LoginFormsServiceReference.LoginFormsServiceClient.GetCompanyIDs(Int32 page, Int32 size) +92
Microsoft.Dynamics.SL.Mobile.CommonModel.LoginFormsAdapter.GetCompanyIDs(LoginFormsServiceClient client) +131
Microsoft.Dynamics.SL.Mobile.CommonModel.LoginFormsAdapter.GetCompanyIDs() +143
Microsoft.Dynamics.SL.Mobile.LoginModel.GetCompanies(String selectedValues) +588
Microsoft.Dynamics.SL.Mobile.LoginModel..ctor() +20
Microsoft.Dynamics.SL.Mobile.HomeController.Index() +1857
lambda_method(Closure , ControllerBase , Object[] ) +79
System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) +247
System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +39
System.Web.Mvc.Async.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() +120
System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +452
System.Web.Mvc.Async.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) +15
System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +31
System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +230
System.Web.Mvc.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) +28
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +15
System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +53
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +15
System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) +42
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +15
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +606
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +288
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (