Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sitecore Rocks Connection not working with Sitecore 9.3 #138

Open
jaffal83 opened this issue Dec 3, 2019 · 12 comments
Open

Sitecore Rocks Connection not working with Sitecore 9.3 #138

jaffal83 opened this issue Dec 3, 2019 · 12 comments

Comments

@jaffal83
Copy link

jaffal83 commented Dec 3, 2019

I have the following error when trying to make a connection to Sitecore 9.3 instance

image

I figured that it could be because 9.3 accepts secure connections only but when I tried the connection work but I had another problem

image

The first node is for 9.3 Instance when I try to open any database I have an error message that it's unavailable and don't get it's children.The second node is for 9.2 which works as expected. Is there an update for Sitecore Rocks to work with 9.3, it doesn't show up in VS.

@Assimilate69
Copy link

I tried adding a binding to http. that allowed me to connect but then I get:
image

@nickwesselman
Copy link
Contributor

Hi @jaffal83 and @Assimilate69 -- I've published a pre-release with Sitecore 9.3 support. Can you try installing the VSIX, updating your server components, and let me know if you still encounter any issues?

https://github.com/Sitecore/Sitecore.Rocks/releases/tag/3.0.284

@nickwesselman
Copy link
Contributor

A workaround is in place, but the main issue driving this is the support for "built-in" Sitecore serialization in Rocks. I question whether anyone actually uses this, and whether we should actually just remove this functionality rather than trying to fix?

@Assimilate69
Copy link

@nickwesselman I have installed version 3.0.284 and it is now expanding the tree in Sitecore Explorer. Thank you for doing this fix so quickly.

@felipemarcolino
Copy link

I had the very same problem and installed this 3.0.284 fix from here and it worked fine! Thank you!

@jaffal83
Copy link
Author

@nickwesselman it worked for me as well, Thanks alot for the quick fix

@nickwesselman
Copy link
Contributor

Hello @jaffal83 @felipemarcolino @Assimilate69 -- try out the latest pre-release when you have a moment, it fixes serialization functionality on 9.3.

https://github.com/Sitecore/Sitecore.Rocks/releases/tag/4.0.290

nickwesselman added a commit that referenced this issue Dec 31, 2019
@sbenhoff007
Copy link

@nickwesselman I installed Sitecore Rocks from the VS Marketplace and I got the "no service" error that others have reported. I tried installing both v4.0.290 and v3.0.284 manually, but I continue to get the "no service" error when I attempt to connect to a working Sitecore website. I also tried adding the fix in the web.config (mentioned in http://rockpapersitecore.com/2017/10/sitecore-rocks-with-sitecore-9/). I'm using VS2019, .NET 4.8, Sitecore 9.3 Initial Release.

@sbenhoff007
Copy link

@nickwesselman I installed Sitecore Rocks from the VS Marketplace and I got the "no service" error that others have reported. I tried installing both v4.0.290 and v3.0.284 manually, but I continue to get the "no service" error when I attempt to connect to a working Sitecore website. I also tried adding the fix in the web.config (mentioned in http://rockpapersitecore.com/2017/10/sitecore-rocks-with-sitecore-9/). I'm using VS2019, .NET 4.8, Sitecore 9.3 Initial Release.

Nevermind, I got this working by adding a binding to http on my local site.

@dsinclairmoore
Copy link

You can solve this by adding https://{instance-hostname} into the Sitecore Rocks hostname without adding a HTTP binding. Proven on Sitecore 9.3.0 & Sitecore Rocks 4.0.291

@Thamizh-commits
Copy link

As @dsinclairmoore mentioned, started to work after enter the host name with https:// in rocks host name. Thanks @dsinclairmoore

@ArulPushpam
Copy link

You can solve this by adding https://{instance-hostname} into the Sitecore Rocks hostname without adding a HTTP binding. Proven on Sitecore 9.3.0 & Sitecore Rocks 4.0.291

Thank you for the solution !! It is working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants