Cannot find an SPSite object with Id or Url in PowerShell over HTTPS

Question

_{Wednesday, September 19, 2012 9:12 PM}

So I've setup a web application that runs on https://hostname:10433.  This website is only accessible via https and I'm thinking that this may be what is causing the problem in PowerShell but I'm not sure.

So when I run...

Get-SPSite https://hostname:10433

...I get "Cannot find an SPSite object with Id or Url https://hostname:10433".  I'm running this command via PowerShell on the server logged in with an account that is a Farm Administrator and Site Collection Administrator for this site so all of the necessary permissions are in place.

I am able to connect to other web applications on this server just fine that are accessible over http (not https).

What am I missing?

All replies (3)

_{Thursday, September 20, 2012 1:16 PM ✅Answered | 1 vote}

Very strange thing happened a little bit after I posted this question.  I went in to Central Administration and created an alternate access mapping to http://hostname:10433 in the Default zone.  I was then able to run...

Get-SPSite http://hostname:10433

...without any problems and got back an object.  Very strange.

And to answer @Roger...

When I ran...

Get-SPWebApplication <WebApplicationName>

...I got back a list of web applications with the url https://hostname:10433.  This is exactly why I assumed (just like you) that it would work.  Strange one.

_{Wednesday, September 19, 2012 9:22 PM | 1 vote}

Was the web application originally deployed with a different URL, or not requiring SSL?  You'll only be able to address web applications (and sites) using the URL associated with the default zone of the web application using PowerShell.  You should be able to confirm the default zone through SharePoint Central Administration, or by issuing the following PowerShell cmdlet:
Get-SPWebApplication

If https://hostname:10433 is returned, you should be able to use Get-SPSite.  I'd be very surprised if this is not the case in your environment.

Roger Cormier

Microsoft
Premier Field Engineer, SharePoint

Blog: http://blogs.msdn.com/b/rcormier/**
Twitter: LinkedIn:
**

Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

_{Friday, April 5, 2019 6:57 PM}

Same thing happened to me if I configured a managed path for "/" (root) to Wildcard exclusion.  The minute I set it back to Explicit inclusion, I was able to do Get-SPSite on it without an issue.  Before then, I got the same error you did.