Closed rroman81 closed 5 years ago
Not sure about the community-provided solution, but there will be a built-in fix for this in the next release of Rocks.
@rroman81 Can you try the latest VSIX build here and let me know if it solves the problem?
https://ci.appveyor.com/project/JakobChristensen/sitecore-rocks/builds/19888982/artifacts
let me try that tonight. Thanks.
On Tue, Oct 30, 2018 at 7:36 AM Nick Wesselman notifications@github.com wrote:
@rroman81 https://github.com/rroman81 Can you try the latest VSIX build here and let me know if it solves the problem?
https://ci.appveyor.com/project/JakobChristensen/sitecore-rocks/builds/19888982/artifacts
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JakobChristensen/Sitecore.Rocks/issues/82#issuecomment-434324970, or mute the thread https://github.com/notifications/unsubscribe-auth/AA5TkkLJiPiru4fMFGXzVhFR89oUG3vaks5uqGPPgaJpZM4XN2zv .
-- Thank you,
Roman Rozinov
This should be resolved in 2.1.126.
I have implemented the web.config change listed in Sitecore Rocks with Sitecore 9, and ensured that "UseDefaultWebProxy" is unchecked. I can also confirm that asmx service endpoint is available via browser once I login to the sitecore instance. However, I am still getting the issue with connecting. I am still getting 'Got a "No Service" error." after attempting to update server components. I am using Sitecore Rocks v2.1.86. What other type of diagnostics can I turn on to understand the connectivity issue?