Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unknown error: Process Error 1

Status
Not open for further replies.

madhuusa

IS-IT--Management
Oct 5, 2006
93
US
Gurus, AppNair,
We installed admin server in our production environment. We have clustered environment with 2 front end's and admin server seperate.

The admin process namely search engine and index engine process does not start but gives Unknown error: Process Error 1.

There is no log information as the 2 process does not start itself. We suspected the contigous memory issue and put a microsoft patch for that but that also did not resolve. We installed a brand new installation in the same machine and that also gave the same error.

Any idea why this is happening. This error as per support means that search process is getting an error from o/s that it is not able to decipher. Unless we can come with some ideas as to why this is happening, debugging this can be really difficult.

Any help is appreciated.
 
Here is the error as displayed in the index engine:

The Process has returned: Process Error 1: Unknown Index Engine Error

Same error comes in search engine except that it says Search Engine Error.
 
the first things to check is to go on the admin servers properties page and check if RMI is communicating.If you are sure that is working allright now the individual parts could be checked.Are you sure your partition is not full nearing full,anybody running anti virus on the data flow and index directories.Mostly search problems are realted to windows file locking and av problems

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
 
how about the notorious hyper threading ?

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
 
Greg, The link helped.

It looks softee had blocked continuous memory access to prevent hacking. And then based on complaints from vendors like textie, they put a hotfix.

We had installed both, but it seems there were several other patches also that has come in last 1 or 2 months and all of that is in our server. There is an outside chance that some of those security patches is blocking the hotfix.

I guess several more clients might be facing this issue once they are coming to speed to patches by softee.

When we reduce the memory access size to 512M instead of 1230M in otadmin.cfg, the processes start.. But given the huge efs we have, this is short term fix.

Also suddenly we are getting Process Error 107 in document conversion process. Any ideas on this? This is not related to reduced memory and support suspects scan on index or efs directory. We are looking into it but scans seems not to be the reason. Any ideas?
 
Friends, a quick closure on this.

We are running our index and search engine with 1024MB and help and admin help with 50MB.

This has helped solve the issues. Although 1230MB is a good memory space for the search process to run, we are just short of it.

It looks like any one of the several past 6 months patches given by softee might have caused this issue. We are in process of rolling back the patches and introducing them one by one to see which one might have caused this.

Till that time, amen, peace, shanthi...
 
the following links cover this issue which was around a while ago which seems to be the same issue you are experiencing :


Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top