Warning : Unable to find SoftwareResourceLocator start point

priyadarshikunal · Post by **priyadarshikunal** » Mon Apr 21, 2008 6:22 am

Hi all,

I am getting a warning message while running the sequences.

the warning text is "Unable to find SoftwareResourceLocator start point"
and this warning comes continuously unless I cleanup the resources

i am unable to stop the sequence too. it doesn't aborts/stops through the abort button. for that i have to logout the processes through cleanup resources option.

can anyone tell me how to resolve this?

Regards,

kumar_s · Post by **kumar_s** » Mon Apr 21, 2008 1:54 pm

Once you clear all the locks and logout the available ports, do you get these error again when you run it?
Does it calls the underlying jobs?
What is the design of the JobSequnce?

ray.wurlod · Post by **ray.wurlod** » Mon Apr 21, 2008 5:07 pm

You may need to recompile the job sequence.

You may further need to check that the logic of the job sequence is intact, for example that every path through the job sequence can enter an activity and leave that activity.

priyadarshikunal · Post by **priyadarshikunal** » Tue Apr 22, 2008 10:34 am

ray.wurlod wrote:You may need to recompile the job sequence.

You may further need to check that the logic of the job sequence is intact, for example that every path through the job sequence can enter an activity and leave that activity.

Hi Ray,

This job was running fine previously but now i am getting this problem.

The sequence runs fine when all the jobs finishes successfully.
but when any of them fails we are getting this warning.

Regards,

ray.wurlod · Post by **ray.wurlod** » Tue Apr 22, 2008 4:06 pm

It's the restart logic code. That's why I suggested recompiling.

priyadarshikunal · Post by **priyadarshikunal** » Wed May 07, 2008 10:09 am

ray.wurlod wrote:It's the restart logic code. That's why I suggested recompiling.

Hi Ray,

I recompiled that sequence and ran again it worked fine.
but I am getting this warning in 90% of the time when any job aborts.

Is there any work around that can restrict these warning and abort the job normally.

Regards,

ray.wurlod · Post by **ray.wurlod** » Wed May 07, 2008 3:49 pm

Preventing the jobs from aborting would be favourite.

What compilation options have you set in your job sequence? Are you using explicit Failure triggers on the Job activities? Is there an Exception Handler in your job sequence?

priyadarshikunal · Post by **priyadarshikunal** » Tue May 13, 2008 10:56 am

ray.wurlod wrote:Preventing the jobs from aborting would be favourite.

What compilation options have you set in your job sequence? Are you using explicit Failure triggers on the Job activities? Is there an Exception Handler in your job sequence?

Yes, thats what i prefer too.

yes we have exception handler in the sequence to abort the sequence (using terminator)after mailing activity.

There are few conditional triggers to to abort the sequence in case of warnings.

and i use the simplest compile option that is on the tool bar of datastage designer (i think i am mis-interpreting this one, correct me if it is so)

Regards,

kumar_s · Post by **kumar_s** » Thu May 15, 2008 3:09 pm

So it wont appear for 10% of time even the jobs get abborts?