Results Explorer. error message in Revit 2022

[jaroslav.kopecky]

Hello,

since Revit 2022 we have issues with the "Result Explorer". We export our results to Revit and try to display them. Since version 2022 following message shows up:

Only change to our api code was to use ForgeTypeId for units as required with new version 2022.

You can see this error, when you open attached file and try to explore results.

If we export only Forces or Moments that issue doesn't show up. The export of deflections (deformations) is causing that error. We are however not sure what is causing the error exactly. Could you help us to track it down?

In case you need further information don't hesitate to contact me.

Greetings Jaroslav Kopecký.

[jeremy_tammik]

Dear Jaroslav,

Thank you for the report and sorry to hear about the problem. I passed it on to the development team for you.

Cheers, 

Jeremy

[jeremy_tammik]

The development team replies:

Did they debug and get a stack trace of the exception they received?  Likely an InternalException - I see that message associated with InternalException creation.   But they'll need to do the work to track down the source of the exception if we are to help them.

[jaroslav.kopecky]

Hello,

I have done a little bit of debugging, but in fact I couldn't see any creation error - no exceptions (there is no creation error, If I did not overlooked something).

So My assumption is, that I cannot judge what is wrong..

Exactly the same scenario - the same result package creation is working with version 2021.

If you see the screen picture (I will put in english here), during exploring the results, there is 3 green check-marks (that probably suggest that data consistency is ok) and the last check is related to filling a dialog. (coudn't be there some problem? some changes to your dialog?)

And you wrote that you could se some exception message. So what is that message about?

So my assumption is that the issue is in your explore results dialog.

Let me know if you have got some additional info or any conclusions.

Greetings Jaroslav Kopecký.

[jeremy_tammik]

Thank you for the update and additional explanation. I passed it on to the devteam for you.

[adrian.dumitru]

Hi,

Do you have any news about the problem ? I received the same exception when trying to explore the results for a surface element in Revit 2022.

It was working well in Revit 2021.

Thank you !

[jeremy_tammik]

I heard back that one developer saw the same behaviour as you report, but nothing more yet. I prompted them for further news now.

[jeremy_tammik]

Yes, good news. The development team confirm that they are aware of the issue and it will be addressed in an upcoming update release based on the issue REVIT-177216.

[colincargill]

I am having the same problem. Can you tell me when the fix will be issued?

Thank you, Colin Cargill

[jeremy_tammik]

As far as I can tell from the development ticket REVIT-177216, the fix was implemented in June last year. The fix versions are listed as Revit 2022.0.1 and Revit 2022.1.

[colincargill]

Hi there: As suggested, I installed the Hotfix 2022.1 but this has not resolved the error message. What's going on and when will it be fixed?

Regards, Colin Cargill

[jeremy_tammik]

Maybe your problem differs in some subtle manner from the behaviour addressed by the development ticket REVIT-177216 and the hotfix. Would you like to submit a minimal reproducible case to demonstrate exactly what your issue is?

https://thebuildingcoder.typepad.com/blog/about-the-author.html#1b