Skip to main content
SharePoint

Return to Question

added 128 characters in body
Source Link
Ola
Ola
  • 4.4k
  • 27
  • 129
  • 232

I am using SharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It is stuck after found 137 items successfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

UPDATE

I have uncheck the IE option "Automatically detect Settings" on the 2 fast servers. I started a full crawl for 1 site collection and it is stil running. See here some printscreens of the warnings, errors and successes. It looks like it is very slow. I dont now what the search is doing now!!

Warnings enter image description here

Errors enter image description here

Successes enter image description here

I am using SharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It is stuck after found 137 items successfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

UPDATE

I have uncheck the IE option "Automatically detect Settings"

Warnings enter image description here

Errors enter image description here

I am using SharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It is stuck after found 137 items successfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

UPDATE

I have uncheck the IE option "Automatically detect Settings" on the 2 fast servers. I started a full crawl for 1 site collection and it is stil running. See here some printscreens of the warnings, errors and successes. It looks like it is very slow. I dont now what the search is doing now!!

Warnings enter image description here

Errors enter image description here

Successes enter image description here

added 128 characters in body
Source Link
Ola
Ola
  • 4.4k
  • 27
  • 129
  • 232

I am using SharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It is stuck after found 137 items successfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

UPDATE

I have uncheck the IE option "Automatically detect Settings"

Warnings enter image description here

Errors enter image description here

I am using SharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It is stuck after found 137 items successfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

I am using SharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It is stuck after found 137 items successfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

UPDATE

I have uncheck the IE option "Automatically detect Settings"

Warnings enter image description here

Errors enter image description here

edited
Source Link
Amal Hashim
Amal Hashim
  • 28.4k
  • 5
  • 32
  • 61

I am using spSharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It stucksis stuck after found 137 items succesfullysuccessfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

I am using sp 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It stucks after found 137 items succesfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

I am using SharePoint 2010 and FAST search. I have created a new content source with 1 site collection. This site collection is new and I created only 2 items inside a list. I started a full crawl for this new content source. It is stuck after found 137 items successfully and 2 errors. The latest crawled items were the 2 errors. This is the error:

This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

How can I fix this issue?

This is the acceptance environment.

Source Link
Ola
Ola
  • 4.4k
  • 27
  • 129
  • 232