Page 1 of 1

Job does not see the change in Shared container

Posted: Tue Jun 15, 2010 7:43 am
by Hongqing Tang
I have a job that uses the shared container. It passed the compile, then I found an error in the shared container while test run it. So, I fixed the error in the shared container and recompile the job. But when I click "Run", it gives a warning msg says that the shared container was modified before the job was compiled, the changes in the shared container is not included in the job. If I click run anyways, the job keep failing with the old error msg as if the shared container was not fixed. The problem here is that although the shared container is fixed, the job is not taking it during compile. Has anyone seen this problem? How did you resolve it?

Posted: Tue Jun 15, 2010 7:58 am
by ArndW
Normally that message only occurs if, indeed, the job was not recompiled after the shared container was modified and saved. But I am in a project where at present we have 3-4 people working on jobs that all use a common shared container which I am still constantly making changes to; and in the past couple of days some of the users have seen similar problems in that they re-compile their job and get an error message referring to a shared container version that is several hours old, while I recompile my test job and use the newer and correct version of the container. If I close my designer (closing the container isn't sufficient) then they get the newer version on recompile. The "force compile" option makes no difference.
I assume that we have a locking and concurrency issue here at 8.1 but haven't looked into possible causes because we are currently too busy to do so.
Back to your problem - did you change the container in the same designer session? If you close the designer and re-open and then compile the job does the warning go away? Perhaps in your case a force compile might do the trick.

Posted: Tue Jun 15, 2010 9:04 am
by Hongqing Tang
That issue started last week. Today, I went back and tried it again, I am having the same issue.

Posted: Tue Jun 15, 2010 11:07 am
by agpt
Hongqing Tang wrote:That issue started last week. Today, I went back and tried it again, I am having the same issue.
Are you sure you are the only user of this shared container?

Posted: Tue Jun 15, 2010 11:39 am
by Hongqing Tang
Yes, I am sure I am the only user at this time.

Posted: Tue Jun 15, 2010 11:40 am
by agpt
Hongqing Tang wrote:Yes, I am sure I am the only user at this time.
did you try restarting you DS client or your machine?

Posted: Tue Jun 15, 2010 11:48 am
by sureshreddy2009
I have a solution by seeing all above posts
create copy of that job. convert that shared container to stages in the job , compile and run.then its easy to debug once its done.then based on that you can change in job or in shared container . :idea: hope this will helps thanks

Posted: Tue Jun 15, 2010 4:51 pm
by ray.wurlod
When you created the shared container in the job, did you make a copy of the shared container, or did you create a reference to the shared container?

Posted: Tue Jun 15, 2010 10:37 pm
by sureshreddy2009
This topic is marked as resolved..What steps you took for resolving this issue..