Just installed Civil 3d 2017.
We are getting the following error when trying to start Hydraflow Express from the Analyze Tab "Invalid Installation. Program Ending"
Multiple Computers, some with clean installs (First time for any Autodesk Software)
Thanks,
Solved! Go to Solution.
We are facing the same issue. I tried this support article and could not get the program to run even though the folders and files are in the correct location. Anyone have a solution for this?
Although not ideal, an uninstall and stand-alone installation fixed the problem.
Now to do it to 7 more stations.
I am working with AutoDesk and have a case number - 11893454. I am working through some fixes with them now and will post here if we have a solution.
Conan, did you get a different resolution from Autodesk? We are having the same issue. I am going to have to uninstall and reinstall 15 computers...what a pain!
Kimberly Fuhrman, LEED AP BD+C
Freelance Architectural Technologist
Even that didn't work for me. I had to install 2016. I am told they are aware of it, so we have decided to wait out the service pack if possible and only do the additional install if needed.
Not everyone needs it, but we have already installed 2017 so our projects are not backwards compatible.
As I told the AutoDesk install tech, not a solution, rather a very complicated workaround.
Just an FYI SP! did not fix this, at least for me. I have not rolled it out to the office yet, so not sure about other machines.
From what I understand, SP1 has its own issues. We have not installed, either. I have downloaded the C3D installer (even though we have the Suite media, Autodesk insisted it's different.) I have yet to test the deployment.
Kimberly Fuhrman, LEED AP BD+C
Freelance Architectural Technologist
There is a an error in knowledge base article about this issue.
In solution 1, if you change it from local to roaming the fix works.
C:\Users\<user>\AppData\Local\Autodesk\C3D 20xx\enu\HHApps
C:\Users\<user>\AppData\Roaming\Autodesk\C3D 20xx\enu\HHApps
@kmfuhrman - how is it, that this KB article was published over a year ago, but this "fix" was not included in any of the Civil 3D 2017 SP, hotfixes, updates, etc.? Am I missing something?
Seems like all they have to do it change the folder where this gets dumped (roaming instead of local). Seems like low hanging fruit....
Can't find what you're looking for? Ask the community or share your knowledge.