Sorry, something went wrong --- I got an error message after a new webapp was built and a new site collection was created

Sorry, something went wrong --- I got an error message after a new webapp was built and a new site collection was created.
This in SharePoint 2013 Farm.
What should I do?
1- I did a DisableLoopBack and set the value to "1".
For hostname do I have to do : 111.111.111.111 (sample) and serversp2013?
P.S. I fixed this issue once, long time ago and I forgot how it ... be done.

Hi,
For troubleshooting your issue, please take steps as below:
1.Go to IIS, make sure the web application is actived.
2.Go to IIS -> Applicaiton Pools, make sure the application pool related to your web application is started.
Reference:
http://support.microsoft.com/en-us/kb/926642/en-us
http://www.techrepublic.com/forums/questions/cannot-browse-created-web-application-site-in-sharepoint-services-30/
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

Workflows completes but goes to "Sorry something went wrong" page

SharePoint Version: 2013
Workflow Version: 2010
My Title: Junior SharePoint Administrator
I have been working weeks on a project to use workflows for a business process. It is as simple as setting variables and sending email to people.
I have successfully created a site workflow and published it. When I start the workflow, it starts fine but then show me this (very annoying and always unhelpful) error --> Sorry,
something went wrong. An unexpected error has occurred.
Funny thing, the workflow stills completes fine and I get the email notification I created in the workflow! No errors messages in the workflow history either - completely clean.
Is there any reason for this? I am concerned since it will be used by a large group of people monthly and this is a huge "NO" for UX experience and usability...
I have tried linking the Correlation ID to anything and looking through server logs. I have got nothing.
Help please? :)

get the time that the error occurs, and recheck the log file that during this time, whether there is related information.
what's your workflow do? what's the result by using other user account to start the workflow.
Qiao Wei <br/> My blog:<a href="http://blog.goobol.com">http://blog.goobol.com</a>

Error while editing Workflow Task List Item - "Sorry, something went wrong.. Web must contain a discussion list

I have an custom approval workflow and when I try to edit an assigned approval Task it throws me an error
Sorry, something went wrong
Web must contain a discussion list
Any help appreciated!
Pravs

Hi,
For a better troubleshooting, I suggest you do as the followings:
1. Check the ULS log for more detailed error message, for SharePoint 2013, the ULS log is located at the path:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
You can use ULS Log Viewer to check the information in the log.
2. You can use fiddler to track if there is something wrong in the workflow request.
Here are some detailed articles about debugging workflow:
https://msdn.microsoft.com/en-us/library/office/dn508412.aspx
https://sharepointlogviewer.codeplex.com/
Thanks
Best Regards
Jerry Guo
TechNet Community Support

Error in Search results - Sorry, something went wrong. Display template had an error

I'm receiving this error in custom search results page in our SharePoint 2013 Enterprise farm:
Sorry, something went wrong.
Display Error: The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types.
'console' is undefined (CoreRender: ~ sitecollection/_catalogs/masterpage/Display Templates/Search/Item_mycustom_Site.js
I believe a similar error was resolved by March 2013 CU but our farm us running Aug 2013 CU. I have also tried adding domain to trusted zone in IE but still the same error.
I do not get this error in Google Chrome or in IE 10 or above. Not sure if it is an issue with my display template because error disappears when upgrading IE to 10 or 11.
Update: In IE 8 I can see search results with no error if the developer toolbar (F12) is enabled!
-- The opinions expressed here represent my own and not those of anybody else -- http://manojvnair.blogspot.com

Hi ,
Did you try these steps
Open up the SharePoint 2013 Management Shell as Administrator
and run the following command: Enable-SPFeature SearchWebParts -url http://<central admin
url>
Use a browser on a different machine, or add you SharePoint
site(s) to the ‘Trusted Sites’ in IE.
Activate the feature : “My
Site Host“. This is a hidden feature scoped at the Site Collection level. The feature ID is 49571CD1-B6A1-43a3-BF75-955ACC79C8D8.
The feature folder under SharePointRoot is MySiteHost.
Install the update: http://www.microsoft.com/en-in/download/details.aspx?id=36989
Here are some similar threads for you to take a look at:
http://sharepoint.stackexchange.com/questions/70452/query-builder-for-result-source-not-working-in-central-admin
http://www.thesharepointbaker.co.uk/sharepoint-2013-gotchas-2/
http://bernado-nguyen-hoan.com/page/2/
Ref:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/6e86cf3f-8001-4d13-a700-9e70d8828f03/controlsearchboxjs-not-found?forum=sharepointsearch

Sorry, Something Went Wrong, Unexpected Error Occurred

Having a very strange issue with main SharePoint 2013 Page after upgraded all the way from 2003 to 2013. Initially setup 2013 Web App for just http and I could log in with my user account and do all things for which there are assigned privileges. Then converted
to SSL and I receive the Sorry, Something Went Wrong error on the main page. No other user account we have tried has any problem whatsoever. This is currently an upgrade test environment but am very worried that we will encounter other users that have the
same problem on the main page or some other site page. Thing is, I cannot find a single log entry that contains the Correlation value in the error report and it is only when hitting the site using SSL. It does not matter what computer I am using (tried multiple).
The other users testing have no issues so far.
Additional testing. When I change back to http set in Public URLs I have no problems but others do. When set to https in Public URLs I have problem and they don't. However, I was the first and only one, other than farm account (which never has problems)
to work on the site using straight http.
Any help on this would be appreciated. I have scanned through table upon table in the User Profile database thinking there must be something in there messing with profiles or setting some sort of default but cannot think of a thing. App Pool needs to be
restarted in addition to IISRESET?

Are you talking about central administration (e.g. "main SharePoint 2013 page")?
if yes, make sure to set bindings in IIS to include a certificate, preferably a wildcard * cert. and then run
Set-SPCentralAdministration -Port 443
https://technet.microsoft.com/en-us/library/ff607832(v=office.15).aspx
If you're talking about your team site, for ex. make sure you set binding for https on the site in IIS and use a wildcard cert.
You can run a Merge-SPLogFile -Path c:\SP-error.txt -Correlation Input-Your-CorrelationID-Here and then paste the results on this blog and the group can help you, better if more info is provided.
If there is a correlation ID, you can get it with Merge-SPLogFile.
https://technet.microsoft.com/en-us/library/ff607721(v=office.15).aspx you may have to use start and end times.
Stacy Simpkins | MCSE SharePoint | www.sharepointpapa.com

Search Error - Sorry, something went wrong

Search has encountered a problem that prevents results from being returned. If the issue persists, please contact your administrator. is the message that I get when I try to search.
The search application seems to be working just fine. I have all green checks in my Search Application Topology and my crawl log show successes and no errors. I also get an error when I try to create a Enterprise Search Center.
I am at a loss and any help would be appreciated.
Thanks

Hi,
Refer to the solution from Peter Filbin in the thread below:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/1522176a-8fe1-4b4e-94a9-a89595e069b4/sharepoint-2013-search-not-working-sorry-something-went-wrong-everytime-do-i-have-to-set-it?forum=sharepointsearch
Thanks.
Tracy Cai
TechNet Community Support

Sorry, something went wrong - Open Office File from Search Results Page with Office Web Apps

Hi,
I'm getting "Sorry, something went wrong" error when I'm trying to open any office document from inside Search Results Page with Office Web Apps, the same error is appearing in the document preview as well.
The error in SharePoint logs says that the file cannot be found.
Please note that this error is coming only when the "Filename" of the document is not written in English (in my case its written with Arabic characters).
If I try to open it from the document library, its opening properly with no errors.
The only difference between two URLs (document URL in Search Results and in Document Library) is the value for "sourcedoc" attribute;
In the case of Search Results page, the filename in "sourcedoc" attribute is kept as is with Arabic characters.
While in the Document Library, the filename in "sourcedoc" attribute is converted into different characters (something like: "B9%D9%85%D9%8").
Anybody have an idea on how to overcome this issue, implement a workaround or modify the "sourcedoc" behavior?
Thanks in Advance.
Hamza AlSughier

Dear Wendy,
Thanks for your efforts, I already tried your last suggestion before, but this didn't solve my problem.
Actually my end users are accessing this portal using ADFS and HTTPS.
Finally I got this solved, I have done below to get my overall solution working perfectly:
- First I have configured Windows Authentication and ADFS Authentication on the same zone which is the default zone.
- The issue when opening office documents with Arabic file name has disappeared as a result of first change.
- Then I have faced an issue where we are not able to crawl content under Default zone, however we have to do so, after too many efforts, I found that its related to the Load-balancer/proxy, I have made the crawler server
to crawl himself (http://CrawlServerName:PortNumber).
- Also a change on Alternate Access Mapping was needed, I have set one of the extended zones (which is running Windows Authentication only) as Internal URL for the Default Zone, and this is was the URL I used for Crawling.
I have configured Server Name Mappings to make sure we got proper URLs in Search Results.
- Then we faced another issue, which is Authentication selection on login page (How to bypass this page, and authenticate using ADFS auto), I used this solution (Set Custom Sign In Page):
http://0ut0ftheb0x.wordpress.com/2014/01/04/skip-the-authentication-selection-page-at-_logindefault-aspx-in-a-mixed-authentication-environment/.
- I faced one more issue as a result of above workaround; Sign Out functionality wasn't working well; users get logged in automatically whenever I click on Sign Out. I solved this by modifying the "Sign Out" Control under _layouts;
I made it to redirect users to ADFS Sign Out Page instead of SharePoint Sign Out Page (I know its not recommended, but I don't have any other option).
Hamza AlSughier

MS Word 2013 unable to start. "Sorry, something went wrong and word was unable to start. (6)

I am trying to open MS Word 2013. I have purchased the MS Office online and pay a subscription. When opening MS Word, it comes up with the error message "Sorry, something went wrong and word was unable to start. (6)" This appears to be happening
with all MS office applications. Can someone please help?

I faced this same problem and reinstalled office several times but no luck, then followed below steps and got my issue resolved:
Solution is that you run word in "Administrative" mode:
To run the Word program in administrator mode, try the step below:
· go to Computer, Programs files/Program files X (86).
· Look for Microsoft Office ->Office 15.
· Look for Winword.exe
· Right click on it and click
Properties
· Click on the Compatibility tab
and check the box forRun as admin.
· Clickok.
Ref: http://answers.microsoft.com/en-us/office/forum/office_2013_release-word/unable-to-open-word-sorry-something-went-wrong-and/aa080850-1fe3-46b5-8338-905633e8f9a0

Sorry something went wrong. Please try again. Power BI Scheduled Data Refresh

My Power Pivot Connection can be refreshed locally from Excel workbook. However I receive the following error when attempting a data refresh from the Power BI site:
Sorry, something went wrong. Please try again. Correlation ID: 70aad105-6563-42de-9c27-272ecfa082ee start date 2/24/15 at 11:38 AM

Hi Ryan,
Will you please check the following:
1. are you refreshing the data from within Excel online?
2. If yes, does your workbook connect to on premises data source?
if yes, then refresh of on premises data sources from within Excel online is not supported. Schedule refresh is the only supported means to refresh workbooks connecting to on premises data sources or using Power Query.
If this does not answer your question. Please mention the steps you followed & attach an image of the error you see.
-mini

SharePoint 2013 - Refiners "Sorry, something went wrong."

Good Afternoon,
I have an issue that has had me stumped for a couple of days now. I have a number of search results pages and on one of them and only one of them I am getting an error.
Whenever I add a refiners webpart and save the page everything works fine. However if I add or remove any refiners I get the infamous "Sorry, something went wrong." Whats causing my problems though is that when I click on Show Details there is
no correlation ID and I cannot see any errors in the ULS logs that might be related to this.
Using SharePoint Manager 2013 I opened the page properties and selected the webpart and I am getting the following message against "Effective Storage" and "Permissions" : Trying to use an SPWeb object that has been closed or disposed
and is no longer valid.
So in desperation I deleted the page and recreated it but the issue persists. The only thing different about this page and the other pages is that this page show people results. However if I change the query to use the "System Everything" results
source I still get the error.
edit:
I have just tried to amend the refiners on an existing page and I can amend them with no issues. I then created a brand new page and I get the same error. On my new pages I changed nothing except adding the search box / search results and refiners web parts.
So its an issue that does not affect existing pages only new ones..
More info: I have just created a new site on the same same site collection and created a page on this new site and I get the same issue.
Regards,
Brian Jones

Hello,
Thanks for your interest.
These are the steps:
1. Create a new page
2. Add the following web parts, Search Box, Search Results, Refiners. If I then just save and close the page everything works fine.
3. Edit the page
4. Edit the refiners web part.
5. Click on change refiners* select any refiner that is already added and remove it (any it does not matter).
6. Click OK on the web part properties. Immediately I get this issue. As you can see there is no correlation id in the error message.
7. Edit the refiner web part again and re-add the refiner I removed. Click on OK on the web part edit pane. The issue persists.
8. If I delete the refiner web part and re-add it the refiners web part works fine again unless I try and modify the selected refiners.
Please note this issue occurs if I add refiners as well.
Brian Jones

Sorry, something went wrong and Word was unable to start (6) Office 2013

Ok this is just so annoying.
Whenever I try to open Word, it gives the error "Sorry, something went wrong and Word was unable to start.(6)". Other office applications either freeze or crash. Only Excel works fine. Running Win7 64 bit.
Tried all possible ways of installation/reinstallation. Did repair, uninstalled and reinstalled manually, uninstalled with FixIt from Microsoft, removed every leftover thing from registry. Also removed some other applications that I thought could cause this
problem for Office.
Uninstalled 64 bit Office, and installed 32 bit, same exact problems.
!!!Don't suggest me to run as administrator please!!!

Hi,
According to your description, I suppose that Word 2013 was blocked by some other applications after you opening it.
Which operation system do you use? Have you installed the Office 2013 SP1?
Then, we try to do some tests to narrow down the issue:
1. Collect the Event log
http://windows.microsoft.com/en-us/windows/what-information-event-logs-event-viewer#1TC=windows-7
2. Use the
Process Monitor to collect the detailed information.
Open process monitor, and reproduce this issue, if there is any files or keys were blocked during the process.Please let me know, and you could save as the file from process monitor, upload the file through One Drive and share the link to me. I'll
analysis it.
Regards,
George Zhao
TechNet Community Support

Office Web Apps Issue - "Sorry, something went wrong" message when opening a document (any MS docx,ppt etc) in IE. With Chrome, it pops (Microsoft Office needs your permission) message and on RUN, it opens the document.

When opening any Microsoft documents ( docx, ppt etc) in SharePoint 2013,
Internet Explorer behavior : "Sorry, something went wrong" An unexpected error has occurred message and then nothing happens.
In Chrome : Pops (Microsoft Office needs your permission) message and on clicking RUN, it opens the document.
In Firefox : the documents opens, after asking which application do you want to use to open it.
The feature (Open Documents in Client Applications by Default) is not activate.
Why the MS documents are not working in IE 10?

Hi,
According to your post, my understanding is that you failed to open Microsoft documents in SharePoint 2013.
I recommend to Run the following PowerShell in OWA Server :
Remove-OfficeWebAppsHost # To Remove any restriction
Or
New-OfficeWebAppsHost -Domain <String> # To allow specific domain Name
In addition, you can allow OAuth via HTTP using the following commands:
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()
Here are two similar articles for you to take a look at:
http://blogs.msdn.com/b/fabdulwahab/archive/2013/10/30/office-web-apps-with-sharepoint-2013-issues.aspx
http://stevemannspath.blogspot.in/2013/03/sharepoint-2013-office-web-apps-issue.html
Best Regards,
Linda Li
Linda Li
TechNet Community Support

PowerPoint 2013 - We're sorry something went wrong...

We've recently upgraded to Office 2013 Professional Plus from Office 2010. Our Workstations are Windows
7 x64 SP1 and this issue is happening on freshly built machines and established installs.
When a limited user creates a new presentation, launches Slide Show, right clicks and tries to access the "Pointer
Options" to annotate the slide with a pen or highlighter, they receive the following error and no annotations:
"We're sorry something went wrong that might make PowerPoint unstable. Please save your presentations and restart PowerPoint"
This error doesn't appear as an Administrator, so its probably a permissions issue . It also happens on existing opened presentations.
Office 2013 has been repaired and re-installed without resolving the issue.
I've tried troubleshooting with Process Monitor to see what files the user doesn't have access to but have come up a blank. There is nothing obvious in the Application or System event logs either. Any other ideas?
I hope someone can help,
Cheers
Tom

Hi Tom,
Please try to right-click on Microsoft PowerPoint within your start menu and select "Properties" then navigate to the "Compatibility" tab. Tick the box before "Run this program in compatibility
for:" and select "Windows 7" from the drop list. Restart PowerPoint to check the result.
We can also try to open PowerPoint in safe mode to check if this issue is related to problematic add-in. To do this, hold
Ctrl key when you double-click to open the presentation.
In addition, some people report that they are able to work around this issue by opening the original presentation and then saving it as a .ppt file (not a .pptx), you may check if it works.
Please let me know the result.
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Project Online - Sorry, something went wrong when trying to load PWA

Hi All
When trying to load a Project Online instance (a new deployment in this case), we get the 'Sorry, something went wrong' error message.
I tried to provision another PWA site (PWA2), and the same error occurs.
Anybody seen this?

Hello,
Providing it has provisioned correctly in the SharePoint Site Collection admin page, there isn't a lot you can do other than raise a support ticket via the Office 365 tenant. If these are new blank PWA instances, try switching the permission modes, see if
that helps.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS |
MVP | Downloads

PowerPoint 2013 - We're sorry something went wrong that might make PowerPoint Unstable

Windows 7 running Office 2013. Mature installation no recent changes.
Simple update to ppt file created in 2003 ( using Compatibility mode). Single user edit saving to my documents
Error Message "We're sorry something went wrong that might make PowerPoint Unstable" / "Please save your presentations and restart PowerPoint"
PowerPoint no longer allows me to save any file in any format without this message.
Actions taken : Restart PowerPoint / Reboots / Deletion of temporary files from C:/Windows/Temp
Problem persists

I had this problem with Win81, PowerPoint 2013, pptx file, no system/software changes or updates that could be blamed. Out of the blue working on an existing document, messages as OP wrote started plaguing PPT. Brand new pptx files created with benign random
text also suffered from this. A save or two within the first 30 seconds of opening or creating the file sometimes went ok, but problem appears inevitably - implicating file lock issue.
There is remarkably little commonality in resolutions of this on the web, and no resolution from MS.
Tried many of the suggestions that can be found - no joy.
Finally isolated this to the live sync on DropBox. If DropBox is active (immediately syncing changes in the background), the problem persists. If DropBox is paused, the problem ceases. DropBox does not need to be removed or exited. If unpaused, problem
immediately starts again. Have not been able to check if other syncing cloud drives have same effect.
What's disturbing is that the DropBox/PowerPoint combination on this machine has been working fine for 1+ years. Turning off DropBox is not an acceptable solution. Perhaps a silent update of one or the other occurred to cause this.

Sorry, something went wrong --- I got an error message after a new webapp was built and a new site collection was created

Similar Messages

Maybe you are looking for