Gravatar for erkan.yildiz@avanade.com

Question by erkany, Jan 5, 2015 2:09 PM

CES install time out

I uninstalled CES and Search API. Deleted c:\ces7 , c:\program files\coveo folders. Now when I install back and go to the fist page where I click on "Create Index" the page times out with below error:

Server Error in '/' Application.

Request timed out.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.Web.HttpException: Request timed out.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 


[HttpException (0x80004005): Request timed out.]

Version Information: Microsoft .NET Framework Version:2.0.50727.8009; ASP.NET Version:2.0.50727.8010
Gravatar for erkan.yildiz@avanade.com

Comment by erkany, Jan 5, 2015 2:09 PM

this is the url: http://localhost:8081/Configuration/InitialSetup/InitialSetup.aspx

Gravatar for slangevin@coveo.com

Comment by Simon, Jan 6, 2015 1:07 PM

This is very strange indeed. Do you see anything more in the Windows Event viewer logs (Application)?

Gravatar for jhollinger@andculture.com

Comment by andculture, Apr 6, 2016 2:13 PM

I am having this same issue with a fresh vanilla install of CES 7.0.8255.2 and the .NET Front-End 12.0.1459.

I tried twice to do the front end initial setup and both resulted in a timeout. Here are the errors from the log FrontEndSetupErrors_16-04-06.log:

4/6/2016 1:23:09 PM      Thread was being aborted.
  Exception:
    Source: mscorlib
    Stacktrace:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
   at Coveo.CES.Web.Search.Providers.Cmf.CmfConnectionFactory..ctor(String p_Server, Int32 p_Port, String p_ConnectionMode, Boolean p_AllowAnonymousUsers, String p_SslCertificatePath, Boolean p_SslIgnoreCrl, String p_ServerId)
   at Coveo.CES.Web.Search.Providers.Cmf.CmfConnectionFactory.GetFactory(String p_Server, Int32 p_Port, String p_ConnectionMode, Boolean p_AllowAnonymousUsers, String p_SslCertificatePath, Boolean p_SslIgnoreCrl, String p_ServerId)
   at Coveo.CES.Web.Search.Providers.Cmf.CmfSearchProvider..ctor(String p_QueryingUser, IList`1 p_AdditionalIdentities, IList`1 p_IdentitiesForDocumentsRatings, String p_SuperUserToken, List`1 p_RemoteIndexes, Boolean p_MergeSuperUserTokenForTagging, IUserIdentity p_NonAdQueryingUser, IQueryProcessor p_QueryProcessor)
   at Coveo.CES.Web.Search.Providers.SearchProviderFactory.CreateDefaultSearchProvider(String p_QueryingUser, IList`1 p_AdditionalIdentities, IList`1 p_IdentitiesForDocumentsRatings, IUserIdentity p_NonAdQueryingUser, IQueryProcessor p_QueryProcessor)
   at Coveo.CES.Web.Search.Providers.SearchProviderFactory.CreateDefaultSearchProvider()
   at Coveo.CES.Web.Search.Controls.FirstTimeSetup.ApplySettings(Boolean p_ShowErrors, Boolean p_NoRedirect)
4/6/2016 1:43:41 PM      Thread was being aborted.
  Exception:
    Source: mscorlib
    Stacktrace:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
   at Coveo.CES.Web.Search.Providers.Cmf.CmfConnectionFactory..ctor(String p_Server, Int32 p_Port, String p_ConnectionMode, Boolean p_AllowAnonymousUsers, String p_SslCertificatePath, Boolean p_SslIgnoreCrl, String p_ServerId)
   at Coveo.CES.Web.Search.Providers.Cmf.CmfConnectionFactory.GetFactory(String p_Server, Int32 p_Port, String p_ConnectionMode, Boolean p_AllowAnonymousUsers, String p_SslCertificatePath, Boolean p_SslIgnoreCrl, String p_ServerId)
   at Coveo.CES.Web.Search.Providers.Cmf.CmfSearchProvider..ctor(String p_QueryingUser, IList`1 p_AdditionalIdentities, IList`1 p_IdentitiesForDocumentsRatings, String p_SuperUserToken, List`1 p_RemoteIndexes, Boolean p_MergeSuperUserTokenForTagging, IUserIdentity p_NonAdQueryingUser, IQueryProcessor p_QueryProcessor)
   at Coveo.CES.Web.Search.Providers.SearchProviderFactory.CreateDefaultSearchProvider(String p_QueryingUser, IList`1 p_AdditionalIdentities, IList`1 p_IdentitiesForDocumentsRatings, IUserIdentity p_NonAdQueryingUser, IQueryProcessor p_QueryProcessor)
   at Coveo.CES.Web.Search.Providers.SearchProviderFactory.CreateDefaultSearchProvider()
   at Coveo.CES.Web.Search.Controls.FirstTimeSetup.ApplySettings(Boolean p_ShowErrors, Boolean p_NoRedirect)
Gravatar for jhollinger@andculture.com

Comment by andculture, Apr 6, 2016 2:15 PM

Here is the info from the Windows Event Viewer log:

Event code: 3001 
Event message: The request has been aborted. 
Event time: 4/6/2016 1:23:09 PM 
Event time (UTC): 4/6/2016 5:23:09 PM 
Event ID: 62aa1beb97bd48a084c7b735e0e65f14 
Event sequence: 35 
Event occurrence: 1 
Event detail code: 0 

Application information: 
    Application domain: /LM/W3SVC/30/ROOT-1-131044367763547345 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\Program Files\Coveo .NET Front-End 12\Web\ 
    Machine name: W520 

Process information: 
    Process ID: 13256 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\NETWORK SERVICE 

Exception information: 
    Exception type: HttpException 
    Exception message: Request timed out. 

Request information: 
    Request URL: http://localhost:2000/Coveo/FirstTimeSetup/default.aspx?lcid=1033&ref=The request has been aborted.fdefault.aspx 
    Request path: /Coveo/FirstTimeSetup/default.aspx 
    User host address: ::1 
    User: CLTR\jhollinger 
    Is authenticated: True 
    Authentication Type: Negotiate 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 

Thread information: 
    Thread ID: 10 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
    Is impersonating: False 
    Stack trace: 


Custom event details:
Gravatar for jhollinger@andculture.com

Comment by andculture, Apr 6, 2016 2:19 PM

I setup Coveo under the windows AD user CLTR\Administrator, but I am noticing in the Event Viewer it says User: CLTR\jhollinger (which is my actual account on this machine). Not sure if that could be an issue or not…

Basically this method is running long until the point where IIS times out: Coveo.CES.Web.Search.Providers.Cmf.CmfConnectionFactory.GetFactory()

Gravatar for jhollinger@andculture.com

Comment by andculture, Apr 6, 2016 2:21 PM

Also even if I just try to go directly to the page root (which in my case is localhost:2000) it also time out.

Here is the Windows Event Viewer log for that:

Event code: 3001 
Event message: The request has been aborted. 
Event time: 4/6/2016 1:40:54 PM 
Event time (UTC): 4/6/2016 5:40:54 PM 
Event ID: 6273bb63175144bfbc2b3ce31a7badc1 
Event sequence: 12 
Event occurrence: 3 
Event detail code: 0 

Application information: 
    Application domain: /LM/W3SVC/30/ROOT-2-131044370335357886 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\Program Files\Coveo .NET Front-End 12\Web\ 
    Machine name: W520 

Process information: 
    Process ID: 13256 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\NETWORK SERVICE 

Exception information: 
    Exception type: HttpException 
    Exception message: Request timed out. 

Request information: 
    Request URL: http://localhost:2000/default.aspx 
    Request path: /default.aspx 
    User host address: ::1 
    User: CLTR\jhollinger 
    Is authenticated: True 
    Authentication Type: Negotiate 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 

Thread information: 
    Thread ID: 8 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
    Is impersonating: False 
    Stack trace: 


Custom event details:
Gravatar for rquirion@coveo.com

Comment by ronald, Apr 6, 2016 3:33 PM

Andculture,

I have the impression that the connection attempts from the front-end to the CES index are hanging for some reason, and ASP.NET ends up killing the thread probably when the HTTP request timeout is finally reached. If the connection parameters that you entered in the first-time setup page are correct, you have to find out why the connection to the index are hanging that way. I may be wrong, but I suspect a firewall issue.

0 Reply
Ask a question