Add-In not found?

[Muppett1]

Hey guys, I've used the backplotter add-in to verify quirkly tp before in earlier versions of FCam, but I just tried to use it in FCam 2018(I still can't download FC2019 btw), and the pop up window says "Public Macro not found".  I've found the backplotter.bas file in my 2018 FC folder, but why isn't it recognizing it?  Also, I've just had a hard drive upgraded, so could this possibly be what's causing the hiccup?  The Manage Add On button is opaque and not working btw.

TIA

[Muppett1]

Thank you Beth!  I'm going to try to uninstall 2018 and reinstall first, then maybe try 2019 again. 

[Muppett1 · Accepted solution]

I just uninstalled, then re-installed 2018 original release and this has solved the problem.  The buttons are now active.  Thank you Beth!

[Muppett1]

Everything was great, was downloading and installing all the 2018 updates and all went as planned, then I tried to download FCam 2019, and I received the same 1063 error, AND my 2018 program went all to heck again!  Having to start over with re-installing 2018 again, and I'll have to stop there for the time being.  What could be the issue when I'm trying to load FCam 2019?  That  has to have been the issue all along I believe now.

[Muppett1]

More details include loss of preview pictures, as well as the opaque addin buttons.  All these were working fine until I attempted to download FCam 2019, then it all collapsed again.

[Muppett1]

I also tried downloading 2019 while having 2018 completely uninstalled, to no avail, still keep receiving the 1063 error.

[beth.cobbYRSKN]

I agree with you; sounds like you've uncovered the root cause of the addin problem. I don't have a good suggestion for the 2019 installer problem, but here are some bits of information that might help.

The files that you need for running macros in FeatureCAM are stored on this folder:
      C:\Program Files\Common Files\Autodesk Shared\FeatureCAM
You could make a backup copy of that folder while you have a working 2018 and stash it somewhere until you get 2019 installed correctly. Then at least you wouldn't have to uninstall/reinstall 2018 every time - you could just copy the folder back. If you try the 2019 install again, you could check whether that folder even exists after the failure, and if so, what files are present compared to the backup.

I googled for the 1063 error ("windows installer 1063 error") and got nothing for 1063, but a whole bunch of info for 1603, so presumably that was just a typo. The 1603 looks like a very general catch-all error from the windows installer framework, and it can have many causes. Given the symptoms you're seeing, maybe it has something to do with permissions on that Common Files folder? But in that case I don't understand why 2019 has problems when 2018 doesn't.

Here are a couple of the links that list a variety of causes (there are plenty of others):
https://www.msigeek.com/715/how-to-troubleshoot-the-error-1603-fatal-error-during-installation
https://support.microsoft.com/en-us/help/834484/you-receive-an-error-1603-a-fatal-error-occurred-dur...
Maybe something in there might sound familiar to you?

@abhishek.juvekar, have you heard of anybody else getting this error during install?

[Muppett1]

Thanks again Beth, I'll have to try to see what I can come up with later on, as I just got FCam 2018 back up and going with all the updates and fixes.  😉

[abhishek.juvekar]

Hi @beth.cobbYRSKN,

No, I have not heard from any other customers in the recent days reporting this issue.

Thank You.

[Anonymous]

I am using FC 2019 and too, having the same issues.

The addins are not even reachable.

I can browse to the location but not use any of them.

Even the addins, run basic macro, etc... buttons are greyed out.

They do not work in any version now.......

[Muppett1]

Have you tried uninstalling and reinstalling the original release of FC2019?  My main issue was that the IT Dept had not upgraded a mainframe update.  After they completed the update, I was able to start over, installing FC2018, then FC2019, and my add-in buttons were activated, as well as other features that weren't accessible.  Hope this helps.