Revit license fails during macro run

[Anonymous]

Hi,

I've created plugin for Revit, which exports certain views as automated process. Plugin works fine, but sometimes it's fails with license.

The strange thing about this is that when i open manually files license works fine, it just sometimes fails when process open/export Revit documents.

Here is the screenshot of the window which pop-up: 

Tested on few computers same error on all of them, Addin file is local file, checked LICPATH.LIC, also tried this solution:

https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles...

Tested also on borrowed license it was still happening.

I've been looking for solution all over forum and internet and can't find reason why it's happening.

Thanks for all advises

Tom

[mikako_harada]

Hi Tom, 

I don't know what is going on.  But is your problem happen with any add-ins?  For example, if you test with simpler tasks, you don't see the same issue?  

if you trace, can you tell at which call the problem happen?  Can you narrow down by stripping out the code?  

How about using a tool like process minitor to see what add-in accessing?  

https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx

also monitor network traffic using a tool like Fiddler?  

https://msdn.microsoft.com/en-us/library/windows/desktop/ff966510(v=vs.85).aspx 

[Anonymous]

Hi, thanks for answer.

It happens when plugin is opening .rvt file, also this happens only at Revit 2015, Revit 2017 works fine.

Fiddler and process monitor files:

https://we.tl/nmi5NQvrkK
https://we.tl/LuFCbOrgqZ

in report ProchemRevitExporter.exe is application which is calling plugin in revit (it works fine).

Plugin file was already send to autodesk help service (to Davide Mortillaro). So you can review it from there.

Regards,

Tom

[mikako_harada]

Hi Tom,

Good to know that the issue not reproducible with the 2017 at least.  That also signals that the code is probably okay with the assumption that API hasn’t been changed and also you rebuilt your project with the matching dlls.

Looking at the code David got, I see it’s not minimum and has plenty of code with dependency to excel and external files.  So I cannot run it as is. (I don’t have 2015 environment at hand, either.)  But one thing I noticed is the Macro declaration for IExternalCommand. From the description above, you are running an add-in, not macro. It may not matter, but just in case, you may want to try without macro declaration.

Typically, the way we debug will be to strip down the code as much as possible till you have minimum reproducible code.  For example, you may try just opening/closing a single file in a loop and see if you see the same issue.