Restarting Application Pool on the Web Server: Difference between revisions
(Created page with "If you are a self-hosted agency and users complain that the system is offline, running slowly, or they cannot create new forms, the first step is to restart the IIS application pool on the TraCS web server. On the web server, pull up IIS and location the TraCSWebServices application pool. Stop it and start it again. File:Applicationpool.png If that does not fix it, restart the web server. If that does not fix it, verify you can log into TraCS on the web server...") |
No edit summary |
||
| Line 1: | Line 1: | ||
If you are a self-hosted agency and users complain that the system is offline, running slowly, or they cannot create new forms, | If you are a self-hosted agency and users complain that the system is offline, running slowly, or they cannot create new forms, restarting the IIS application pool on the TraCS web server is the first step to resolve the issue. | ||
On the web server, pull up IIS and | On the web server, pull up IIS and locate the TraCSWebServices application pool. Stop it and start it again. It may take more than one attempt to restart it. | ||
If that does not fix the issue, restart the web server. | |||
If | If restarting the web server does not fix it, verify you can log into TraCS on the web server to see if there is a connection issue to the database. | ||
If | If all else fails, take the TraCS database offline and bring it back online. There are jobs you can run to do this without having to restart the entire SQL service. | ||
Remember, if we do not host you, we do not have access to your servers. We cannot do these steps for you. | |||
[[File:Applicationpool.png]] | |||
Revision as of 10:17, 29 March 2024
If you are a self-hosted agency and users complain that the system is offline, running slowly, or they cannot create new forms, restarting the IIS application pool on the TraCS web server is the first step to resolve the issue.
On the web server, pull up IIS and locate the TraCSWebServices application pool. Stop it and start it again. It may take more than one attempt to restart it.
If that does not fix the issue, restart the web server.
If restarting the web server does not fix it, verify you can log into TraCS on the web server to see if there is a connection issue to the database.
If all else fails, take the TraCS database offline and bring it back online. There are jobs you can run to do this without having to restart the entire SQL service.
Remember, if we do not host you, we do not have access to your servers. We cannot do these steps for you.
