Etabs Adapter is not able to launch Etabs
verasluijter opened this issue · comments
Description:
When using the Etabs adapter and toggling it to active, it doesn't seem to be able to launch Etabs. It does start doing it, showing the etabs start-up frame on my screen. But then it closes off and gives this error:
_1. This component failed to run properly.
- Error: Failed to read from an IPC Port: The pipe has been ended. - Occured in BH.Adapter.ETABS.ETABSAdapter..ctor(String filePath, EtabsSettings etabsSetting, Boolean active)
called from BH.UI.Base.Caller.Run(List`1 inputs) - Are you sure you have the correct type of inputs? Check their description for more details._
When I already have etabs open, it does work. So the problem is in the launching. I have Etabs 19 installed.
Steps to reproduce:
Just use the etabs adapter and set it to active.
Expected behaviour:
That it can launch etabs.
Test file(s):
Thanks @verasluijter, could you confirm:
- which version of ETABS you are using when you experience this bug
- which version of the BHoM installer where you experiencing this on, or if you compiled from source and the specific branch you used
@alelom
Etabs 19
BHoM v6.1.0.230131
Thanks @verasluijter , this is because ETABS 19 is not yet supported, as mentioned in the ReadMe:
https://github.com/BHoM/ETABS_Toolkit#readme
I will close this issue as not a bug, but feel free to raise a new "feature" issue requesting the support of ETABS 19.
Etabs 19 should actually work - readme is out of date.
Have had a look at this now, and get the same behaviour on my machine.
Updating the nugets have sorted this problem my end, but a bit cautious of making a nuget upgrade this close to beta release.
so either we live with the fact that one has to start Etabs before activating the adapter, or we make the slightly risky Nuget upgrade.. Currently leading to option one for now, even if it means slightly worse UX, as the adapter at least on my end works just fine as long as ETABS is running before it is activated.
Not sure what the adoption of ETABS_Toolkit is, just wanted to mention that in some cases not doing Nuget updates is also not risk-free, and this seems to be one of such cases. Personally if time permits (if we have resources to test) my choice would be the second one: upgrade packages, test by going through full test procedure. Understand time constraints though.