locked
Cannot connect to a Web site RRS feed

  • Question

  • Hello,

    I have a site xxxx.xxxx I tried to login butafter inputting User name and Password the blue progress bar is goinghalf-way and stop for ever ... ( 1 hour at least tested) I do not see any error in the event logs (Application, Security, System) where should I look to get some clue?

    The databases have been restored from an existing sharepoint environment. As they have the same UTL I am using the hosts file to access the test environment URLs.

    It is a site on SharePoint 2007

    the Hosts file has been modified as

    # Copyright (c) 1993-2006 Microsoft Corp.
    # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
    # For example:
    #      102.54.94.97     rhino.acme.com          # source server
    #       38.25.63.10     x.acme.com              # x client host
    127.0.0.1       localhost
    xx.xx.xxx.xx   abc.ad
    where xx.xx.xxx.xx is the IP of the server locally. abc.ad is the FQDN of the local server.

    I have access to Central Administratioon on the test server without issue.

    Web Authentication: Anonymous is disabled, Windows Authentication is Enabled.

    Ping URL is giving me the local server IP.

    I have check allow in the Anti-virus Forefront Client Security .

    Getting Website found. Waiting for reply...

    Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager







    • Edited by Felyjos Friday, January 11, 2013 7:40 PM
    Friday, January 11, 2013 6:19 PM

Answers

  • Hi,

    You are missing to important installations in your new SharePoint environment that exist in the old environment where you moved the databases from.

    Since you are getting an error screen, its not that you are unable to browse the site the issue is there is a problem with the site.

    You are missing the features:

          <WebFeatures>
            <!-- TeamCollab Feature -->
            <Feature ID="00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5" />
            <!-- MobilityRedirect -->
            <Feature ID="F41CC668-37E5-4743-B4A8-74D1DB3FD8A4" />        
            <!-- Knowledge Base Keywords List -->
            <Feature ID="75A0FEA7-12FE-4cad-A1B2-525FA776C07E" />
            <!-- Knowledge Base Knowledge Base List -->
            <Feature ID="75A0FEA7-D31D-491a-9177-F0E461A81E3F" />
            <!-- HelpDesk ExpertsList -->
            <Feature ID="75A0FEA7-E63B-4059-8F5A-CE9CBBADAD2A" />
            <!-- HelpDesk ServiceRequestsList -->
            <Feature ID="75A0FEA7-FE9D-4119-9615-2C2EF22D6FDB" />
            <!-- HelpDesk SupportFaqList -->
            <Feature ID="75A0FEA7-70E3-40b1-B395-C06F85D0D158" />
            <!-- HelpDesk Tasks -->
            <Feature ID="75A0FEA7-3B2A-4838-8A0C-57BA864FEED3" />
            <!-- Help Desk List Instances -->
            <Feature ID="75A0FEA7-97C5-4487-88E4-70FDE8F79B25" />
            <!-- Help Desk Modules -->
            <Feature ID="75A0FEA7-02CB-4f87-BB11-1FFDE748A953" />
            <!-- TSA Image -->
            <Feature ID="75A0FEA7-C54F-46b9-86B1-2E103A8FEDBA" />
            <!-- KB Provisioning Handler -->
            <Feature ID="75A0FEA7-84D9-447d-B9EC-BC49570874DB" />
            <!-- Post Provisioning Event Handler -->
            <Feature ID="75A0FEA7-B0EF-434e-90D6-CE997D970564">

    What this means is that you need to install the FAB40 Help Desk Template and Core

    Reference :

     Also, you have Reporting Services installed in the old environment as can be found by searching for the GUID 367b94a9-4a15-42ba-b4a2-32420363e018 on BING. However, if its not affecting the site you need to use then you may not need to setup RS In SharePoint integrated mode.

    You need to download and install the from the referenced URLs above the HelpDesk template and the Core installation and if these are the onl=y errors you should be good to go.

    Please reply to this post if you hae any additional questions and let us know if you arte successful as well

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders, Business Intelligence in SharePoint 2013.

    • Marked as answer by Felyjos Monday, January 28, 2013 8:45 PM
    Monday, January 28, 2013 12:04 AM
  • HI,

    They are deployed to the SharePoint root as Features. Whenever, you restore/move/upgrade a Farm all Apps/Solutions/Features need to be installed on the new farm so the references made to them in the ContentDbs can continue to work. The HelpDesk Template is part of the FAB40 that were created for ISVs and VARs to demonstrate what you could do easily with SharePoint. they were never meant to be production ready, their deployment model does not conform to best practices. You have to download and install from the links I provided and you should be good to go.. Reporting Services is usually used from a Centralized location. At some point you will want to resolve this issue as well but I don't think it will be necessary at this time to provide usability to your site. If this were production, you should have iterated through the issues in development prior to going live and I think that's kindof what you are doing now..

    I am glad I could help, have fun with SharePoint it ROCKS!! Please let me know how things go..

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders, Business Intelligence in SharePoint 2013.

    • Marked as answer by Felyjos Tuesday, January 29, 2013 6:36 PM
    Monday, January 28, 2013 10:21 PM

All replies

  • Hi,

    I understand that you cannot sign into a site when using host header.  Have you tried to not use the host header?

    Check the IE settings: Internet Options>Connections>LAN settings.  Make sure that ‘Automatically detect settings’ is unchecked.

    Thanks,

    Entan Ming

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttnmff@microsoft.com.


    Entan Ming
    TechNet Community Support

    Monday, January 14, 2013 6:38 AM
    Moderator
  • Hello,

    Yes "Automatically detect setting" is unchecked.

    Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Monday, January 14, 2013 5:11 PM
  • Hi,

    Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support.

    Thanks,

    Entan Ming

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttnmff@microsoft.com.


    Entan Ming
    TechNet Community Support

    Tuesday, January 15, 2013 7:18 AM
    Moderator
  • Hello Dom,

    If you are accessing the site from the server then you may have to disable loopback check. Following article will help you doing that

    http://support.microsoft.com/kb/896861?wa=wsignin1.0

    Other options what you can try

    -> Can you browse the site using IP address

    -> Can you browse the site from client workstation (or outside of the server)

    -> Check in ULS & IIS logs to see if the request is reaching the server.

    Wednesday, January 16, 2013 5:17 AM
  • Hello Satheesh,

    I cannot browse the site from anywhere. Don't forget this site is available only locally on the hosting server as I am using the HOSTS file to use the same URL for test and production and differentiate them through the HOSTS only. It launched the waiting for web site to reply but stay on the login screen doesn't matter which user I entered service account, farm admin, site collection admin, etc...

    When I ping the URL it replies with the correct IP for test.

    Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Wednesday, January 16, 2013 2:50 PM
  • Okay.

    Disable Loopback Check

    • Click Start, click Run, type regedit, and then click OK.
    • In Registry Editor, locate and then click the following registry key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    • Right-click Lsa, point to New, and then click DWORD Value.
    • Type DisableLoopbackCheck, and then press ENTER.
    • Right-click DisableLoopbackCheck, and then click Modify.
    • In the Value data box, type 1, and then click OK.
    • Quit Registry Editor, and then restart your computer

    Check following if the issue happens

    -> Check IIS bindings for this hostname in IIS Manager.

    -> Check AAM Settings For Internal URL & Public url for this hostname.

    -> Verify from IIS if you receive this request in IIS, and then in Sharepoint ULS logs.

    -> Try browsing the site by IP address, see if that works.

    Thursday, January 17, 2013 9:23 AM
  • Hello,

    This is working for one site...

    the second one is giving a new error:

    Same IIS Bindings for both sites.

    AAM Settings look identical.

    Not sure how to do "Verify from IIS if you receive this request in IIS, and then in Sharepoint ULS logs"?

    Any idea?

    Thanks,
    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager




    • Edited by Felyjos Thursday, January 17, 2013 8:02 PM
    Thursday, January 17, 2013 7:42 PM
  • -> From what i understand, out of two site collections under one web application, one is working and on other you get a error.

    -> If that is case, then you don't have check IIS bindings & AAM.

    -> Verify the ULS log for errors.

    Tuesday, January 22, 2013 10:21 AM
  • Hello,

    The IIS Bindings and AAM looks for me the same as in Production!!

    IIS Bindings

    The Binding Information column on the right side is emoty for both sites...

    the redirection to test is done by the HOSTS file on the test server:

    # Copyright (c) 1993-2006 Microsoft Corp.
    #
    # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
    #
    # This file contains the mappings of IP addresses to host names. Each
    # entry should be kept on an individual line. The IP address should
    # be placed in the first column followed by the corresponding host name.
    # The IP address and the host name should be separated by at least one
    # space.
    #
    # Additionally, comments (such as these) may be inserted on individual
    # lines or following the machine name denoted by a '#' symbol.
    #
    # For example:
    #
    #      102.54.94.97     rhino.acme.com          # source server
    #       38.25.63.10     x.acme.com              # x client host

    # localhost name resolution is handled within DNS itself
    #  127.0.0.1      localhost
    #  ::1  localhost

    10.32.136.60 helpdesksp.domain
    10.32.136.60  sop.domain

    Let me know if there is something worng ?

    Thanks,

    DOm


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager



    • Edited by Felyjos Tuesday, January 22, 2013 8:49 PM
    Tuesday, January 22, 2013 8:44 PM

  • System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Tuesday, January 22, 2013 8:45 PM
  • AAM

    Reviewing the log now

    Cannot get ghost document: Features\HelpDeskModules\default.aspx

    Failed to determine the setup path of the list schema for feature {75A0FEA7-70E3-40B1-B395-C06F85D0D158}, list template 7150.

    Possible mismatch between the reported error with code = 0x8107058a and message: "Feature '75a0fea7-70e3-40b1-b395-c06f85d0d158' for list template '7150' is not installed in this farm.  The operation could not be completed." and the returned error with code 0x80070002.

    Failed to determine definition for Feature with ID '367b94a9-4a15-42ba-b4a2-32420363e018'.  Skipping this feature for element querying consideration.

    could it be the reason?

    I tried to filter the log for helpdesk(I found the message above 4 times) or sop (nothing with this filter)

    Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager






    • Edited by Felyjos Wednesday, January 23, 2013 1:45 AM
    Tuesday, January 22, 2013 8:46 PM
  • Hello,

    still looking for cluse?

    Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Friday, January 25, 2013 5:42 PM
  • Hi,

    You are missing to important installations in your new SharePoint environment that exist in the old environment where you moved the databases from.

    Since you are getting an error screen, its not that you are unable to browse the site the issue is there is a problem with the site.

    You are missing the features:

          <WebFeatures>
            <!-- TeamCollab Feature -->
            <Feature ID="00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5" />
            <!-- MobilityRedirect -->
            <Feature ID="F41CC668-37E5-4743-B4A8-74D1DB3FD8A4" />        
            <!-- Knowledge Base Keywords List -->
            <Feature ID="75A0FEA7-12FE-4cad-A1B2-525FA776C07E" />
            <!-- Knowledge Base Knowledge Base List -->
            <Feature ID="75A0FEA7-D31D-491a-9177-F0E461A81E3F" />
            <!-- HelpDesk ExpertsList -->
            <Feature ID="75A0FEA7-E63B-4059-8F5A-CE9CBBADAD2A" />
            <!-- HelpDesk ServiceRequestsList -->
            <Feature ID="75A0FEA7-FE9D-4119-9615-2C2EF22D6FDB" />
            <!-- HelpDesk SupportFaqList -->
            <Feature ID="75A0FEA7-70E3-40b1-B395-C06F85D0D158" />
            <!-- HelpDesk Tasks -->
            <Feature ID="75A0FEA7-3B2A-4838-8A0C-57BA864FEED3" />
            <!-- Help Desk List Instances -->
            <Feature ID="75A0FEA7-97C5-4487-88E4-70FDE8F79B25" />
            <!-- Help Desk Modules -->
            <Feature ID="75A0FEA7-02CB-4f87-BB11-1FFDE748A953" />
            <!-- TSA Image -->
            <Feature ID="75A0FEA7-C54F-46b9-86B1-2E103A8FEDBA" />
            <!-- KB Provisioning Handler -->
            <Feature ID="75A0FEA7-84D9-447d-B9EC-BC49570874DB" />
            <!-- Post Provisioning Event Handler -->
            <Feature ID="75A0FEA7-B0EF-434e-90D6-CE997D970564">

    What this means is that you need to install the FAB40 Help Desk Template and Core

    Reference :

     Also, you have Reporting Services installed in the old environment as can be found by searching for the GUID 367b94a9-4a15-42ba-b4a2-32420363e018 on BING. However, if its not affecting the site you need to use then you may not need to setup RS In SharePoint integrated mode.

    You need to download and install the from the referenced URLs above the HelpDesk template and the Core installation and if these are the onl=y errors you should be good to go.

    Please reply to this post if you hae any additional questions and let us know if you arte successful as well

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders, Business Intelligence in SharePoint 2013.

    • Marked as answer by Felyjos Monday, January 28, 2013 8:45 PM
    Monday, January 28, 2013 12:04 AM
  • Hello,

    This is definetely the issue thanks a lot.

    One Question these wsp templates are they not supposed to be restored from the backup? All Databases have been backed up by TSM and then restored by TSM why do I miss items like this?

    Which database if any is containing these templates?

    Thanks,

    Dom


    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager


    • Edited by Felyjos Monday, January 28, 2013 8:45 PM
    Monday, January 28, 2013 8:44 PM
  • HI,

    They are deployed to the SharePoint root as Features. Whenever, you restore/move/upgrade a Farm all Apps/Solutions/Features need to be installed on the new farm so the references made to them in the ContentDbs can continue to work. The HelpDesk Template is part of the FAB40 that were created for ISVs and VARs to demonstrate what you could do easily with SharePoint. they were never meant to be production ready, their deployment model does not conform to best practices. You have to download and install from the links I provided and you should be good to go.. Reporting Services is usually used from a Centralized location. At some point you will want to resolve this issue as well but I don't think it will be necessary at this time to provide usability to your site. If this were production, you should have iterated through the issues in development prior to going live and I think that's kindof what you are doing now..

    I am glad I could help, have fun with SharePoint it ROCKS!! Please let me know how things go..

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders, Business Intelligence in SharePoint 2013.

    • Marked as answer by Felyjos Tuesday, January 29, 2013 6:36 PM
    Monday, January 28, 2013 10:21 PM