I have a new twist to this error message. In our production environment, our scheduled jobs have successfully run for several months up until September 10th. There have been no changes to our configuration but on that day I went into the TAC to manually run a job. When it failed, I tried to regenerate it which gave me the error. The other jobs in the scheduler continued to execute until I tried to regenerate them. This caused the generator error for each job. I am still able to run the jobs from the Studio. I've pasted the TAC administrator log for that period below.
I have tried to delete the commandline workspace and restart the service. The configuration in the TAC shows invalid connection to the commandline and I'm unable to connect to it with Telnet. Again..there were no config changes to the environment during this period. Can someone tell me how to get the commandline working again? Can (or should) I uninstall/reinstall it?
Thanks
Tim
~~~~~~
There must be a problem in your network, as you said, you are not able to telnet or ping to the machine where commandline is installed, and it displays invalid status in TAC configuration page.
I don't think it's network related. I can not telnet or use localhost from the same server where the command line is installed. Also, all other services are reachable over the network.
