The information in this article applies to product: e-Work 6.x
Question
- What are some things to consider if the e-Work engine becomes non-responsive (hangs)?
Response
- Is this actually an engine issue? Maybe it's web-related instead? Try restarting just the web server.
- Using Windows Task Manager, monitor the server for CPU and Memory consumption at the time of the hang.
- Test connectivity with the Outlook/Notify client as these bypass the e-Work web extensions and IIS when connecting to the engine.
- Is the engine still running?
a. There should be two processes visible in the Task Manager:
eEngine.exe
dllhost.exe - the process id should match that reported in the 'e-Work engine started' information entry in the Windows application event log.
b. There should be an entry in the eActiveEngine table for each engine running. Furthermore, its eAliveAsOf entry should be reasonably up-to-date - by default no more than 2 minutes out-of-date. The frequency of this update is defined in eServer.eKeepAliveInterval.
- Are there multiple engines in the production environment? Is this a problem with all of the engines? Does it occur on the development/QA system? If not, what's the difference between the 2 environments?
- Are there any messages in the Windows event log and/or designer log? If possible, increase the system audit levels to get the system to be more verbose. Go to Start --> Settings --> Administrative Tools --> Local Security Settings --> Local Policies --> Audit policy.
- Is there other evidence of e-Work system activity, such as folder locks being applied recently (check eFolder.eActionTime)? Or new folders being created (check eFolder.eCreationTime).
- Try raising a dummy flag with the command-line utility:
eRaiseFlag.exe /flagname:DummyFlag
Does eRaiseFlag.exe return? If so, does it report an error? Is there a corresponding entry in the eRaisedFlag table? If so, it may indicate a problem or just that the engine's event manager is busy processing other data.
Try creating a dummy request for the Transaction Protocol (TP) interface. Use the following JScript to create a .js file:
var ET = new ActiveXObject("e-work.EworkTransaction.3");
// Do something, pass in invalid folder id and session id, cite a non-existent action
var request = "";
var response = ET.eworktransaction( request );
WScript.echo( response );
ET = null;
Run the file from the Engine server. What response do you get?
- If SQL Server is used, examine locks on the database. Using the Enterprise Manager, expand the SQL Server hosting the e-Work database then drill down to Management --> Current Activity --> Locks / Process Id. Check for long-held locks or blocking? If so, what resources are being held?
- Has anything changed in the environment - new procedure published, heavy usage, other applications accessing e-Work database, security patch installed, etc.?
