I've been trying to help my father install and evaluate MS13 EOD (he and I both use MS 11, but I'm 1,000 miles away so use remote-access software to get to his system).

So far, he's been utterly unable to get it even running after installation, even after spending over an hour with MS tech support - it appears something is blocking access to the license servers. We've checked/disabled firewalls, antivirus and Windows Security features with no success (this is Win7 Pro64, by the way).

In addition to this failure to run, I also discovered that the program insists on installing to a folder buried deep underneath the C:\Users\username\...... folder structure - about 5 or 6 levels down!

I did an uninstall and reinstalled from his downloaded EXE file, thinking Dad missed an option to customize installation - there is none. MS13 insists on installing everything (program, data, everything) in this obscure, buried folder tree.

This is something rarely seen; there's not even a user option to install to standard Program Files or Program Files(x86) folders.

So, MS13 wants to install to a very nonstandard location, offers no choice to do otherwise, and then refuses to run at all.

We'll contact tech support again next week, but so far we're not impressed. Personally, I think I'll skip it and stick with MS11 just from hearing that the "Edit Data" option for local data is no longer available to fix data errors. Feh.

Hi,

FWIW, it's possible to load MSPro V12 into other locations by changing the install location prior to letting the executable run. I suspect that there hasn't been any change in this procedure for V13, Pro or EOD. Download, but do not run the installation program that starts the process. To make the next step easier, copy and paste that program, most likely "TRD8_WebStart.exe" into a location that will be easy to navigate to with a command prompt, something like C: emp. Then start a Command Prompt as an Administrator. Navigate to that location. Then type in the following command:

trd8_webstart.exe /command=_sso=0_useUpdateProxy="http://tr-update-proxy"

If you don't want to navigate to the folder that the executable is stored in, type the command with the proper path, such as:

C: emp rd8_webstart.exe /command=_sso=0_useUpdateProxy="http://tr-update-proxy"


That will bring up the Deployment Manager. When that is up, you can select "Customized install" if I remember this correctly, which will allow you to select the folder of choice for installation of both Eikon and Metastock programs and a secondary folder where the unpacked install files will be located. There is only one install location selection, so, both Eikon and Metastock will load into the one location. Even with the program installed to a non-standard location, you will still end up with user files for both programs buried within the User Directory.

The documents you are looking for that describe the command switches are as follows:

Thomson Reuters Eikon_DirectInstall_v1.3.pdf

Thomson Reuters Eikon Technical Migration Guidev30 External.pdf

Note that the Migration Guide might be at a higher version by now.

These are available from Thomson Reuters. MS support does not have these and from my discussions with them months ago, they appear have no knowledge of them or how to install to non-standard locations.

If you start the install executable with the following command: trd8_webstart /help you will see some of the command switches that are available. But, there is very little explanation on the popup window that follows.

I have MSPro V12 loaded on a ram drive, as well as Eikon (unfortunately). Its too bad that there isn't separate selections for both programs. The actual executable that loads EOD V13 might have a different title, but I suspect that the same process should work.

Hope this helps.

Thanks for that info about Run As Admin - we'll give it a try.

Is there a solid reason why, by default, you don't install MS13 into the standard Program Files folder tree? Why do you bury it in the Users tree, which is normally used only for user-specific settings and data?

I found it incredible that so much is being installed there, and buried so deeply.

Thanks for the quick answer, John.

We have occasionally seen where not having Microsoft .NET Framework 4 installed can cause this issue. They may not have seen this particular variation as most of the time MetaStock will crash with a fairly specific error. Please try downloading and installing Microsoft .NET Framework 4 to see if this helps: