CWITEC

MeanMrMustard · Post by **MeanMrMustard** » Mon Oct 22, 2018 1:32 pm

Can not get Version 3.02 to run, I'm getting IDispatch Error #3603 upon start. I do have ver 1.4 and 2.4 installed and running.

How can I correct this problem ?

Thank you....

elcallio · Post by **elcallio** » Mon Oct 22, 2018 1:35 pm

Can you provide your installation details? OS version, which plug-in flavour did you run, and which host?

MeanMrMustard · Post by **MeanMrMustard** » Mon Oct 22, 2018 3:19 pm

Yes of course, sorry for leaving that out.

- Win10 Home 64 bit

- 64bit vst2 only of tx16 (free ver)

- I used both Savihost ver 1.42 64bit (where vers 1.4 and 2.4 of TX16 do work fine), and then tried Studio One 3.5.

elcallio · Post by **elcallio** » Mon Oct 22, 2018 5:13 pm

Is "IDispatch Error #3603" the only output? If you get a COM error like that there should be some additional info in the error message?
I have no idea exactly which function might have thrown here. To bad you could not get a minidump.

MeanMrMustard · Post by **MeanMrMustard** » Mon Oct 22, 2018 6:48 pm

elcallio wrote: ↑Mon Oct 22, 2018 5:13 pm Is "IDispatch Error #3603" the only output? If you get a COM error like that there should be some additional info in the error message?
I have no idea exactly which function might have thrown here. To bad you could not get a minidump.

Yes I only get that small error window (see attachment) upon startup. With both Studio One 3.5 and Mixcraft (just tried it) I get the same "IDispatch Error #3603" popup during the DAWs startup. I believe they both initialize VSTs before they start. In the photo you can see where Mixcraft stopped during initialization when it got to TX16 and the Warning/Error message popped up.

Yet vers 1.4 and 2.4 of TX16 both load fine.

elcallio · Post by **elcallio** » Tue Oct 23, 2018 11:28 am

So this looks like there is some issue with your msxml (windows built-in xml parser). Can you check the version of your C:\Windows\System32\msxml6.dll file?

MeanMrMustard · Post by **MeanMrMustard** » Thu Oct 25, 2018 11:54 am

elcallio wrote: ↑Tue Oct 23, 2018 11:28 am So this looks like there is some issue with your msxml (windows built-in xml parser). Can you check the version of your C:\Windows\System32\msxml6.dll file?

It appears to be 6.30.17134.345 (see the photo below for all info)

Does this file need to be updated ? Other files as well ? If so how does one go about this ?

Thank you...

BTW, the latest vers of TX16 is outstanding and far and away exceeds other sampler apps.

elcallio · Post by **elcallio** » Thu Oct 25, 2018 12:18 pm

No, that looks exactly right. Do you still get the error with the latest build? Is there any more info in the error message?

MeanMrMustard · Post by **MeanMrMustard** » Fri Oct 26, 2018 11:33 am

elcallio wrote: ↑Thu Oct 25, 2018 12:18 pm No, that looks exactly right. Do you still get the error with the latest build? Is there any more info in the error message?

Yes, I still get the error with the latest version 3.0.5

No, there are no other error messages. Just the IDispatch Error #3603

However prior versions load and work fine, there must something about the 3.xx builds that are causing this ?

Thank you...

elcallio · Post by **elcallio** » Fri Oct 26, 2018 3:05 pm

Yes indeed. And now I am even more confused as to where it comes from.

MeanMrMustard · Post by **MeanMrMustard** » Sat Oct 27, 2018 11:15 am

elcallio wrote: ↑Fri Oct 26, 2018 3:05 pm Yes indeed. And now I am even more confused as to where it comes from.

Is there any way I can produce a 'log' of sorts that I could send to you that would show the startup sequence of TX16 and help to determine what the cause of the problem is ?

And thank you for your tireless work and excellent app.