Bob try uninstalling TLT first, then unblocking the Setup program before you run it.

@ norman - I LOVE YOU!

Thanks and glad to help in some way.
Really this is more of an WE than a ME thing. I just contributed.

WE cannot fix bugs.
WE cannot add features.
WE can find ways to work around install quirkiness.
WE can hopefully find ways to work around application bugs.

@Gary,
I uninstalled TLT through the Add/Remove applet. Rebooted the computer, unblocked the setup program for version 1057, installed, launched VegasPro 13 and sorry to say I got the same error message.
Bob

BobMoyer, specifically because Timeline Tools might have an additional issue with setup exectuable in VegasPro13 because of changes that have been recently made. This remains to be tested.

We seem to have verification from at least one person that
TLT version 1049 will install correctly (Reply by: rmack350 Date: 4/21/2014 9:49:42 AM --Noted 1a) Timeline Tools 1.0.49 starts successfully and appears to function and 1b) Vegasaur 1.9.4 starts successfully and appears to function - rmack350 has since installed 1056 and it is running)- may be a few later versions - untested yet not 1053 ?, 1056? or 1057 as of this date.

rmack350 and I both have .56 working in Vegas 13.

I just tried the demo V13 on my laptop with Win 7 64-bit, one hard-drive, user account, etc., and TT version 1.0.41 seems to work fine.

Previously I had tried it on my desktop which uses an SSD 120 HD as the boot "C" drive. I think I installed the V13 demo to my "D" drive as I try to keep my "C" drive from filling up. Maybe that's why it didn't work for me on the desktop. I recall I may have installed V11 on the "C" because that's the main program I use on that computer. I'll try uninstalling V13 from the "D" and re- installing on the "C" and see if that works.

OK - I re-installed V13 on the desktop's "C" drive and it still won't open. FYI - this is a Windows 8.1 machine. It works on my older Win7 laptop but not on my newer Win8.1 desktop. Why??

1.0.56 and 1.0.57 both installed and ran without incident for me.

Rob

EDIT: I see the problem was solved in prior posts in this thread. Let us never speak of this again (except to spread good advice).

Ok Bob. The next step is to look at the TimelineTools.dll.

1. Navigate to C:\Users\your_name\Documents\Vegas Application Extensions.
2. Find TimelineTools.dll.
3. Right click on the dll and select Properties at the bottom of the popup menu.
4. From the Properties form, see if the Unblock button is displayed as shown in the following image from the web site I linked to earlier. If so push it.

Gary? The screengrab is pointing at a file on your Desktop. Where is this UNBLOCK on the DLL for TLT?



Cheers

Grazie

TLT 1057 not appearing in VP13.

New attempt/process

1/- Uninstalled TLT 1057

2/- Did a NEW download - now TLT 1056 (yes?)

3/- While IN Download folder I did the UNBLOCK

4/- Installed TLT 1056

5/- Same Error messages as Bob and no-show for TLT 1056.

Working fine in VP12.

Cheers

Grazie

Grazie, the screen grab was from the web site I linked to, that talked about the Unblock Button. It wasn't from my PC. I simply used this as an example.

What are your current UAC settings? Bring up Control Panel, and switch to the Icon view. Click on User Accounts, and then click on Change User Account Control settings.

What level is the slider currently set to? Just for this test, if it's not all the way down to Never notify, set it there, and close the form. You may have to reboot your PC.

With UAC disabled, try running SVP-13 again, and see if you still get the error.

Gary, on the case. Just rendering out a short project then I'm at it!

g

No good in VP13. UAC set to zero. I even uninstalled and reinstalled TLT again just to be sure.

g

Ok, I've got one more thing to try. But first I need you to go to the Vegas 13 installation folder; probably something like:

C:\Program Files\Sony\Vegas Pro 13.0

and find a file named vegas130.exe.config. If you can email this to me, I'll take a look at the policy settings in the file. Send it to nfatoys@hotmail.com. There are a couple policy settings that can be added to the existing settings that tell Windows to use old .Net v2 style security. I'll make the changes and post the file where you can download it. When you get it, rename your old config file, and copy the modified version in its place.

OK, we need to come up with another solution than me sending you my vegas130.exe.config. I'll contact SCS and see if they will/can liaise directly with you. This is getting in way too deep for me to and feel comfortable, to draw back from and STILL garner direct SCS support should ANYTHING go awry. I know you'd understand.

This is a real pickle, and no mistake!

Cheers

Grazie

I understand your reluctance to venture into an area of unfamiliar territory like what I'm suggesting. But, in actuality this is no more intrusive than the test of changing your UAC settings. There are two settings I believe I can add to the config file that may clear this all up. I'd only be modifying a COPY of your original config file. If the change doesn't work, simply delete my modified copy of the .config file, and rename the original back to what it was.

When windows starts a .Net application the .Net framework looks at the policy settings in the config file, if one is present with the same name name as the executable with a ".config" extension, and applies those policy settings to control how the program behaves in certain circumstances. One of the settings I want to add to the existing .config file is called useLegacyV2RuntimeActivationPolicy="true". Another is loadFromRemoteSources enabled="true". If these do what I expect them to, there will be no need to even use the "UnBlock" button action that I mentioned here a couple days ago.

But the only way I can try this out is to have someone with v13 installed on their PC give my modified policy file a chance. We both know how long, if ever, it would take to interact with Sony on this issue.

Hi Gary, I've done what I promised, I've contacted SCS and asked them to read this thread and invited them to get involved with the issues being raised.

You don't need a Rank outsider - moi - to the art of programing to muddy the waters even further.

Get it right with SCS and let's get a sane way forward - yes?

Cheers

Grazie

Gary, I appreciate what you are finding resident in the policy setting. This is likely an issue that SCS created of itself.
One thing I am wondering, however, is that some users now have TLT -apparently upto 1057 now running inside of VegasPro13. They also say they have UAC left on - but it is right to point out that of itself can have different levels of security.
I am also wondering if this actually effects anyone who does NOT have their NLE PC CONCURRENTLY connected to the Internet. I for one never use any NLE PC directly connected or even used once with the Internet - essentially disabling the territory of the IE explorer etc. So that opens another avenue of issue.
I note that because of other programs I am running VegasPro9.0e on an NLE PC with NET4 fully installed and have no issues with that.

Gary,

I'm sure you know this but I thought I'd post it for the purpose of illustration. Here's the content of my vegas130.exe.config file:

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

    <runtime>

        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

            <probing privatePath="mediamanager;x86;bdmux" />

        </assemblyBinding>

        <gcConcurrent enabled="true" />

        <generatePublisherEvidence enabled="false" />

    </runtime>

    <startup useLegacyV2RuntimeActivationPolicy="true">

    </startup>

</configuration>

Nothing super secret in there.

I could try to add loadFromRemoteSources enabled="true" but at the moment I have the .57 version of your script running just fine, and Giles Event Length Script also runs fine now that it's unblocked. I suppose I could re-block Giles script and try the modified config file...where would I insert that line?

Rob

There are so many factors that are coming into play with this issue, but the one that has had the most noticeable effect of all, was the security policy change that Microsoft introduced in .Net 4.x.

Until .Net 4, even though modules may have always had a security stream attached to them, that we now know can be removed via the UnBlock button, this was ignored in pre v4.x versions of the .Net Framework. With .Net v4.x, it's enforcing those security stream attributes that are attached to downloaded and networked files, preventing them from running.

From what I can find on this subject over the Internet, the two new entries in the application configuration file I mentioned, should force the .Net 4.x Framework to revert back to ignoring those streams.

It'd be best if Grazie tested it since he's got the problem and I don't, but I could create the problem and try it. If you want to pursue that send me an email through my profile. No need to have the whole conversation here.

Rob

"I'm sure you know this but I thought I'd post it for the purpose of illustration. Here's the content of my vegas130.exe.config file"

Thanks, that's helped me add the necessary changes to the file. Here's a link to anyone who is having problems and wants to give this a try. Download this version of vegas130.exe.config, Go to your Sony Vegas 13 folder and rename your existing vegas130.exe.config to something like vegas130.exe.config.old, then copy the downloaded version of the file into the Sony Vegas 13 folder. Then start Vegas 13 and verify if the change worked. If so great. You can leave the new file in place. If not, delete the new file and rename the old one back.

Download Link

Here's the config file after my changes.

<?xml version="1.0" encoding="utf-8"?>

<configuration>

  <runtime>

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <probing privatePath="mediamanager;x86;bdmux" />

    </assemblyBinding>

    <gcConcurrent enabled="true" />

    <generatePublisherEvidence enabled="false" />

    <loadFromRemoteSources enabled="true" />

  </runtime>

  <startup useLegacyV2RuntimeActivationPolicy="true">

    <supportedRuntime version="v4.0" />

  </startup>

</configuration>