Error with Hydraflow Express 2017 installation

[Anonymous]

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,

[hmartinez5]

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?

https://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticl...

[KyleNishioka]

I'm having the same issue as well. However, the issue seems to only affect users who have a network license. Those who have a stand-alone license can use Hydraflow Express 2017 with no issues (yet).

[hmartinez5]

Although not ideal, an uninstall and stand-alone installation fixed the problem.

Now to do it to 7 more stations.

[Anonymous]

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.

[hmartinez5]

Any updates from Autodesk?

[KyleNishioka]

I would not call what they gave me a fix. I think my deployment is still messed up and I am contemplating whether I should delete it and create a new one in the hopes that it was just a glitch in the deployment creation tool.. The workaround is to perform a clean uninstall of all Autodesk products and then install Civil 3D by itself, without the rest of the Infrastructure suite. The installer for Civil 3D can be found through this link: http://autodesk.creativevirtual15.com/autodesk/bot.html?isJSEnabled=1&businessArea=Root.Front%20Desk... You have to navigate a bit to get to the actual download links, the installer is split into 3 parts. Once C3D is installed and Hydraflow Express is working, push out the deployment as normal. The deployment will see that C3D is already installed and skip that part of the deployment.

[kmfuhrman]

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!

[Anonymous]

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. 

[kmfuhrman]

I've created another case report - Case ID: 12061288. And referenced the link to this forum thread.

[Anonymous]

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.

[kmfuhrman]

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.

[Anonymous · Accepted solution]

There is a an error in knowledge base article about this issue.

Link: https://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticl...

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]

That was it! Thanks, mromeo!

[Anonymous · Accepted solution]

One of our C3D 2017 Network license customer's experienced the very same issue yesterday. The solution of copying the HHApps folder contents from a working machine to the Roaming path vs. local path worked like a charm. Thanks much 'mromeo'!

[Anonymous]

Copy to Roaming worked!

Thanks,

[KirkWM]

Worked for me too! Thanks!!!

[rkmcswain]

@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....

[KyleNishioka]

It's also a low priority bug.  Luckily, the issue seems to have been
fixed in 2018.

[Anonymous]

Had the same issue on at least on 2018 install. I remembered the fix from last year.
The dev team needs to take a break and fix everything they have broken along the way. I am getting tired of Work arounds and multiple visits to every install to install hot fixes and fixes like this.