Object doenot exist after multiple executions
I have an issue where the object doenot exist error pops up after couple of executions.The object does exist in the name mapping but still the error is popping up it is a recorded script to launch an ...
Forum Discussion
The problem, as the error suggests, is that the process for your application is not found.
While your program may be running, the NameMapping/Alias for that program may not be finding it. This could be the case if the name mapping has a process index that no longer matches the process index in your actually application.
Edit the namemapping parameters for your application and make sure they are set up to find your process.
Also, make sure that you don't have more than one copy of your application running. If more than one copy is running, that may also contribute, again, due to the mismatch in process ID.
While your program may be running, the NameMapping/Alias for that program may not be finding it. This could be the case if the name mapping has a process index that no longer matches the process index in your actually application.
Edit the namemapping parameters for your application and make sure they are set up to find your process.
Also, make sure that you don't have more than one copy of your application running. If more than one copy is running, that may also contribute, again, due to the mismatch in process ID.