failure to install as startup script

[EViews Steve]

By "manual" I meant not using our installer -- you could write a batch file to perform the work of installation.

Otherwise, I'm not sure how I can help you figure out your problem on your network.

Steve

[EViews Steve]

By the way, if you're using a license server that has a concurrent license (not a LAB license), then you don't even need to install anything on the user's machine. They can all run EViews from a common network file share directly. They would just need a shortcut.

[rbos]

"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"

[rbos]

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 generate any log file information.

Interesting.. if I copy/paste the install command and run it directly instead of from the script, setting up variables beforehand, it installs. Maybe WPKG is screwing something up.

I may be able to figure this out.

[rbos]

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.

[EViews Steve]

Great. Glad to hear you resolved it.

[sampei]

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.

This thread is a life saver!
I made exactly the same stupid mistake today doh.
Thanks for sharing.


________________
EViews is the easiest-to-use tool for analysis & forecasting I have ever come across, I use it even on one of my websites > Free hosting