Export Project Failed (Error 100013)

Export Project Failed (Error 100013)

Anonymous
Not applicable
12,039 Views
23 Replies
Message 1 of 24

Export Project Failed (Error 100013)

Anonymous
Not applicable

I keep getting this problem where I am exporting a registered .rcp file to .rcs. My rcp file itself is 129GB in size. The point cloud itself was registered with Faro Scene 5.5.0.44203. It was exported from Faro Scene as a .rcp file. Now what I want to do is to create .rcs file. My Recap version is Recap 360 Ultimate 2.2.0.25. Last time I checked my screen, it has reached about 40% completion. I left it overnight and by the time I checked back in the morning, I saw this Error 100013 message. I didn't see Autodesk Recap 360 Error Report page and my Recap didn't crash. 

 

Below, I attached the screen shot of the error message I got.

 

Computer specs: Core i7-4900MQ @ 2.8GHz, 32GB RAM, AMD FirePro M6100 FireGL V, Windows 7 

 

Thanks in advance.

0 Likes
12,040 Views
23 Replies
Replies (23)
Message 21 of 24

Anonymous
Not applicable

Hi,

 

Has anyone found a solution to this? 

 

I have installed the latest recap version (4.2.0.2).

 

I have a 1TB SSD drive, 64gig of ram, quadro K4100M graphic card. 

 

I have tried the export process for a 25gig recap project (I have 40+ projects like this to export in RCS for next week...). The files were all optimized + saved as and erase points...

 

We have tried on 6 different computers with different configuration, all with high performance configurations) and yet they all failled to export projects with about 25gig size (support folder size).

 

So has anyone managed to export a file that was giving them an error 100013? 

 

Ex; is it a computer issue? do you get this error on one computer but managed to export the same project on another computer?

 

or is it a software issue? 

 

Thank you,

 

 

0 Likes
Message 22 of 24

efaustoD3RAG
Contributor
Contributor

I got the same error trying to unify a 2 GB RCP with 200 free GB on my internal SSD. I was trying to overwrite an existing file - unifying to a new file worked fine.

 

This workaround isn't apparent since this error is usually associated with disk space, so I thought I'd share.

0 Likes
Message 23 of 24

wizard_ettore
Advocate
Advocate

I've had this issue with most versions of Recap, and it happens a lot less if I am writing directly to the local drive. It has never been space related, but since I have more issues with writing to our server, I assume it has to do with the software not dealing well with hiccups in file writing.

Usually I fix it by exporting a second time, or restart the software. If that doesn't work, restart the PC.

0 Likes
Message 24 of 24

orlando7TTD4
Observer
Observer

When using OneDrive, try exporting to a folder or location that OneDrive is not updating. For some reason, exporting .rcp files into OneDrive syncing folders will show this error. 

0 Likes