I am new to Sharepoint and was playing with the webparts. I downloaded a zip file called LyteBoxForSharePoint and uploaded the webpart using add a web part function. Now I am getting errors. The good thing is, that it's only my dept page. The bad thing is I have no clue what happened. All other pages beside the dept landing page is working. So, I am guessing it's only the landing page that has the issue. Is there a way to find out what code was added or to revert to old code. The error I get is the following, and it keeps on changing every time I refresh the page.
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: e8eca359-70f9-42d0-b41e-834fbe0fc910
Date and Time: 2/23/2012 2:47:39 PM
Could be anything, most common error in SharePoint is authentication errors where a web part is trying to reach content the logged in user cannot reach
You should check the logs, they are available in the directory C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
Open the last modified log file and search for your Correlation ID, e8eca359-70f9-42d0-b41e-834fbe0fc910
When you find the errors there you will now and also be able to post something that we can use to help you.
Then there is always the webpart maintenance page: /_layouts/spcontnt.aspx?url= http://sharepointserver.com/_layouts/spcontnt.aspx?url=default.aspx
Rex,
first browse the page which is giving webpart error and copy the new correlation id and go to the log folder under 14 hive and open the latest log file and find the correlation id. it should give you the error details if logging is not disabled.
also you can go to the webpart manger on the page to revert the page to the previous state by adding contents=1 as query string and in this page you will get list of webparts with checkbox against each. select the faulty one and revert to previous version if any or delete it.
you can also use SPD2010 to remove the webpart with error. alternating powershell can be also used.
One way to check if the webpart is installed is to type ?contents=1 after your url. There is also stsadm -o preupgradecheck and unfortunitely stsadm has another command to list all webparts but I cannot think of it at this time
Related
I have a project which uses SharePoint lists as data sources to create the reports. I'm using Visual Studio 2013 for this.
I have this real annoying issue at this moment, ie. when I want to edit a dataset I created a while ago and I press 'Query Designer...' in the dataset properties to see all fields from my list I get an error which says that I am unauthorized.
My DataSource is configured to link to the SharePoint Site Url with Windows Credentials. I have also tried this out for multiple datasets on multiple reports but the error is everywhere.
Because of this I'm also not able to run my reports. They just say "An error occurred during local report processing.".
I have been working on this project since March and this is the first time this has occurred so I have no idea what might have gone wrong nor how to solve it.
Does anyone know what might cause this error and how to solve it please?
If you have any questions or remarks about my question/problem, please, don't hesitate to leave a comment.
Kind regards
EDIT 1:
I have just tried deploying a report that I finished last week and for the first time I got a prompt that asked for my credentials. I haven't even put my credentials anywhere in the project for past authorisation so I have no idea why the project would suddenly need it now...
EDIT 2:
I have just tried changing the DataSource credentials to my own login for the SharePoint Site. If I run the report I get the same error as before but when I go to Query Designer for one of the datasets I get following error:
EDIT 3:
I just restored a back-up I made a couple of weeks ago. I can now run my reports but I still get the Unauthorized error when I try to open a dataset's query designer and the prompt for my credentials when I try to deploy a report.
So, the solution has been found!
Apparently something has gone wrong with my PC and I had to reconfigure my user accounts.
To do this go to Control Panel -> User Accounts
Then click on 'Manage User Accounts'. Go to the 'Advanced' tab and click on 'Manage Passwords'
Next, go to 'Windows Credentials' and change the credentials for your site or recreate them.
Every time I try to edit the homepage of a sub site, I get this error:
Sorry, something went wrong
An unexpected error has occurred.
Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.
TECHNICAL DETAILS
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: e600839c-9ba3-8086-3aaa-67ad6e8baef0
Date and Time: 4/1/2014 8:21:33 AM
I'm fairly new to SharePoint. If anyone could shed some light on this, it will be greatly appreciated.
This is a pretty generic error in SharePoint that can be caused by any number of things. You can take a look a the Web Parts Maintenance Page by adding "?content=1" to the URL of your page. If you recently added a web part to the page or some other customization, this will allow you to turn it off.
More than likely though, you will have to do some digging. Whenever you ih that page and get an error, you get a correlation id like in your example above. You can dig deep into the logs by finding them (typically in C:\program files\common files\microsoft shared\web server extensions\15\logs). Look for the most recent file and do a search it in and see if you can find that correlation id. If you can't find it you might try the previous log. When you find matching entries for the correlation id, you should get some idea to the component that is failing and causing your issues.
As odd as this sounds it worked to fix this for us.....
I had imported calendars from sharepoint 2003 to sharepoint 2013.
We had a reoccurring calendar appointment that would trigger in sharepoint 2013. The "Sorry, Something went wrong" Web Parts Maintenance Page: If you have permission you can use this page blah blah blah.... error would trigger for us on only the reoccurring appointments that were imported from SP 2003.
We deleted the reoccurring appointment in the SP2013 calendar and restored it from the settings - site contents - recyclebin (user who deletes must do the restore) and for some odd reason all the appointments were now opening and all content was still there.
Maybe this will help someone
I'm using SharePoint 2010. I saved a Site Template(.stp) and used this template to create a sub site. Browser shows file not found error, however, if I add /_layouts/ChageSiteMasterPage.aspx to that URL, I'm able to see settings Page.
Error:
cannot create folder "Path".
Correlation ID: 4baa2636-0dd9-4965-afc1-e438d74a20d5
What could be the problem??
Search for that correlation ID in your SharePoint log. Probably the problem is because you need to activate a feature in the new site, or you have a custom solution that you need to deploy there.
Go to Site Setting and open the Master Pages section. Look for anything checked out and chack it back in. This happens each time you create a new site from a template.
Does anybody know how to find offending web part which causes this error ?
“A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe.”
I have inherited an old SharePoint 2003 portal site which uses custom web parts.
I know what this error means. I also know that each web part must be installed and registred as safe in web.config. The problem is that I don't know which one is missing.
I get same error when I'm trying to open the page in FrontPage as well.
Use contents=1 in QueryString to disable/remove WebParts from page that causes errors.
stsadm.exe -o enumallwebs -includewebparts
http://sharepointreporter.wordpress.com/
Requires updating to Sp2 I believe, for this command to be available. Problematic web parts will appear as 'Missing' in the resultant list.
Go to Event Viewer of the machine and you shall be able to see Error entries. Out of tons of entries you have to find out the entries related to you and you shall be able to see the names of the webparts that the sharepoint site is trying to load but fails. If you shall read the complete description of the error entry in the Event Viewer, it will give you version and even PublicKey Token of the webpart as well.
I hope this helps!!!
Try reading this:
http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=189
It should give you some clues to solving the problem. Essentially you have a control that is not marked as safe and it is failing. You can most likely config it to work, but the link above has other possible solutions.
in your url just append content=1. This will give you the all the webparts that are deployed. Now, you can keep deleting each of the webpart to find which one is causing issue ( ensure that you know to add the web parts back).
For example: if Url is http://localhost:9000/default.aspx, try with http://localhost:9000?contents=1
Alternatively, try to create a new webpart page,add web parts that are there on your actual page and check which one is causing issue. This will avoid changes to the actual page.
Hope this helps.
I've just suggested this same answer on MSDN:
This stsadm helped me in finding where the webpart was referenced in any way:
stsadm -o enumallwebs -includewebparts > C:\temp\somelog.txt
Then you can see the web part is listed under some <Web Id=... Url=...> XML node, i.e. you know the "culprit" web site.
At that point, some reasons I've found for those forgotten references:
the webpart is used in some sub-site of the culprit website, and the sub site is hidden from the quick list or top bar
the webpart has been deleted from the culprit website, but it still is in the "site collection recycle bin". You can reach that by going to the normal website recycle bin, then look for its link on the top bar description ("Use this page to restore items that..."). By the way, this site collection recycle bin has two views itself: be sure to check them both.
In both cases, I got some help by browsing the culprit website with SharePoint Manager. With that I could easily spot the existence of a forgotten subsite, as well as the existence of this "second level recycle bin".
HTH
I have a Site Template with few customized lists and customized pages. I create new webs when ever needed using the site template. After creating the web, I also set up a theme and unique permissions to the web using C# code itself, then I redirect the page to the newly created web URL. My code runs within a Long running operation. It works all the time fine, but in some circumstance I get an error "file not found" when the page re-directed to the newly created web.
When I had closer look, I see that the web was properly created and the permissions were set; the pages library & other lists are also found, but the master page gallery is not found. Due to that I could not browse any pages in the page library & I could not even check web theme. When I see the Logs I found the below error.
04/09/2009 14:22:49.35 w3wp.exe (0x11B4) 0x0D0C Windows SharePoint Services General 8z1y Medium Failed to create list "Master Page Gallery" in web "http://rootsite/subsite", HRESULT=0x81020012. List XML: ""
What could cause this issue? I don't get this all time only sometimes I get this issue. There were no errors thrown on code, but the web's master page gallery was not created. Have you ever faced such problem? How can I solve this?
Thanks in advance,
~Yuva
The HRESULT you're getting is from a COM error: System.Runtime.InteropServices.COMException (0x81020012): The specified name is already in use.
Make sure that the gallery you're trying to create is at the web level, not the site or webapplication level. Can you post examples of the URL when it worked vs. when it didn't?
Isn't the master page gallery usually at the site rather than web level? Subsites can use a master page defined by the parent site, so you could be confusing things by trying to define the master pages on the subsite as well.