Hi Vishal,
As Mudasir mentioned, right click the process server, select Monitored jobs and make sure all the jobs are deleted.
For the file events, make sure they point to a different process server.
After all these, if you still have the problem, i would suggest, making a select statement from the table JCS_JOBDEF0 where uniqueid = 359554596 - this would give the job name.
(the number followed by the word "non-visible job" is usually a unique id for the job in that table).
Now you will have an idea which job is causing the problem, and you can examine and remove them.
We have M33.69 version of CPS and i noticed in JCS_JOBDEF0 table that, when i modified a job definition(in redwood) to have a different application, there were two copies of the job definition - one still pointing to the old application and the other to the new application. I was not able to remove the old application because of this dependency. So i had to delete the job definition and then delete the application.
(I'm also assuming the reason for the copies is that the changes were not committed in the backed immediately, someone may clarify this.)
My point being, Sometimes when you modify a job definition it ends up being 2 copies with two different values in the database, but redwood will show you only the latest copy though. In those cases it is better to remove the entire job definition(from redwood) in case and re-create it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.