Central admin 404

Hi 
The client has Sharepoint 2013, from couple of days when the Central administration site is being accessed , we received  404 resource not found, however when we add /default.aspx soon after the URL the sites seems to work as expected.
when accessed from all programs and Microsoft share Point 2013 Products and when clicked on SharePoint 2013 Central Administration... we still receive 404.
After a day or 2 the issue gets resolved all by itself and reappeared again.
what would cause that to happen?
Checked the configuration (c:\inetpub\temp\appPools\SharePoint Central Administration v4)
Checked Default document, and there are no changes being made.
Satyam..

Hi Satyam,
Please recycle the Central Administion web application pool from IIS manager, and check results again
Plase re-add the service account name and password for Central Administration site from IIS manager, see if it works.
You can also run the SharePoint congiration wizard and test again.
http://social.technet.microsoft.com/Forums/office/en-US/68d5913b-dec3-49a0-895e-d8b1770ff4f2/sharepoint-2010-central-administration-is-not-working?forum=sharepointgeneralprevious
http://www.pengzhang.ca/blog/2011/09/09/sharepoint-central-administration-site-returns-404/
Thanks
Daniel Yang
TechNet Community Support

Similar Messages

  • Ran the reprovision powersheel sripts still no Central admin site on a 404 error

    I still have no central admin site.
    When I call it thru the browser I get a 404 error.
    I ran these scripts:
    .\psconfig.exe -cmd adminvs
    -unprovision
    .\psconfig.exe -cmd adminvs
    -provision -port 9999
    -windowsauthprovider onlyusentlm
     the message came back telling me that the CA is at the location etc.. no errors were thrown when I ran the scripts.
    What Else can I check?

    I'm on  windows server 2012 and this is SharePoint 2013
    Windows Authentication is Enabled  has 401 challenge.
    I also did this:
    Problem: SharePoint Central Admin Page diplays HTTP 404 Error after Installation
    Cause: HTTP Verbs are not configured to allow in IIS
    Resolution: Go to the server where SharePoint Central Admin is hosted, Start -> Run -> Type inetmgr -> Click OK -> Expand Server_Name -> Expand Sites -> Click Web Application -> Click Request Filtering under IIS on the
    Right -> Double click "Request Filtering" -> Click on HTTP Verbs->Click Allow from the top right corner and enter GET and click OK. Repeat the same steps to allow other verbs POST, HEAD, CONNECT, PUT, DELETE, TRACE, OPTIONS and Central Administration
    started to load properly
    Note: If you require, future web applications not to face this issue, then the settings has to be applied to the IIS level as well. Following are the steps to apply the same
    Go to the server where SharePoint Central Admin is hosted, Start -> Run -> Type inetmgr -> Click OK -> Click on Server_Name -> Click Request Filtering under IIS on the Right -> Double click "Request Filtering" -> Click on HTTP Verbs->Click
    Allow from the top right corner and enter GET and click OK. Repeat the same steps to allow other verbs POST, HEAD, CONNECT, PUT, DELETE, TRACE, OPTIONS.
    Still no Central Admin Site, still get the Error message that the web page can not be found. hTTP 404

  • Team Foundation Server 2013 update 4 New Install - Error 503 Service Unavailable for Sharepoint Central Admin

    Hello,
    I ran a new install of Team Foundation Server and let it install the built in SharePoint pieces on a single server setup. After the install i'm able to access the
    http://teamfoundation:8080/tfs/ address without issue but am unable to create a project. When I attempt to create a project I get the following error:
    TF30172: You do not have permission to create a new team project (when checking security i'm a member of the project collection administrators and Team Foundation Administrators)
    This led me to look at the sharepoint central administration site where I receive the following error:
    Error 503 Service Unavailable
    I've gone through and validated the identity is set correctly in IIS for the following services:
    SharePoint Central Admin v4
    SharePoint15AppPool
    The SharePoint Web Services Root is set as LocalService instead of the domain user.
    The identity domain user is setup as local administrator on the Team Foundation Server. They are all set to use .net v4.0.30319 with integrated Pipeline mode.
    Any help would be great!
    Thanks!
    Eric

    Hi Eric,      
    Thanks for your post.
    Please share your detailed team project creation log here.
    In your TFS Admin Console>>Extensions for SharePoint Products tab, ensure SharePoint Web Application shows correctly in the right panel. And go to TFS Admin Console>>Application Tier>>SharePoint Web Applications tab, ensure your SharePoint
    web application displays in the right panel, then select your SharePoint web application and click Repair Connection, ensure can repair successfully.
    In your IIS Manager, select your SharePoint Central Administration V4 site and click Browser:17012(http) in the right panel, check if your SharePoint Central site can be opened successfully or not. If your SharePoint Central site cannot be accessed, I think
    this issue relate to your SharePoint site, you should contact SharePoint experts to resolve this issue first. After you resolved this issue and your SharePoint Central Admin site can be accessed correctly, then try to create your team project(within SharePoint
    site) again, if there still has issue when creating team project, please share the detailed error message here, we will try to resolve it.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Sharepoint 2013 foundation central admin "something went wrong"

    I recently installed SP1 (the bad version before it was pulled) on my SharePoint 2013 foundation server. I ran psconfig and made sure my databases were up to date after SP1. I checked central admin after psconfig and everything was working and good to
    go. I have little need to access it on a regular basis, so after the install I haven't attempted to access central admin for approximately a month. As the updated SP1 just hit a few days ago I attempted to pop into CA to does some work on the site in preparation,
    and I received the sorry something went wrong message. I thought it may be an issue due to the bad version of sp1 that was installed and/or high ram utilization. As this is a standalone box in production I could not reboot easily. I was finally able to do
    the install last night, and it appears the problem is still ongoing. The site has been in production for about 6 months now, I have never had any issues hitting CA previously. SharePoint is running as a VM, and we have decked the specs out for it. We are allocating
    4 cores and 24gb of ram to the site, and we are not seeing anything close to max resource utilization on the hypervisor or on SharePoint. I checked the correlation ID that SharePoint provides in the ULS logs and the only thing close to an error I get is a
    message "cannot find site lookup info for request uri
    http://localhost:<port binding>/." this is followed by "Application error when access /, Error=Exception of type 'System.ArgumentException' was thrown.". I'm exporting a copy of the vhd to experiment on in a test environment now, so
    I will update this if I get more info. I don't think this was caused by SP1 as I was able to hit the CA page after doing the upgrade, but other than standard users interacting with the site since SP1, there have been no changes from an administration perspective.
    I am the only one who touches the site here so I know changes weren't made without my knowledge. Anyone have a clue what could be causing this?

    I see, good to know. IT couldn't have been someone visiting the CA page turning it on, as its an IIS only setting. I cant say that no one ever would have changed the settings, but generally I am the administrator for this server and my colleagues don't touch
    it.
    When I say default content pages I mean my SharePoint site collection pages. The problem I was having when I started this thread was about CA, but I also noticed on my site collection that FBA is turned on as well. When I turn this off a few things
    happen, generally I get a message around authorization saying that the site collection admin or farm admin cannot view the page. On the few occasions I am able to login, the page content often renders without any css, so its just plain text on the page, or
    it places the text in random locations around the page. Generally when I try to navigate though I just get an access denied message shortly therafter. Keep in mind I have done absolutely no setup at all around FBA, so I'm not sure why turning off an authentication
    method that has not been configured at all would not allow me to access my site pages.

  • People picker works in Central Admin but not other site collections

    Hello
    I am having a sudden problem with adding users to permissions for document libraries. It appears to only affect the main site collection. The people picker displays some users that are already in site collection when you start typing letters of the name
    of the user. However at some point in the typing the message appears "sorry we're having trouble reaching the server." The problem does not occur in Central Admin when adding permissions. Using Fiddler there is an error when I get the message "sorry..."
    "500, HTTP, SERVERNAME, /_vti_bin/client.svc/ProcessQuery." Also when I go to the library and select "shared with" I get error "Unexpected response from server. The status code of response is '500'. The status text of response
    is 'System.ServiceModel.ServiceActivationException'." I believe they are connected. Any help is appreciated.

    Hi Jeffrey,
    Please try to verify “HTTP Activation” feature per the article below:
    http://blog.karstein-consulting.com/2014/02/18/sharepoint-2013-people-picker-error-sorry-were-having-trouble-reaching-the-server/
    Are you using custom FBA provider for web application other than CA site which might be causing misconfiguration in web.config?
    Could you please provide more complete related error message from ULS log for troubleshooting?
    Regards,
    Rebecca Tu
    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]

  • SQL Server Reporting Services Service - missing in Central Admin

    Hi,
    I am following "Install Reporting Services SharePoint Mode for SharePoint 2013" at
    http://msdn.microsoft.com/en-us/library/jj219068(v=sql.110).aspx#bkmk_install_SSRS_sharedservice .  
    I have a WFE, APP and SQL server. We have SQL Server 2012 SP1. Central Admin is installed on the APP server.
    I installed the Reporting Services Add-In on the WFE using rssharepoint.msi  per "Install or Uninstall the Reporting Services Add-in for SharePoint"
    http://technet.microsoft.com/en-us/library/aa905871(v=sql.110).aspx  and then ran
    Install-SPRSService and Install-SPRSServiceProxy
    successfully on the WFE.
    I cannot see "SQL Server Reporting Services Service" in Central Admin.
    (Central Admin is on the APP server)
    get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance finds the service but does not successfully provision it.
    The SharePoint LOG just shows: Updating SPPersistedObject SPServiceInstanceJobDefinition Name=job-service-instance-8efb2291-4f12-4fea-bb52-63e86f486e6e. Version: -1 Ensure: False, HashCode: 49732161, Id: 81b73567-58c0-4e94-9072-be5ab39077af, Stack:
    I tried installing the "Reporting Services Add-in for SharePoint" again using
    rssharepoint.msi on the APP server (since it has central admin), and the install rolls back. The error after running
    rsCustomAction.exe /i from the command line - per
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/880b77ac-3228-40ce-99dc-12b0ff0eb46a/reporting-services-add-in-for-sharepoint-installation-interrupted?forum=sqlreportingservices
    Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
    or one of its dependencies. The system cannot find the file specified.
    also saw: SharePoint Web Application content files could not be propagated because no Web Applications could be detected or they are off-line. Which may be normal.
    Q. which servers should I be installing the "Reporting Services Add-in for SharePoint"?
    Q. how can I fix the errors I see?
    macrel

    Hi Ketak. Thank you for replying. I already followed your instructions - specifically -
    You do not see the SQL Server Reporting Services  service in SharePoint Central Administration after installing SQL Server 2012 SSRS in SharePoint mode
    I get the following error when I run rssharepoint.msi on the APP sever (where Central Admin is installed). I have to run this other wise
    Install-SPRSService and Install-SPRSServiceProxy 
    are not recognized as commands on that server.
    Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
    or one of its dependencies. The system cannot find the file specified.
    macrel

  • Can you install Workflow Manager 1.0 on Central Admin App Server Machine in 3-tier SharePoint Farm?

    Hi,
    I have just realised when looking at doing a Workflow that 2013 Workflows not available (you need to install Workflow Manager Farm). I understand why from a tenant installation perspective, but we are on-premise.
    Can someone tell me if I can install Workflow Manager 1.0 (seen you have to now install WM 1.0 Refresh version) on the Central Admin App Server Machine in a 3 tier SharePoint farm. 3 WFE, 4 APP Servers, 1 DB Server and 1 DB Analysis Services Server.
    I did test on a test farm 1WFE, 1 APP Server (with CA) and 1 Database Server. We are getting issues with the WFE Server having issues booting up or losing connection - possibly faulty network card. This may in no way be related to the install,
    but just in case. 
    Any help appreciated.
    Thanks.
    John.

    Yes, you can install WFM on any server in a SharePoint farm.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • How can I determine what sites are being referenced within Central Admin Upgrade and Migration Manage Databases Upgrade Status?

    When I go to Central Admin > Upgrade and Migration  > Manage Databases Upgrade Status, I have 2 content databases which have the status:
    Database is up to date, but some sites are not completely upgraded.
    How can I determine which sites are not completely upgraded?

    Manage Databases Upgrade Status will provide you all active and offline DB details, you can get same result
    using below PowerShell cmdlet.
    Get-SPDatabase and Get-SPContentDatabase will provide all active database/Content DB in Farm which include Service application db, central admin DB.
    Get-SPDatabase | Format-Table Name, ID
    Coming back to your question, if you find that there are some site are not completely upgraded then run below command and understand the cause if issue on specific DB.
    Test-SPContentDatabase WSS_ContentDB_Name
    If you find any missing file issue in DB then resolve these issue to upgrade content database.
    (verify all customizations referenced within the content database are also installed in the web application. This cmdlet can be issued
    against a content database currently attached to the farm, or a content database that is not connected to the farm )
    Use the Upgrade-SPContentDatabase cmdlet
    to resume a failed database upgrade or begin a build-to-build database upgrade against a SharePoint content database
    Upgrade-SPContentDatabase WSS_Content
    reference:
    http://technet.microsoft.com/en-us/library/ff607813(v=office.15).aspx
    http://technet.microsoft.com/en-us/library/ff607941(v=office.15).aspx
    If my contribution helps you, please click Mark As Answer on that post and
    Vote as Helpful
    Thanks, ShankarSingh(MCP)

  • How to remove duplicate template names in central admin - Sharepoint 2013

    Hi Guys,
    I can see some duplicate site templates in central admin (SharePoint 2013).
    How can i remove it? Please help me out on this.
    Regards,
    Krishna

    Hello,
    As there are many duplicate templates you could try below two steps.
    1) Find the templates :
    # Find the template name of SharePoint site using PowerShell
    $web = Get-SPweb <Site Url>
    Write-host “Web Template:”
    $web.WebTemplate ” | Web Template ID:”
    $web.WebTemplateId
    $web.Dispose()
    # To get a list of all web templates, use the following PowerShell code
    function Get-SPWebTemplateWithId
         $templates =
    Get-SPWebTemplate | Sort-Object "Name"
         $templates |
    ForEach-Object {
    $templateValues = @{
         "Title" =
    $_.Title
         "Name" =
    $_.Name
         "ID" =
    $_.ID
         "Custom" =
    $_.Custom
         "LocaleId" =
    $_.LocaleId
    New-Object PSObject -Property
    $templateValues | Select @("Name","Title","LocaleId","Custom","ID")
    Get-SPWebTemplateWithId | Format-Table
    2) Remove the ones you want to
    $templateTitle = "TitleOfTemplateToBeZapped"
      $site = Get-SPSite <Site coll url>
      $templates = $site.GetWebTemplates(1033)
    #lcid, 1033 = U.S.    $badTemplate
    = $templates | where { $_.Title
    -eq $templateTitle }
      if ($badTemplate
    -ne $null) {
        # the hidden feature Id is the first part of the template 
        #    name for custom web templates
        $id = $badTemplate.Name.substring(0,
    $badTemplate.Name.IndexOf("#"))
        $badId = [System.Guid]($id)
        $site.Features.Remove($badId)
        write-output "Template '$templateTitle' has been removed"
    } else {
        write-output "No template was found with the title of '$templateTitle'"
      $site.Dispose()

  • Issues connecting to SSRS 2012 SP2 through SharePoint 2013 SP1 Central Admin

    When trying to open "system settings" for the SSRS Service application in Central Admin, I get the error "The remote server returned an error: (500) Internal Server Error."
    Also, when trying to create a new Report Builder Report within SharePoint, I get an error "403 Forbidden".
    The ULS log entry for this is:
    Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.ServiceModel.ProtocolException: The content type text/html of the response message does not
    match the content type of the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML
    1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">  <html xmlns="http://www.w3.org/1999/xhtml">  <head>  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
     <title>500 - Internal server error.</title>  <style type="text/css">  <!--  body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}  fieldset{padding:0 15px
    10px 15px;}   h1{font-size:2.4em;margin:0;color:#FFF;}  h2{font-size:1.7em;margin:0;color:#CC0000;}   h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;}   #header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet
    MS", Verdana, sans-serif;color:#FFF;  background-color:#555555;}  #content{margin:0 0 0 2%;;}  .content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;;}  -->  </style>  </head>  <body>
     <div id="header"><h1>Server Error</h1></div>  <div id="content">   <div class="content-container"><fieldset>   '. ---> System.Net.WebException: The remote server
    returned an error: (500) Internal Server Error. 
        at System.Net.HttpWebRequest.GetResponse() 
        at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)     --- End of inner exception stack trace ---    Server stack trace:  
        at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding) 
        at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) 
        at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) 
        at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) 
        at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) 
        at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) 
        at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:  
        at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) 
        at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) 
        at Microsoft.ReportingServices.ServiceContract.IReportServiceManagement.GetSystemProperties(ICollection`1 properties) 
        at Microsoft.ReportingServices.SharePoint.SharedServiceProxyHelper.<>c__DisplayClass9.<GetSystemProperties>b__8(IReportServiceManagement mchannel) 
        at Microsoft.ReportingServices.SharePoint.SharedService.ProxyHelper.DoManagementChannelCall(Action`1 caller) 
        at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.get_SystemProperties() 
        at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.LoadSettings() 
        at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.OnInit(EventArgs e) 
        at System.Web.UI.Control.InitRecursive(Control namingContainer) 
        at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 
        at System.Web.UI.Page.HandleError(Exception e) 
        at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 
        at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 
        at System.Web.UI.Page.ProcessRequest() 
        at System.Web.UI.Page.ProcessRequest(HttpContext context) 
        at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 
        at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    Any ideas on what might be the issue would be greatly appreciated.

    Hi Joshua.Arenz,
    As per my understanding, you configured SSRS 2012 of SharePoint mode, when you click system setting in Central Admin, you got the error message.
    According to the error message, the Reporting Services service application is not configured correctly. Please make sure you created service application correctly by following steps:
    In SharePoint Central Administration, in the Application Management group, click Manage Service Applications.
    In the SharePoint toolbar, click the New button.
    In the New menu, click SQL Server Reporting Services Service Application.
    In the Create SQL Server Reporting Services Service Application page, enter a name for the application.
    In Application Pool section, create a new application pool for the application (recommended). Then select or create a managed account for the application pool.
    In the Database Server, you can use the current server or choose a different SQL Server.
    In Database Name the default value is ReportingService_<guid>, which is a unique database name. If you type a new value, type a unique value.
    In Database Authentication, the default is Windows Authentication.
    In the Web Application Association section, select the Web Application to be provisioned for access by the current Reporting Services Service Application.
    Click OK.
    For more information about Creating a new Reporting Services Service Application, please refer to the following document:
    http://niftit.com/how-to-install-configure-reporting-services-sharepoint-2013/
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu

  • Custom Timer Jobs not visible in Central Admin Job Definitions

    I have multiple custom timer jobs which I was using on old farm, and it was successfully working and was visible in the Central Admin Job Definitions.
    But ever since I moved to new farm, by restoring the site collections from old to new farm, and deployed the custom timer jobs on new farm, they are not visible in Central Admin Job Definitions.
    I tried to change the scope of the solution to "Web Application", and deployed it's wsp in new farm, then also they are not visible in Job Definitions. But I can see them in "Farm Solutions", they have been successfully deployed.
    Please suggest what should I do.

    public override void FeatureActivated(SPFeatureReceiverProperties properties)
    SPWeb wb = properties.Feature.Parent as SPWeb;
    if (wb == null)
    throw new SPException("Error obtaining reference to context Site ");
    // make sure the job isn't already registered
    foreach (SPJobDefinition job in wb.Site.WebApplication.JobDefinitions)
    if (job.Name == List_JOB_NAME)
    job.Delete();
    RSS listLoggerJob = new RSS(List_JOB_NAME, wb.Site.WebApplication);
    SPHourlySchedule schedule = new SPHourlySchedule();
    schedule.BeginMinute = 0;
    schedule.EndMinute = 59;
    listLoggerJob.Schedule = schedule;
    listLoggerJob.Update();
    public override void FeatureDeactivating(SPFeatureReceiverProperties properties)
    SPWeb wb = properties.Feature.Parent as SPWeb;
    // delete the job
    foreach (SPJobDefinition job in wb.Site.WebApplication.JobDefinitions)
    if (job.Name == List_JOB_NAME)
    job.Delete();

  • Central Admin AND WebApp on 443 for hosting HNSC?

    Greetz!
    First a couple things about my environment:
    - I'm using SP2013 Enterprise on Windows 2012R2 with IIS8
    - SNI isn't an option since I need to support IE on WinXP (plus I believe it needs to be part of the initial IIS installation which it wasn't AFAIK)
    - I'm using a wildcard SSL certificate
    - I setup Central Administration on port 443 and gave it a URL spca.company.com
    - I have a single IP for my APP server and a single IP on my single WFE.
    Now I need to setup a non host header web application on which I am going to create an unknown number of host named site collections (HNSC). When I tried to do this in Central Admin I got an error saying this IP and port were already in use. To do this the
    web app can't use a host header. I want this to be on HTTPS as well. If I can have this on port 80 and still have my HNSCs on port 443 that's an option since I won't be routing people to the root site collection and it will simply be there as per the requirements.
    Is it possible to set up a web app on port 80 and have the HNSCs on port 443 while still having CA on 443?
    Is it possible to set up a web app on port 444 and have the HNSCs on port 444 while still having CA on 443?
    I attempted to use Set-SPCentralAdministration to move it to port 444 and then to 80 but both attempts failed. I'd be game to move CA to port 80 if you know how.
    Love them all...regardless. - Buddha

    Hi Stacy,
    Thanks for your reply. I had done something very similar to the sharepointpapa.com walkthrough yesterday and wasn't able to get 443 to come up. I will try the walkthrough on this site this morning.
    I am on a split back-to-back topology. My APP and DB are on my internal network with an internal IP of 10.30.X.X and my WFE with the public IP of 192.168.X.X. I have a wildcard SSL certificate *.company.com
    I was able to get the web application created by running the powershell on the 10.30.X.X App server but instead of using 'https://machinename/' for the webappurl I used  'https://root.company.name/' for which I have a DNS Entry A record which
    points to the public IP of 192.168.X.X After I created the Web App I went into IIS and made sure that the SSL Certificate was bound to the site. There was only the 10.30.X.X IP available to bind too. I tested using both the IP and 'All Unassigned'. I
    then created a HNSC site collection with the same url of 'https://root.company.com' but wasn't able to connect.
    I'm just wondering if my A record for root.company.com points to the 192.168 IP and the application is created on the 10.30 IP is it not able to resolve correctly? We have NAT in between our network segments so maybe that's fouling it up?
    Love them all...regardless. - Buddha

  • User missing from all site collections but present in User Profile (Central Admin)

    I have a user who does not show up in "People and Groups" (or if I search for this user) in any of the site collections but does show up when I look up his user profile on Central Admin. I've tried to add this user to the site collection using
    the following command, but I get an error: " The specified user domain\accountname could not be found."
    Get-SPWeb 'http://site' | New-SPUser -UserAlias 'domain\accountname'
    Idk if this is related, but on this user's profile, "Personal Site" field shows up as "SPSSITEERROR".
    Any help would be greatly appreciated.
    Thanks.

    Hi,
    I recommend to check if the user exists in Active Directory firstly.
    If yes, then the error will occur. And for the user profile of the user, it may due to the user profiles have not been synced with Active Directory yet.
    That "Personal Site" field shows up as "SPSSITEERROR" means that the MySite of that user has not been created successfully.
    I recommend to run User Profile Synchronization timer job and then check the results.
    Thanks,
    Victoria
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Victoria Xia
    TechNet Community Support

  • Central Admin site won't let anyone log in.

    I am trying to set up our production multi-server farm.  I have run the configuration wizard after creating the configuration database manually using powershell, and Central Administration site loads fine when opened directly from the application server
    which it is hosted on while logged in as the setup user account.  However, if i am on any other server or machine, it prompts for credentials and doesn't accept anything.  Also, if i am on the application server hosting the central administration
    site, and i try to sign in as the farm administrator account, it will not accept those credentials.  It won't even then accept the setup users credentials.  I have to close IE then re-open the central administration page in order to be able to administer
    anything.
    Here is a little more information:
    I already ran through the same type of installation on a sandbox machine in a single server environment, and it was working fine.  The only major difference at this time is that i am using separate accounts for the setup user and the farm administrator.
    I have tried to push forward with my deployment, however, i get an error when trying to set up the search service.  After running a set-spenterpriseSearchService command i get an error: "The specified credentials are invalid"
    I am using Kerberos authentication just like i did on the sandbox, and i have set up the SPNs for the SQL service account, farm admin account, application pool account, and the setup user account just in case.
    I am at a complete loss on this one, it seems like it is not able to validate any credentials, but i don't know how to verify that at all.  I did try to verify kerberos was working, but i didn't see any security logs regarding verification of any account
    at all, so i don't technically know if kerberos is working or not.
    Please help.  Thanks.

    From the login issue you described in your last post, this sounds a lot like a Kerberos configuraiton issue.  IIS will challenge for Basic, NTLM, and Negotiate protocols before issuing an access denied message (which it appears you were not even getting). 
    So, you may want to run the get commands from the KB article I posted to check the CA web site to see if only NTLM is configured which could cause the problem.  The cscript commands in the KB I posted still work on IIS 7.  I used them in Beta to
    fix the triple login prompt I was getting from Central Admin.  Regardless, when you have a Kerberos issue, you need to check multiple facets of the configuration:
    Account trusted for delegation in AD?
    Computer trusted for delegation in AD?
    No duplicate or missing SPNs (ldifde or setspn -l commands can provide listings)?
    IIS Web Sites configured for Negotiate protocol
    Sometimes you need to go to Component Services and find the DCOM WAMREG properties and allow local activation for service accounts though I thought this wasn't necessary in SP2010.
    Is the correct Service being registered?
    For instance if my web application is on a machine with FQDN server.host.com so that the NETBIOS name is "server," then I'd issue the following SPNs:
    "setspn -a HTTP/server.host.com <Service account w/ domain>" and "setspn -a HTTP/server <Service account w/ domain>"
    That being said, if you are using the same service account for everything (such as port 80 web app pool and CA app pool), then you may be having a duplicate SPN issue due to the port numbers not being handled properly in the browser. However, this issue
    should only exist in IE6.
    http://sharepointspot.blogspot.com/2008/12/non-standard-port-numbers-hotfix-for.html
    http://support.microsoft.com/kb/908209/en-us
    I agree with Rob_H that you may want to only allow NTLM for Central Admin. 
    Dan Luciano - Sogeti USA - MCP, MCTS WSS 3.0 and MOSS 2007 Configuration WSS 3.0 Applicaton Development

  • SQL Server Analysis Services not showing in Services on Server on Central Admin

    Hi All
    We have a Sharepoint 2013 farm set up (2xApp, 2xWeb, 1xSQL) and we have a number of excel powerpivot workbooks deployed and refreshing.
    This was all working fine, until recently when our Excel 2013 Tabular workbooks stopped refreshing manually.  This had worked fine in the past, but now is giving the following error:
    "An error occurred during an attempt to establish a connection to the external data source"
    The first thing I wanted to check was that the "SQL Server Analysis Services" was started in Services on Server within Central Admin.   However when i navigated to check this, I noticed that the service was no longer listed at all.
    I checked the Analysis services for Powerpivot is running on the server and it is registered within Data Models on Excel services.   
    There was recently some Windows updates that were applied to the servers, but i'm pretty confident that the refresh was working after these, however i cant rule out 100%.
    Hoping for any advice on what I can check/do here?
    Thanks!

    When i try to run that tool i actually get a strange error (we are running Enterprise Edition):
    "PowerPivot for SharePoint 2013 Configuration is missing prerequisites: SharePoint 2013 Enterprise Edition is required.
    For more information go to http://go.microsoft.com/fwlink/?LinkId=247828.
    Please address the validation failures and try again."
    Yes it looks like on the server hosting PowerPivot analysis server that a number of windows updates got applied.  However
    none look to be specifically about for SQL, and the 2 cumulative ones are for IE and Active X for Windows Server.

Maybe you are looking for