- Powershell
- Microsoft SharePoint
SharePoint 2013 - Not working after config IIS to work with port 443 SSL
Hello everyone.
I installed Sharepoint 2013 Standard edition on a virtual AWS (Amazon Web Services) server which is running server 2008 Standard with SQL.. Everything was installed using default settings. Once it was installed, I configured a few users and groups for testing. At that point, everything was working perfect. Was able to login, go to my document libraries and was able to upload, edit and save documents with literally no issues.
One of my development team guys got it and made changes within IIS to make SharePoint use port 443 SSL. After than change was made, I can get logged in, and initially see the initial SharePoint screen with folders and document libraries.
The issue now is that anytime I try to click on a folder or document library, I get the following error:
Sorry, something went wrong
Method 'Upgrade' in type 'Microsoft.SharePoint.Work
TECHNICAL DETAILS
GO BACK TO SITE
Can anyone comment or give advice on this ? I was suppose to have this issue corrected last week and am running out of things to do.
Thanks !!
I installed Sharepoint 2013 Standard edition on a virtual AWS (Amazon Web Services) server which is running server 2008 Standard with SQL.. Everything was installed using default settings. Once it was installed, I configured a few users and groups for testing. At that point, everything was working perfect. Was able to login, go to my document libraries and was able to upload, edit and save documents with literally no issues.
One of my development team guys got it and made changes within IIS to make SharePoint use port 443 SSL. After than change was made, I can get logged in, and initially see the initial SharePoint screen with folders and document libraries.
The issue now is that anytime I try to click on a folder or document library, I get the following error:
Sorry, something went wrong
Method 'Upgrade' in type 'Microsoft.SharePoint.Work
TECHNICAL DETAILS
GO BACK TO SITE
Can anyone comment or give advice on this ? I was suppose to have this issue corrected last week and am running out of things to do.
Thanks !!
Probably not the issue, but something to check. When the developer set up SSL, did he also bind the site to a valid certificate. Sure he did, but this is a good place to start troubleshooting.
Hi,
did the SSL certificate got imported into Central Administration?
Central Administration >> Security >> Manage Trust
Did you also update the web applications url mapping in Central Administration?
Also as SneekCo mentioned, verify IIS.
A good step by step blog post on MS:
http://blogs.msdn.com/b/fabdulwahab/archive/2013/01/21/configure-ssl-for-sharepoint-2013.aspx
HTH
Rainer
did the SSL certificate got imported into Central Administration?
Central Administration >> Security >> Manage Trust
Did you also update the web applications url mapping in Central Administration?
Also as SneekCo mentioned, verify IIS.
A good step by step blog post on MS:
http://blogs.msdn.com/b/fabdulwahab/archive/2013/01/21/configure-ssl-for-sharepoint-2013.aspx
HTH
Rainer
Hi folks,
@ SneekCo, yes the site was bound to a good valid cert within IIS.
@ Rainer: well, I am not too sure hot to import the Cert into Central admin. I did review the link you posted in your response and it was somewhat helpful. There was no https path setup in the AAM are and I was able to add it..
But, as of right now, I am still getting the same issue, the same error message.
@ SneekCo, yes the site was bound to a good valid cert within IIS.
@ Rainer: well, I am not too sure hot to import the Cert into Central admin. I did review the link you posted in your response and it was somewhat helpful. There was no https path setup in the AAM are and I was able to add it..
But, as of right now, I am still getting the same issue, the same error message.
Hi,
have you rebooted the server after you have imported the certificate in the trusted store in Central administration?
I am pretty sure that the update might not get applied for running services.
Second question: which Service Pack and which cumulative update do you have applied to your SharePoint farm?
It seems that there might be an issue with Windows Updates and non-SP1 farms.
HTH
Rainer
have you rebooted the server after you have imported the certificate in the trusted store in Central administration?
I am pretty sure that the update might not get applied for running services.
Second question: which Service Pack and which cumulative update do you have applied to your SharePoint farm?
It seems that there might be an issue with Windows Updates and non-SP1 farms.
HTH
Rainer
All, this was the solution. Didn't even need a reboot.
PA~
http://blogs.msdn.com/b/fabdulwahab/archive/2013/01/21/configure-ssl-for-sharepoint-2013.aspx
PA~
http://blogs.msdn.com/b/fabdulwahab/archive/2013/01/21/configure-ssl-for-sharepoint-2013.aspx
-
![]()
received a Solution
PowerShell script to set a large number of SharePoint 2013 site collections to "No Access" lock status -
![]()
wrote an Article
![]()
Create Custom SharePoint Dependent Dropdowns
-
![]()
created a Video
![]()
How to delete the Recently Browsed folder list in Microsoft Office Picture Manager
-
Explore Cloud Class® ![]()
SharePoint Foundation 2010: Advanced
Premium Content
You need an Expert Office subscription to comment.Start Free Trial