Timeout Issue when Indexing

[Former Member]

Hello all,

I recently installed my TREX instance onto a dedicated server per the documented setup recommendations.

In terms of the setup itself, everything appears to be functioning as it should and all monitors show "green" status across the board (on both the Portal server monitoring tools and the TREX Admin tool).

My problem is that I am unable to successfully initiate an index as I receive the following message in the application log:

"<b>Indexing document failed. Timeout reached (Errorcode 8005)"</b>

If I try to reindex, I get the following message:

"<b>Operation failed timeout while stopping task</b>"

I'm guessing the task it's attempting to stop is the first index request.

Some information regarding the servers and application;

I'm running EP60 SP12; both of these servers are in the same domain, physically located in the same server rack on the same subnet.

Windows 2003 Server is installed on both boxes with no service pack.

Within the Visual Administrator, I've identified the TREX name server with it's IP address, not host name.

I WAS able to successfully setup a TREX before with this EP instance, however it was installed on the same server as the portal itself so I split it up.

Does anyone have an idea what could be causing this problem?

I'm presenting a demo in 2 weeks and would LOVE to have this functionality working by then.

Thanks in advance for your help!

~H

[KarstenH · Accepted solution]

Hi Henry,

at first sight, it sounds like TREX cannot reach the server it is supposed to index. Did you set the TREX user? Can you open a document from the server that you are trying to index from the TREX server?

See also:

Regards, Karsten

[Former Member · Accepted solution]

Hi Karsten,

Thanks for your feedback.

Unfortuntely, this problem continues for me.

I went through the thread you provided and double-checked all my parameters were setup correctly and verified that the TREX instance is communicating w/the Portal instance and yet my Index requests continue to fail.

I notice through the TREX Admin tool that the preprocessing runs successfully and that the que for "To be transmitted" begins to grow..however it doesn't look like anything gets transmitted!

The que for "Transmitting" remains at 0 until the application log fills with the timeout errors.

Hopefully someone has seen this type of scenario before; this is extremely challenging.

~H

[Former Member · Accepted solution]

One more thing to add;

I've let the Index job continue to run since I've posted the last message; strangely enough it looks like documents are getting indexed and yet the Application Log continues to generate errors such as:

<b>Error 6/27/05 4:10:49 PM IndexmanagementService Indexing document failed. Timeout reached (Errorcode 8005)

Error 6/27/05 3:43:33 PM IndexmanagementService Indexing document failed. Communication error. cannot send XML request to http://<TREX_SERVER>:30005/TREXHttpServer/TREXISAPIExt.dll; reason: Connection reset (Errorcode 7262)</b>

When I check the Indexing Monitor I see that 508 documents are indexed, 71 are in process and there was 1 Error.

I have no idea at this point what is happening or whether or not the Indexing is truly successful.

Any feedback would be greatly appreciated.

[Former Member · Accepted solution]

After reviewing my Index closely, it looks as if though the Index is actually running but it appears as if though the timeout period expires before documents go from "In Process" to "Indexed".

Does anyone know where to change the timeout parameter?