TestStand searching for LVCoreAcc.msi

[Underflow]

Good morning all,

I have a computer that had TestStand (3.1) and LabVIEW(7.1) installed from the network.  The computer's been removed from the network, and on startup, TestStand is looking at the network location of LabVIEW for a component called "LVCoreAcc.msi".

Does anyone know what is causing this to occur?  If it's relevant, the system is using a debug deployment license.

Thanks,

Joe Z.

[Patrick_P.]

Hey Joe,

Just to ask a few more questions, I assume this problem didn't appear until you disconnected it from the network.  If you reconnect it to the network does it still give the same error?  Also does this error appear if you just try and open LabVIEW by itself or does it only appear when you open TestStand?  The first thing I would recommend to do is try doing a repair install of both TestStand and LabVIEW.  Let us know if this doesn't solve the problem.

Thanks,

[Underflow]

Hey Pat, thanks for the answer.

Unfortunately, the computer and the network cable are now several (cough...thousand) miles distant from each other, so reconnecting won't work (without a REALLY good extension cable).

I did find out that the original installer's user account on the machine was deleted (by directly deleting their user folders), and the problem appeared after that.

Further detail: if the error is cancelled out of (apparently a few times), the system does run fine.  The error reoccurs every time TestStand is restarted.

It almost sounds like TestStand trying to track down some missing configuration information, not finding it in the (now deleted) original installer's personal folders, and returning to the default installation source for it, not finding that, and ending up with some defaults.  (Unfounded speculation is fun!)

Unfortunately, the install disks are not at the computer site, so a repair install will be difficult.  I will attempt to find out about starting up LabVIEW directly.

Joe Z.

Edit: Speeling

Message Edited by Underflow on 06-14-2006 02:23 PM

Message Edited by Underflow on 06-14-2006 02:25 PM

[Underflow]

Apparently, the error also occurs when LabVIEW is started by itself... off to the LabVIEW forum?

Joe Z.

[Underflow]

Update: it looks like a re-install of the LabVIEW runtime engine has cured the error problem.  LV still starts slowly (1+ minutes on a 3GHz machine), but it's a start.