locked
Central Admin getting an "IE cannot display the webpage" error RRS feed

  • Question

  • About a week ago, I discovered that CA no longer works.    We have a wss farm with 2 WFEs and sql 2k5 backend.   I've reset IIS and i've been googleing like crazy to find a solution.    I found many errors in the event viewer that probably pertain to this issue:

    ******************************

    The start address <sts3://ntteamsitep1:3333/contentdbid={17d9e94d-1989-4502-9d0e-b2480de33e88}> cannot be crawled.

    Context: Application 'Search index file on the search server', Catalog 'Search'

    Details:

    Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read"

    ***************************

    Teamsitep1:3333 is where CA lives.    I had our DBA team verify that the domain username that sp runs under is an owner for the admin content db.     Here is the other one:

    ***************************

    The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

    Context: Application 'Search', Catalog 'index file on the search server Search'

    **********************

    These two errors are repeated thru out the day.   

    here are two more:

    ****************************

    Unknown SQL Exception 10054 occured. Additional error information from SQL Server is included below.

    A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

    *********************

    The Execute method of job definition Microsoft.SharePoint.Administration.SPConfigurationRefreshJobDefinition (ID 0d405d26-0f77-427b-9ac3-bcf0ad1f3084) threw an exception. More information is included below.

    A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

    *************************

    If anyone has any ideas, i'd love to hear them.

    thanks

    Wednesday, July 20, 2011 7:09 PM

Answers

  • Hi ,

     

    This error can be caused by the WSS web front end is unable to communicate with the SQL Server backend .And a solution is mentioned in a similar case listed below.

     

    What is the error message in the log file in located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS .Find the log file on the day the error occur .What is the detailed error information ?

     

    For detailed information about the solution ,please refer to this site:

    SharePoint SQL error:  http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/1bb474b4-87d1-44b9-97c4-d018d9b35b75/

     

    Thanks,


    Entan Ming
    • Marked as answer by Emir Liu Monday, August 8, 2011 3:16 AM
    Monday, August 1, 2011 5:33 AM
    Moderator

All replies

  • Have you tried from the server where CA was installed - and you still can't access the site? Is it added to the browser as trusted site?

    Can you try opening the IIS Manager and go to the CA web site - if you try to browse - does it open?

    From IIS also check the port number - if the port number has changed or not? Does it still show 3333?

    Hope this helps!


    BlueSky2010
    Wednesday, July 20, 2011 7:28 PM
  • Thanks for the reply.     Yes, it's in the trusted sites.    No, it still gets the same message from the server.   No, browsing from the IIS console doesnt work.   Yes, it's on the correct port.

    Fisk

    Monday, July 25, 2011 12:41 PM
  • I'm still getting this in the event viewer all day and all night:

    The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

    Context: Application 'Search', Catalog 'index file on the search server Search'

    And this one:

    The start address <sts3://ntteamsitep1:3333/contentdbid={17d9e94d-1989-4502-9d0e-b2480de33e88}> cannot be crawled.

    Context: Application 'Search index file on the search server', Catalog 'Search'

    Details:

    Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)

     

    Does anyone else have any ideas?   Our DBA has verified that the domain account that SP connects to the DB is listed as owner.

    Tuesday, July 26, 2011 5:47 PM
  • Hi ,

     

    This error can be caused by the WSS web front end is unable to communicate with the SQL Server backend .And a solution is mentioned in a similar case listed below.

     

    What is the error message in the log file in located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS .Find the log file on the day the error occur .What is the detailed error information ?

     

    For detailed information about the solution ,please refer to this site:

    SharePoint SQL error:  http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/1bb474b4-87d1-44b9-97c4-d018d9b35b75/

     

    Thanks,


    Entan Ming
    • Marked as answer by Emir Liu Monday, August 8, 2011 3:16 AM
    Monday, August 1, 2011 5:33 AM
    Moderator