A colleague deleted a Sharepoint 2013 page by mistake, I can find it in the recycle bin, but when I try to restore it I encounter an error:
A file named "P10.aspx" already exists in "PORG/OAN/Pages". To restore the file, rename the existing file and retry.
The fact is that when I go into "PORG/OAN", site content, Pages, I can't find any "P10.apsx". I also tried to search for an existing "P10.aspx" file on the entire Sharepoint and didn't find anything.
Does anyone have an idea where that file might be hidden or how to delete/rename it without finding it so I can restore the one in the recycle bin please?
Thanks in advance for your answers.
In the Pages library settings, click on "Manage files which have no checked in version" and check if the offending page is shown there. –
Monte_fisto
Related
Okay so I'm using sharepoint online and the site I'm developing is pretty much done. There's only one issue, the icon.
I can change the site icon to the company logo with ease, but seemingly at random it just switches back to the previous icon. I've had a look in the site assets folder and it turns out every time it happens the previous logo is re-added to the folder and set as the site icon automatically.
I have no idea why this is happening and need to fix it quickly as it is the last issue.
Maybe it's an easy fix? May be something to do with the group that it's attached to? Maybe there's a way to overwrite it using CSS?
Any tips or advice?
I managed to solve the issue.
The logo was synced with the office 365 group that the sharepoint site was linked to.
I went into Outlook and deleted the group photo, then changed the site logo again and it hasn't changed since.
I'm finding that I need an App_Code folder in my web site, and I also need to permanently exclude it from TFS. I'm using VS2012 and TFS2012.
I've discovered some offered solutions, but they generally lead back to clicking on the "Detected Changes" link in the Team Explorer pane in order to open the "Promote Candidate Changes" window.
I can find "Included Changes". I can find "Excluded Changes". Neither contains the link to "Promote Candidate Changes".
I can't find anything marked "Detected Changes", link or otherwise. I haven't found anything that looks like a "Promote Candidate Changes" window.
Any clues as to why or to an entirely different solution that has nothing to do with those options would be greatly appreciated.
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
I am working on an intranet in Sharepoint online. I have added a custom css file and included it in the masterpage, after the default stylesheets. In the sourcecode I can see it clearly and I can follow the path to its intended file.
Earlier I had no problems to check it out, edit in Sharepoint designer, save it, then checking it in and changes would apply to the site.
But now the changes I make don't seem to catch. I have cleared cache on several browsers but still no change.
The masterpage and the custom startpage are both published. No files are left checked out.
I may be a sharepoint noob, I have searched any number of forums but not found anything pertinent to my problem.
Can anyone give me a pointer in the right direction please?
:)
Do you save the CSS file in a document library that uses versioning? Perhaps you forgot to publish the latest version of your changes, so browsers only see your previous version.
I made an account specifically to respond to this post because I was having the same issue and found your update about creating a new CSS file helpful in determining the real issue. So I wanted to share my solution!
In the end I discovered it was our BLOB cache being enabled that was causing the issue. We had enabled it to use image renditions. As per the following technet article regarding configuring the BLOB cache, I removed CSS from the file types and our issue was resolved!
http://technet.microsoft.com/en-US/library/cc770229(v=office.15).aspx#BLOB
I hope this helps :)
You are logged in as the Site Collection administrator?
CTRL+F5 to get the latest .css from server?
When you View Source you are able to see the link to your .css file?
When you follow the link to the .css file and open the .css file, it has the recent changes you made?
I think you might have done this.. but make sure after publishing the .css file it is approved.
Press F12 to load IE Dev Toolbar to see what styles are being used in the elements in question. May be you have a small syntax error in the recent classes you added.
Thanks, Karthik.
In the end I made a copy of the css file, gave it a new name and referred to that instead, worked like a charm.
Thanks for your answers and comments all
Under Site Collection Administration settings, go to SharePoint Designer settings and make sure all the checkboxes are marked including "Enable Customizing Master Pages and Page Layouts "
Also, make sure your tag that cites your custom CSS is just below the last meta tag in the head of your master page.
Lastly, remove quotes... there are additional quotes added with javascript so you don't need quotes AND have the full URL to the stylesheet or it will not work!
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