QAID # 14142 Published
Question / Problem:
When attempting to run the new Server Scheduler service with an Admin account, the following error is occurring:
"There was no endpoint listening at net.pipe://localhost/BPP1-73e4d44d-6e80- 4710-904d-8b747b81bc5b that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details…".
How can this issue be resolved?
Answer / Solution:
Please see QAID 14125 for the common resolution of this issue.
If the Server Scheduler service is verified to be running with an Admin account and the error is still occurring, this could be a deep level policy issue that could be preventing the service from correctly starting.
There is also a Microsoft .NET bug related to verifying an application’s authenticity related to the .NET and CLR processing architectures. Please see QAID 13662 in regards to a workaround for this .NET bug.
In one case, a call to
crl.verisign.net was present in a Process Monitor trace indicating that the process was attempting to download certificates from Verisign in relation to the .NET authenticity check mentioned above. The machine was located in a hardened environment with no Internet access, which prevented the process from obtaining the certificate. Please follow the workaround in QAID 13662 to disable this check.