cannot login to sequence editor

[Ron_in_SD]

Hi,

I seem to have broken something in my version of TestStand 4.2. When I launch sequence editor it starts in the logged off state.  When I click Login... nothing happens.

I think this may have something to do with the Process Models - I had installed a modified SequenceModel.seq that was modified by a co-developer and had re-installed the original back over it because the modified process model wanted to access components I did not have on my computer (i.e. a sql database).  Anyway, since I did this, I cannot get the logon dialog to display.

TIA

Ron

[lvrat]

Did the modified process model "SequenceModel.seq" used LabWindows adapter? If so was the sequence file saved with CVI adapter configuration as "Execute step in external instance of CVI". Although there seems to be no link b/w login window and adapter configuration....I had the similar problem and remember changing the CVI adapter setting from external to in-process and it worked. Just as an FYI...not sure if it will solve the issue but does not hurt to try. Of course the model will need to be opened on a computer where TS is logging in correctly.

Another thing to check is that the correct model is placed under the shared document folder (if the customized model was moved to that location)...likely the path should be:

....\Documents and Settings\<user>\shared Documents\National Instruments\TestStand 4.2.1\Components\Models.

[dug9000 · Accepted solution]

It's the frontend callback, not the process model, that is responsible for implementing the login/logout process.

There should be two versions of the FrontEndCallbacks.seq file on your machine as follows:

1) in <Program Files>\TestStand 2010\Components\Callbacks\FrontEnd, this version in here should have a sequence called LoginLogout

2) in <TestStandPublic>\Components\Callbacks\FrontEnd, this version should be an empty sequence file.

Also, make sure you don't have the station option set to automatically login the Windows system user.

Hope this helps,

-Doug

[Ron_in_SD]

---

@dug9000 wrote:

It's the frontend callback, not the process model, that is responsible for implementing the login/logout process.

There should be two versions of the FrontEndCallbacks.seq file on your machine as follows:

1) in <Program Files>\TestStand 2010\Components\Callbacks\FrontEnd, this version in here should have a sequence called LoginLogout

2) in <TestStandPublic>\Components\Callbacks\FrontEnd, this version should be an empty sequence file.

Also, make sure you don't have the station option set to automatically login the Windows system user.

Hope this helps,

-Doug

---

Thanks!  I copied the FrontEndCallbacks.seq from the <Program Files> Path (which was unmodified from the install) to the <TestStandPublic> path and my logon dialog is back.

Thanks - back to work for me.

[dug9000]

It's best to delete the loginlogout callback sequence from the version in your teststandpublic directory. That way if you install an update of teststand in the future that updates the version in the programfiles directory you will use the new version rather than the version in your teststandpublic directory which might then be out of date. Basically, if the version in your public directory has the sequence then that one takes priority over the version in the programfiles directory.

Hope this helps,

-Doug