This content has been marked as final. Show 4 replies
When I opened the ArcMap document on Monday morning, the error did not appear again. I've added some fiber cable features and splice closures without the error popping up.
Thanks for your email and sorry for the late response.
I have seen this error message recently and i'm looking into the cause and a fix. Can you let me know what SP level you are on and any patches or additional AddIns you might be running. Might take me some time but hoping to work out the cause of this soon. Thanks
Mark Reddick | Technical Marketing - Telecommunications
Esri | 606 Columbia Street NW, Suite 300 | Olympia, WA 98501 | USA
T 360-754-4727, x8954 | firstname.lastname@example.org | esri.com
I have a relatively new PC with Windows 7, 64-bit OS. I have ArcGIS 10 - SP2 installed with the DFRS patch. Sorry, I can't remember what that patch fixed. I have been adding cable & splice cloures without any errors. Perhaps I simply had to re-boot in order for the COM objects to register properly? The documentation included with the download is very good and easy to follow. I know this would take some time, but it would be very helpful to have another video showing all the steps to add a new overhead cable & splice closure with the fiber attributes, etc. It took me over an hour to figure out that a splice closure could not be snapped to a pole feature in order for the Splice Editor dialog to work as advertised in the video. But, all things considered, this model seems quite robust and I was thrilled to find it on the Resources page.
I've ran some more testing against SP2. I wasn't able to reproduce this error but i definitely found some things that could explain it. I have created an updated setup.exe in the arcgis.com download for this template. I created folders in the zip download for the different compiled levels, so there is a 10.0 and 10.0 SP2 folder. Can you uninstall the current fiber tools (through Add Remove Programs) then run the new setup.exe in the SP2 folder.
Let me know if you still see those same errors after that?
I'm hoping this might get rid of them,