The online FAQ database contains hundreds of answers to frequently asked questions, articles on using our
web server applications and other related technologies, and resolutions to common problems. If you are seeing
an error message, be sure to try searching on the error message or error number that you are seeing.
|
| |
| |
| |
| |
|
My scheduled tasks do not seem to be executing or do not seem to run at all?
|
|
|
Scheduled tasks are a great way to automate your site. They allow your site to automatically perform some maintenance functions, freeing you from having to monitor or update the site manually. Scheduled tasks run in the background and it might not be immediately obvious if they are running as intended. If you notice that your scheduled tasks do not seem to be performing the activity you expected, the task might not actually be getting run or might be hung for another reason. There are a few key things to check for in order to make sure that your scheduled tasks will run as expected.
The most common trouble encountered when trying to schedule tasks is that the account being used to run the task under does not have adequate permissions to run the application. Make sure that the account has access permissions to any and all of the resources it might need when it runs the task. If you are scheduling tasks using the WSH or scripting files included with the XCENT applications, then double check and make sure that the account has read permissions in the folder with the script files. If you are trying to schedule another type of application or executable, usually you want to make sure that the account has read/write permissions in the folder(s) that the application is installed in, as well at the system defined TEMP folder (usually %SYSTEMROOT%\Temp or C:\TEMP or C:\TMP). One method to help diagnose this problem would be to use a test script to verify that the account can launch the task properly and has write permissions in a folder. Recent versions of the XCENT web server applications may include this in the WSH folder as xcTestScript.vbs. Or, you can download it from the XCENT web site at this link. This script will try to write a timestamp to a log file is the same folder it is located in each time it is run. The name of the log file will be prefixed with the word "test" with the current date. If the log file is not generated when the test script runs, then the permissions fir the account will not allow access to the file or folder.
If the permissions appear correct, then a potential problem could be that the account you are using for your scheduled tasks has never been logged in as a console level user and certain profile information is not completely setup for the account for Internet Explorer. In this case, this can interfere with the way Internet Explorer works under that account. The scripts included with the XCENT web server applications will use Internet Explorer on the machine with the scheduled tasks to communicate with your web site/server. This is true even when the scheduled tasks are the same machine as the web server.
One way to identify this condition is to look at the list of processes running on the machine using Windows Task Manager. First, try running the scheduled task by right clicking it and selecting Run from the menu. Nothing may appear to happen, but this ensures that a task is launched and should be running despite that nothing appears to be happening. To launch Task Manager, click on the Start menu and select the Run option. Type in TASKMGR and click OK. When Task Manager appears, click on the Processes tab and in the list, look for the name ICWCONN1.EXE. If this is running under the name of the account that you have been trying to use for your scheduled tasks, then the process you are trying to run is getting hung when it tries to access Internet Explorer. To correct this problem, logout of the machine that the scheduled tasks are to be run on, and login using the account that you wish to have your scheduled tasks run under. Once logged in, double click on and run Internet Explorer. It should launch the Internet Connection Wizard. You need to run the wizard and configure it appropriately for your machine. Most likely you are just going to be telling it to use your LAN connection. This is what you would use for any machines with a dedicated permanent internet connection, like your web server would have. Once that is finished, make sure Internet Explorer will run normally when you launch it.
Now using that same login, try manually running the script or application you are trying to schedule. If it runs now, it should begin functioning with the scheduled tasks on the next scheduled event. You should now be able to logout and try launching your task again manually to verify it runs and does not hang.
|
|
|
|
| |
