-17500 ERROR_DESCR_NOCLIENTFILE

[mrbean]

There is an expression in the sequential model Test UUTs Entry point (in the Setup) - f(x) Check For Client File

Here is the expression details.

Step

.Result.Error.Msg = SearchAndReplace(ResStr("MODEL","ERROR_DESCR_NOCLIENTFILE"),"%1", NameOf(RunState.Sequence)),

Step

.Result.Error.Occurred =true,

Step

.Result.Error.Code =-17500

Here is my problem.  We created a Norton Ghost image of one of our test racks, and we want to restore that image onto another test rack to ensure they are identical.  I thought we might have a problem with TestStand, as it's tied to the hardware.  On the new target, after restoring the image, I ran our sequence file (using the TS User Interface), and saw the error above.  I then (tried to) open the sequence file using the sequence editor, and saw that TS was requiring me to activate the license.  As these targets are not connected to a network, I used the s/n of the new target, and phoned into NI to get an activation Code.  That all worked fine, and I rebooted the machine.  However, when I brought up the sequence file, I once again got the above error.  The comment above the expression in question says "In case someone accidently tries to execute this sequence directly, give them a error message".

Any thoughts?

[snowpunter]

You're either trying to run a sequence file with no process model or a process model with no sequence file (client file.)

[mrbean]

I'm not sure how that's possible.  I load the sequence file I created (and have run 600 times (but on a different target)), and just click 'Run Test UUTs' as always.

[mrbean]

Problem solved.  The symptoms were a little weird, but the problem turned out to be that the D-drive of the target was not formatted, and at the step in question, it was trying to do some on-the-fly reporting, and we were telling it to store the report file on the d-drive.  I didn't really  provide enough information in my initial post.  Thanks anyway.

[vishalvy]

What is exact solution to this error? Because I am also getting the same error.