Has anyone experienced 1603 errors with Pinnacle Studio 14 HD? I'm getting a 1603 error, but it seems random and does not happen at all on v15.
Answer Summary:
Double install of Pinnacle Studio 14 HD with an added reboot between installs solves the problem.
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

4
create a log file with /l*v parameter and see where it is failing.
Answered 03/20/2012 by: piyushnasa
Red Belt

  • Yeah that was my next step, was curious though if I was lucky enough, to find some in here, who had the experience with Pinnacle Studio 14 HD.

    But log file it is, will update with my results.
  • Remember that 1603 is very much a generic error. In your shoes, I'd be running ProcMon alongside the install.
  • Getting an 1721 error, but the strange thing, this doesn't happen all the time and while it does require .net 3.5sp1 and Windows Installer 4.5, both of these items are already installed, as it's on Win 7.

    To make it even weirder, if the install is being run on the same machine, the second time, it always passes through.

    It never happens when the install is being run manually, so I'm guessing the installer has some random issue with silent installs.
Please log in to comment

Answers

1
Dirty solution that works: After install (which fails), machine reboots automatically (scripted) and runs the install again, which works. Not perfect, but it works with the buggy installer.
Answered 03/21/2012 by: Erroneus
Fifth Degree Black Belt

Please log in to comment
1
If the manual install always passes you should take a look at the InstallUISequence. Maybe you will find some CAs which need to be put the InstallExecuteSequence as well.
Answered 03/21/2012 by: Teitan
Senior Purple Belt

  • Good idea, will do that when got the time, spend way to much time on this one :)
  • Are you testing this on a VM?
Please log in to comment
Answer this question or Comment on this question for clarity