The following items are included in this installation checklist:
Check the following items to make sure required resources are not blocked.
- HTTPS port
The HTTPS port you are going to use for Apex Central is currently not binding to IIS. For example, you are going to use Port 443 for Apex Central HTTPS, then make sure the port 443 is not binding on IIS. If the port is currently binding on a Web Site, manually remove it or use another port to be the Apex Central HTTPS Port.
- Application Pool
There should not be a TMCMApplicationPool in IIS Application Pools. Check the Application Pools in the IIS. If there is a TMCMApplicationPool, manually remote it.
- Folders or Virtual Folders
The website you are going to install Apex Central should not have the following folders or virtual folders:
If there are folders with the same name under the website, remove these folders/virtual folders or create a new website for Apex Central.
- Database Instance
Make sure that the database instance name you are going to use for Apex Central is not existing in your SQL Server. If there is the same name database instance in the SQL Server, Apex Central will installation will fail. You can remove the database instance from SQL Server or assign a new name for Apex Central.
- Windows Authentication
If you are using the Windows Authentication to install Apex Central, make sure that the Windows Account for Database Connection is part of Local Administrators Group. If the account is not a Local Administrator, manually add it into Local Administrators Group.