EViews.com

Okay, failure is mine. I was logging to a network path instead of a local path, and changing that to a local log file and copying them over to the network share afterwards seems to have resolved the problem.

Same issue, hm. Bleh. I install dozens of programs this way, including a few ISS ones. Never run into this issue. I can reliably reproduce it - a computer that's never had it installed, running with a shell prompt as computer$ (psexec -s -i cmd), simply won't install the software and doesn't generat...

"manually install EViews quite easily with just a few file copies"

good idea for plan B - misread "manual" as "do it sitting at a computer" rather than "manual" as in "don't use the installer" :)

Okay, I'll give it a shot with the newer media, thanks.

The econ department has a license server set up, and when I install the software manually it uses it just fine. Even if I install it manually with the automated installer. The important factor seems to be that I'm logged in with an interactive console of some kind, but I could be wrong about that.

I'm installing in a computer lab with ~200 machines, so doing it manually would not be my preference. Similarly for a logon script, since we don't use roaming profiles and a user cannot count on having the same computer twice. Anyone who uses a startup script to install software is using the SYSTEM ...

Perhaps the eviews installer is boneheadedly requiring some kind of interactive mode?

To summarize, in general, manual installation succeeds as SYSTEM user or admin user, automated installation via startup script fails. It failed a couple times as SYSTEM user, manual install - I've been doing repeated uninstall/reinstall on the test machine and it works consistently. Trying to come u...

Another complaint, probably not critical: It doesn't appear to be possible to replay a completely silent uninstall. It asks the user if they want to uninstall despite using a response file.

minor complaint: Removing the program does not entirely remove %PROGRAMFILES (x86)%\eviews7: C:\Program Files (x86)\EViews7\abank32.dll C:\Program Files (x86)\EViews7\Docs C:\Program Files (x86)\EViews7\EDX_35 C:\Program Files (x86)\EViews7\Docs\EViews 71 Supplement.pdf C:\Program Files (x86)\EViews...

No, that didn't do it, three computers' startup installation failed. It took about 60 seconds to do so, though, so it's doing SOMEthing..

with a bit of experimentation, removing -SMS may have fixed it, sigh. Copypasted from a previous package. In theory it's supposed to tell InstallShield to not spawn the setup as a background process, but maybe it's doing something stupid. I'm going to kick a few computers into maintenance and see if...

I tested it again as the SYSTEM user (this time fully removing my previous attempt) and it failed.

2013-01-30 09:24:58, ERROR : Could not process (install) EViews 7.|Failed checking after installation.

Here is the log file from a failed attempt.

[InstallShield Silent]
Version=v6.00.000

Yep, that's it.

It seems to install correctly when I give myself a SYSTEM account shell and then run the updater routine exactly as it runs during startup.