In my email today I got the following:
The My Site of is scheduled for deletion. As their manager you are now the temporary owner of their site. This temporary ownership gives you access to the site to copy any business-related information you might need. To access the site use this URL: http://mysites.mycompany.com/personal/
I click on the link and I can see that there site is there. I do not want there site to be deleted at all what can I do.
When I search for the user using the PeopleSearchBoxEx web part the user comes up but when I click on there name I get the error:
Server Error in '/' Application.
--------------------------------------------------------------------------------
User not found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.SharePoint.SPException: User not found.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SPException: User not found.]
Microsoft.SharePoint.Portal.WebControls.ProfilePropertyLoader.OnInit(EventArgs e) +4415
System.Web.UI.Control.InitRecursive(Control namingContainer) +333
System.Web.UI.Control.InitRecursive(Control namingContainer) +210
System.Web.UI.Control.InitRecursive(Control namingContainer) +210
System.Web.UI.Control.InitRecursive(Control namingContainer) +210
System.Web.UI.Control.InitRecursive(Control namingContainer) +210
System.Web.UI.Control.InitRecursive(Control namingContainer) +210
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378
Any idea how I can stop this person from being "delete" and get there profile to work again?
I experience the same error.
I changed the primary site collection admin to myself on this mysite and that worked. This message is coming from the primary site collection admin being the user that has been deleted.
Go to central admin > application management > site collection administrators and choose your mysite application and then your user site collection for this site.
It looks like the user has already been deleted (possibly due to sync with AD) but not yet removed from the search index. You'll need to look into what caused the user to be removed.
Related
I have a two month old, single server SharePoint 2013 site collection with several sub sites. Everything is working fine except the Newsfeed shows deleted items from community site discussion posts.
Steps for me to reproduce:
Create a new Community Site
(example.com/discussions/SitePages/Community%20Home.aspx)
Post a new discussion. That post immediately shows up in the Newsfeed
(example.com/my/default.aspx)
Go back to the post and delete it. The post is still in my Newsfeed and the following error is given when it is clicked:
Server Error in '/' Application.
Cannot complete this action.
Please try again.0x80004005
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Cannot complete this action.
Please try again.0x80004005
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[COMException (0x80004005): Cannot complete this action.
Please try again.0x80004005]
Microsoft.SharePoint.Library.SPRequestInternalClass.GetFolderContentTypeId(String bstrUrl, String bstrFolderUrl, Object& pvarContentTypeId) +0
Microsoft.SharePoint.Library.SPRequest.GetFolderContentTypeId(String bstrUrl, String bstrFolderUrl, Object& pvarContentTypeId) +209
[SPException: Cannot complete this action.
Please try again.]
Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) +146
Microsoft.SharePoint.Library.SPRequest.GetFolderContentTypeId(String bstrUrl, String bstrFolderUrl, Object& pvarContentTypeId) +519
Microsoft.SharePoint.SPList.GetContentTypeIdByUrl(String url) +346
Microsoft.SharePoint.SPViewContext.get_FolderContentTypeId() +288
Microsoft.SharePoint.SPViewContext.get_NeedToRedirect() +530
Microsoft.SharePoint.SPViewContext.RedirectIfNecessary() +153
Microsoft.SharePoint.WebPartPages.DataFormWebPart.CreateChildControls() +567
Microsoft.SharePoint.WebPartPages.XsltListViewWebPart.CreateChildControls() +2986
Microsoft.SharePoint.WebPartPages.WebPartMobileAdapter.CreateChildControls() +129
System.Web.UI.Control.EnsureChildControls() +166
System.Web.UI.Control.PreRenderRecursiveInternal() +73
System.Web.UI.Control.PreRenderRecursiveInternal() +240
System.Web.UI.Control.PreRenderRecursiveInternal() +240
System.Web.UI.Control.PreRenderRecursiveInternal() +240
System.Web.UI.Control.PreRenderRecursiveInternal() +240
System.Web.UI.Control.PreRenderRecursiveInternal() +240
System.Web.UI.Control.PreRenderRecursiveInternal() +240
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4090
Even after waiting several hours, deleted posts are still in the Newsfeed. There are no failed timer jobs in Central Admin and it happens for all users.
Event Log and ULS show similar messages and I can't find any clues why it's happening.
We don't have the problem when we post "Site Feeds". Those immediately disappear from the Newsfeed after deletion.
I have (2) questions:
Why are deleted posts showing up in the Newsfeed,
And why isn't SharePoint showing a typical "page not found" when they are clicked?
I have implemented the SharePoint:DateTimeControl in a very simple webpart
<SharePoint:DateTimeControl ID="dtStartdate" runat="server" DateOnly="true" />
The problem is when I click on the control it renders an exception
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Microsoft.SharePoint.Utilities.SPUtility.GetThemedImageUrl(String originalUrl, String themeKey) +199
Microsoft.SharePoint.WebControls.DatePicker..ctor() +1460
Microsoft.SharePoint.WebControls.SPDatePickerControl.InitDatePicker() +44
Microsoft.SharePoint.WebControls.SPDatePickerControl.set_MinJDay(Int32 value) +25
Microsoft.SharePoint.ApplicationPages.DatePickerFrame.Page_Load(Object sender, EventArgs e) +1708
System.EventHandler.Invoke(Object sender, EventArgs e) +0
System.Web.UI.Control.LoadRecursive() +94
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2935
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929
Any advice or help to resolve this is highly appreciated, thanks!
I know it's been a while since you asked this but having just solved something very similar I thought I'd share my (simple) solution.
Make sure you have a site collection created at the root of the web app.
I was working on a web part in http: //webapp/sites/mysitecollection and had the above error. Looking at http: //webapp gave me a 404 so I created a root site collection and now the datepicker in my sitecollection works fine.
I'm trying to migrate an existing 6.01.01 site to Windows Azure web pages for testing some new features. I had so much trouble going about doing so that I decided to start over and just get version 6.1.1 running on Azure from the community install. Now I'm running into an error when I finish the InstallWizard. The exception in the log is as follows:
DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object.
---> System.NullReferenceException: Object reference not set to an instance of an object.
at DotNetNuke.Framework.DefaultPage.InitializePage()
at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace ---
Does anyone have any idea on what might be causing this or even how to debug it? I'm very new to Azure and DNN.
NOTE: In order to get the InstallWizard to work I had to make a few changes to the web.config file. They are as follows:
replace the default db string with our SQL azure string
put in a long request timeout
comment out the url rewriting modules
When i try to open sharepoint in my windows server, following error appears:-
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
Can anybody help me on this.
Following is the error:-
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[COMException (0x80070005): Access is denied.
]
System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) +377678
System.DirectoryServices.DirectoryEntry.Bind() +36
System.DirectoryServices.DirectoryEntry.get_IsContainer() +31
System.DirectoryServices.ChildEnumerator..ctor(DirectoryEntry container) +26
System.DirectoryServices.DirectoryEntries.GetEnumerator() +25
Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.System.Web.IHttpModule.Init(HttpApplication app) +471
System.Web.HttpApplication.InitModulesCommon() +65
System.Web.HttpApplication.InitModules() +43
System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +729
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +298
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +289
Any help is appreciated.
Do the Following to get the idea about exact error :
Go to C:\inetpub\wwwroot\wss\VirtualDirectories\ of your web application for which you have error.
Open and Edit web.config file and set customErrors mode to Off.
See what is the main error.
Let us know the error.
This error is occured when a login you are using is not having enough permission to login to the sharepoint site.
Check Permission of a user, it has the permission to login or not?
If you are able to able to access CA then you can add this user as Site Collection administrator, and access the sharepoint site.
Hope this helps
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Our networks guys installed this patch over the weekend to our single server sharepoint front end: KB956716
http://www.microsoft.com/downloads/details.aspx?familyid=a7fda284-273c-42ab-8188-433beaacca86&displaylang=en
http://support.microsoft.com/kb/956716
After which our search service stopped working.
When attempting to do a search on any of our apps we get this error: System.IndexOutOfRangeException: DisplayInAdminUI (stack info below)
I logged into the shared services admin page and when I click on search settings it just crashes too.
I have included the event viewer error below as well...
Any ideas?
Thanks,
Christopher
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 12/30/2008
Time: 1:03:35 PM
User: N/A
Computer: VKSPS02
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/30/2008 1:03:35 PM
Event time (UTC): 12/30/2008 7:03:35 PM
Event ID: 90ade1cc6d5949a3ae2ea97afa5d75e6
Event sequence: 19275
Event occurrence: 67
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1927250994/Root-1-128751076993856152
Trust level: WSS_Minimal
Application Virtual Path: /
Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\vktoday80\
Machine name: VKSPS02
Process information:
Process ID: 8136
Process name: w3wp.exe
Account name: VIRCHOWKRAUSE\SharePointSSPApp
Exception information:
Exception type: IndexOutOfRangeException
Exception message: DisplayInAdminUI
Request information:
Request URL: http://sitename.domain.net/searchcenter/Pages/peopleresults.aspx?k=lori
Request path: /searchcenter/Pages/peopleresults.aspx
User host address: 172.30.202.56
User: VIRCHOWKRAUSE\JF11767
Is authenticated: True
Authentication Type: NTLM
Thread account name: DOMAINNAME\SharePointSSPApp
Thread information:
Thread ID: 6
Thread account name: DOMAINNAME\SharePointSSPApp
Is impersonating: False
Stack trace: at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at Microsoft.Office.Server.Search.Query.ConsumerScopeCache.Refresh()
at Microsoft.Office.Server.Search.Query.ConsumerScopeCache.EnsureFresh()
at Microsoft.Office.Server.Search.Query.ScopeCache.TryGetScope(Guid siteGuid, Int32 id, ScopeInformation& scope)
at Microsoft.Office.Server.Search.Query.ScopeCache.TryGetSharedScope(Int32 id, ScopeInformation& scope)
at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnHiddenObject()
at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.SetPropertiesOnHiddenObject()
at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnPreRender(EventArgs e)
at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Server Error in '/' Application.
DisplayInAdminUI
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IndexOutOfRangeException: DisplayInAdminUI
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[IndexOutOfRangeException: DisplayInAdminUI]
System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName) +1433771
System.Data.SqlClient.SqlDataReader.GetOrdinal(String name) +102
System.Data.SqlClient.SqlDataReader.get_Item(String name) +12
Microsoft.Office.Server.Search.Query.ConsumerScopeCache.Refresh() +1241
Microsoft.Office.Server.Search.Query.ConsumerScopeCache.EnsureFresh() +58
Microsoft.Office.Server.Search.Query.ScopeCache.TryGetScope(Guid siteGuid, Int32 id, ScopeInformation& scope) +75
Microsoft.Office.Server.Search.Query.ScopeCache.TryGetSharedScope(Int32 id, ScopeInformation& scope) +68
Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnHiddenObject() +2503
Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.SetPropertiesOnHiddenObject() +41
Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnPreRender(EventArgs e) +1977
Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.OnPreRender(EventArgs e) +11
System.Web.UI.Control.PreRenderRecursiveInternal() +86
System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal() +62
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2041
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
I've had a similar experience with a corrupt search index (caused by the indexing server randomly rebooting) and unfortunately the only way to fix it was to Stop the Search Services and Start them again. This is done through Central Admin-Operations-Topology and Services-Services on Servers.
Not that we were getting this error - the IndexOutOfRangeException error you are getting relates to something going out of the bounds of a list or something when displaying the UI rather than something to do with the search index. However, the behaviour you describe is the same as we were getting - searches returning errors and not being able to access the Search configuration area in the Shared Services Provider.
Note that this is not like stopping and starting a Windows service - stopping the search service uninstalls it from the indexing server and starting it re-installs it so you will lose your search index and will have to do a full crawl to get it back. So be very sure that you are out of other options and are willing to lose your search index before going down this path.
Well I broke down and opened a support ticket w/ M$. They did resolve the issue quite quickly. We use lan desk to push our patches to our servers. Our networks guys didn't run the sharepoint product config wizard after the patch was installed. I guess this needs to be done on any update to the binaries which most of the patches do update..
So we ran the config wizard, it failed. Then tries to run it using command line:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>PSCO
NFIG -CMD UPGRADE -INPLACE B2B -FORCE -WAIT
That failed too... but just on the last step of restarting the service (found that info in the log). So we started the services manually, reset iis. and it WORKED!
I guess our network guys need to learn to run the Sharepoint Configuration Wixard or Psconfig at the command prompt.