Application Error Access _admin Createsite Aspx
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ upgrade spcontentdatabase object reference not set to an instance of an object Search related threads Remove From My Forums Asked invalid object name 'webs' sharepoint 2013 by: Application error when access /_admin/createsite.aspx, Error=This page has encountered a critical
Test-spcontentdatabase Invalid Object Name 'webs'
error SharePoint > SharePoint 2013 - Setup, Upgrade, Administration and Operations Question 0 Sign in to vote Hi, I have
Mount Spcontentdatabase Invalid Object Name Webs
tried to created a web application using central administration and after few minutes it show the page can't display error but shows in the webapp list. Once i tried to see the Genaeral settings it gives me the error "Updates are currently disallowed on GET requests. To allow updates on a GET, set the 'AllowUnsafeUpdates' property on SPWeb." which i have solved using some powershell script. Now when i go to create site collection with any template then i got the following error message (from ULS log): Application error when access /_admin/createsite.aspx, Error=This page has encountered a critical error. Contact your system administrator if this problem persists. at Microsoft.SharePoint.ApplicationRuntime.SafeControls.IsSafeControl(Boolean isAppWeb, Type type, String& unsafeErrorMessage) at Microsoft.SharePoint.WebPartPages.TypeCache.CheckIfSafeControl(Type type, Boolean isAppWeb) at Microsoft.SharePoint.WebPartPages.TypeCache.get_Item(Type type, Boolean isAppWeb, Boolean disableSafeControlsCheck) at Microsoft.SharePoint.WebPartPages.WebPart.WriteXmlGlobal(Boolean disableSafeControlsCheck) at Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.Serialize(SerializationMode mode, BinaryWebPartSerializerFlag binaryWebPartSerializerFlags, BinaryWebPartSerializerWriter writer) at Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.Serialize(SerializationMode mode, BinaryWebPartSerializerFlag binaryWebPartSerializerFlags) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartToStore(WebPart webPart, Int32
various reasons. It could be that the Alternate access mapping is set incorrectly or some orphan entries in your database or you've set content hub or environment is unstable and you notice Upgrade required when you navigate Central Admin > System Settings > Manage Servers First thing tried was to use PowerShell to create site collection thought may be this slip the attention of the ward and could let me create site collection. Nope doesn't work. Checked for environment stability by navigating to Central Admin> System Settings > Manage https://social.technet.microsoft.com/Forums/office/en-US/bcd72575-93ed-4782-b29d-eee7a63c4c0d/application-error-when-access-admincreatesiteaspx-errorthis-page-has-encountered-a-critical?forum=sharepointadmin Servers. Didn't find any server with status upgrade required which means may be cumulative update was installed but psconfig wasn't executed or failed. Checked the alternate access mapping intranet, extranet and default urls were intact For Content Hub, checked the Managed Metadata Proxy Service Application properties and unchecked the last two options that didn't resolve the issue Had a look a at ULS logs http://sp-vinod.blogspot.com/2012/02/cannot-create-site-collection-error.html again and pointed something about the content database. Change your central url from default to : http://centraladmin:portnumeber/_admin/DatabaseStatus.aspx and notice for any unusual databases or the ones not responding. Found that the one which wasn't responding was orphan database added some time back but didn't delete. Run the following command in Powershell orphanedDB = Get-SPDatabase | where{$_.Name -eq "Content Database Name"}$orphanedDB.Delete() Performed an IIS reset and voila now able to create site collection Posted by Vinod Kevaliya at 02:47 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) View my complete profile Linkedin Profile My Linked Profile Blog Archive ► 2011 (3) ► July (3) ▼ 2012 (56) ► January (1) ▼ February (3) Cannot create site collection error object referen... This view cannot be displayed because the number o... error the search service instance on this server i... ► March (13) ► April (7) ► May (5) ► June (5) ► July (5) ► August (2) ► September (9) ► October (2) ► November (1) ► December (3) ► 2013 (17) ► January (
for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://sharepoint.stackexchange.com/questions/112358/not-able-to-create-web-application-in-sp-2013 this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a invalid object question Anybody can answer The best answers are voted up and rise to the top Not able to Create Web Application in SP 2013 up vote 0 down vote favorite I am trying to create a new web application in our SP 2013 Farm and i am not successful in doing it .I had created 4 web apps before without any invalid object name issue and today when i tried to create a new webapp i am getting "Request Timed out " Also i observed that the ContentDB is getting created in the DB Instance but there are no sites that are created in IIS ,I have 4 WFE and 3 App Servers .I was not able to find much in the ULS Logs ULS Logs Provisioning of the web application, SharePoint - 80, has encountered the following error: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, SPProcessAccount processAccount, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures) Application error when access /_admin/extendvs.aspx, Error=Request timed out. Update 2 I also observed one more issue which is when I am creating the web application now it is creating the site in Central Admin Server but it's not creating the site on any of the Web front ends. Also it's still giving the Request timeout. I already checked the Web application servi