If a WAS-hosted region does not start and "cannot contact" messages or thread abort messages appear, a good first step is
to ensure that the WAS infrastructure is set up correctly.
As part of the initial setup,
wassetup should be run. If it was not, then run it now.
If IIS or WAS is behaving inconsistently, the first thing to do is to use the
wasreset command to reset the environment. The command kills all
Enterprise Server for .NET processes and re-cycles IIS and WAS.
wasreset with the /full option removes all active w3wp processes and terminates any active transactions.
Other steps to take include the following:
- Check that the pool definitions in the IIS console are correct.
- Check that the port sharing service is running.
- Check that
seemonitor service can be started in the services console.
- Ping the local machines host name to check for DNS or network issues.
- Ping the database host machine, if the database is not local, to check DNS or network issues.
- Open a browser and check that navigation to http://localhost/MicroFocus/SEE/SEP.svc sends back the "metadata publishing is
The following steps could be used with
- See if anything relevant appears in the event logs.
- Activate and use the Micro Focus common tracing facility.