Autodesk Installation Diagnostic Assistant (AIDA) Python Error

[dgladfelter]

I was just working to install the AIDA tool, and keep receiving the following Python error.

I have tried restarting my computer; uninstalling the utility; and reinstalling with elevated Administrator permissions.

I have similarly verified the Python34.dll file located C:\Program Files (x86)\Autodesk\AIDA\ matches the one bundled in the AIDA installer.

I do not have a c:\Python34\ directory.

[Mark.Lancaster · Accepted solution]

@dgladfelter

You need to clean out your personal temp (%temp%) folder as much as possible and then try again.

Anyhow why do you need the AIDA?  Are you having installation issues?  If so just post your installation log file here and we can tell you what the issue is.  Also are you trying to install through your Autodesk Account/Install now option?

[dgladfelter]

Thank you, that did the trick.

I am not currently troubleshooting any installation issues, but simply exploring AIDA to be able to share with industry peers who are not as versed at reading LOG files.

Thanks again for your help.

[Anonymous]

I do experiment the same problem. My goalis to understand why i do permanently catch error when installing the Revit 2017. AUtodesk tells us >AIDA might help understanding why install fails, the purpose of AIDA is to examine install log files if i understood correctly. The solution you provide is to clean temp folders where the instazll logs are, welll thzat's logic and i bet it will help a lot examining files that were deleted.

Your other question is why the users wants to use AIDA and me too, well i would answer : to solve my issue and understand those 1603 errors we get on the Revit install at the C++ 2005 redist install (which by the way i already made manually without any problem)

Does AIDA breing me coffee to help solving issues ???

Daniel Diligent 

[dthede]

    I have the same problem as Donnie G., however I am reluctant to totally clean out my %TEMP% without knowing what I'm getting rid of. I can see deleting the 500 or so zero-byte files.  Some files there are log files, and others are in GUID "{...}" named folders that track various installations of MS Office, and many other pieces of software. The suggestion to clean them all out seems to be "a shotgun approach."

Can you be more specific about which temporary files are (likely to be) causing the AIDA startup failure?

[pendean]

Friend, there is a reason the folder is called TEMP, as in TEMPORARY, as in NOT PERMANENT, it's an OS dump folder for content used only temporarily during software temporary installs files/folders, install log, crashes logs etc. There is nothing you would ever need in there ever again.
You can Google search it, it is the year 2017, you never need to ask, here is a quick link and explains things more that I did if you want to start reading https://www.pcworld.com/article/2602104/windows/how-to-clean-your-windows-temp-folder.html

BTW, what files are actually needed by any running app will be locked and Windows will not let you delete them no matter how hard you try. So there is a built-in safety already in place.

But if it bothers you so much, make a copy of it somewhere else first. Note that Windows may prevent you from copying some files (same ones it prevents you from deleting as I noted earlier).

[dthede]

Thankyou, Pendean, for your gracious and informative reply. I always wondered what 'TEMP' meant. Here I was all these 25 years thinking it had something to do with 'TEMPerature' but I could never figure out what. Sure glad I checked into this Form!