Dynamo crashes upon attempting to save *.dyn file using the Desktop Connector

Dynamo crashes upon attempting to save *.dyn file using the Desktop Connector

w.somers
Contributor Contributor
839 Views
4 Replies
Message 1 of 5

Dynamo crashes upon attempting to save *.dyn file using the Desktop Connector

w.somers
Contributor
Contributor

Are there any limitations upon saving certain files to BIM 360 Document Management. Both Dynamo and Revit crash when attempting to access a directory in a BIM 360 Project through the Desktop Connector from Dynamo version 2.01.

 

All directory permissions in the BIM 360 project are configurated correctly. 

 

BUG REPORT DYNAMO 2.01:

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

at System.Windows.Forms.FileDialogNative.IFileDialog.Show(IntPtr parent)
at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner)
at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner)
at Dynamo.ViewModels.DynamoViewModel.ShowSaveDialogAndSaveResult(Object parameter)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

0 Likes
840 Views
4 Replies
Replies (4)
Message 2 of 5

Jacob.westergaard
Autodesk Support
Autodesk Support

Hi, 

 

Thank you for taking your time to post this on the forum,

 

There shouldn't be anything restricting the access from how it's designed, could you check and see if you are using the latest version of the Desktop Connector? 

 

Simply right click the icon > Help > Check for Updates. 

 

It's a tool that needs to be updated, so might be what's causing it. For testing I had a go at it with 2.01 and it seemed to be working fine. 

 

Let me know how it goes, 


Jacob Westergaard

Autodesk Premium Support Team
AEC Premium Support Services
0 Likes
Message 3 of 5

w.somers
Contributor
Contributor

Hi Jacob,

 

I'm currently using the latest version of the Desktop Connector. Did a second test in saving a *.Dyn file from within Dynamo 2.01 itself and Dynamo even crashed upon touching the BIM 360 icon. Couldn't open the directory.

0 Likes
Message 4 of 5

Jacob.westergaard
Autodesk Support
Autodesk Support

Hi Wout,

 

I think first of all, before doing anything else, uninstall and reinstall desktop connector. 

 

Then I would use something like procmon to log whatever is happening, if you're not able to look through the logs yourself, you can always send them to us. 

 

It would most likely tell us what is being blocked and give us some indication to what we need to be looking at. 

 

Most often procmon is something an IT savy person would be able to do, are you able to do that you think?

Thanks again.


Jacob Westergaard

Autodesk Premium Support Team
AEC Premium Support Services
0 Likes
Message 5 of 5

Dharman.Gersch
Observer
Observer

I'm getting the same problem.

It's not possible for me to open or save files through dynamo if they are located within a BIM 360 folder. Sometimes even expanding folders in the file open dialogue will cause dynamo and/or revit to crash.

 

Should it be possible? I'm using Dynamo 2.0.3.0 Revit 2018.3 and desktop Connector 12.3.0.971

 

I tried looking at procmon logs, which don't mean a lot to me. There's quite a spattering of results such as NO SUCH FILE, NAME NOT FOUND, FILE LOCKED WITH ONLY READERS, BUFFER OVERFLOW, NO MORE FILES, END OF FILE, NAME COLLISION

 

here's an entry

 

5:37:11.0852169 PM DesktopConnector.Applications.Tray.exe 20640 CreateFile C:\ProgramData\Autodesk\AdSSO NAME COLLISION Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0

 

0 Likes