Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Using iManage (AKA Filesite, Worksite) 8.5 and Excel 2007. Having trouble saving documents locally. Saving into iManage works fine, but trying to export documents to a local directory using 'local save' triggers an error.

Error #429 ActiveX component can't create object

No 'save as' dialog is presented. Hitting ok on the error just returns the spreadsheet to focus. The add-ins are all enabled and local save works fine in word. Disabling the add-in allows users to save locally.

share|improve this question

2 Answers 2

Be sure to check both Disabled Items and COM Add-ins. I've seen it show up in disabled items but also seen the COM add-in get unchecked. you'll have to launch excel using run as admin in order to re-check that box. then close, relaunch normally and try again. Other thought - be sure to check the registry for excel add-ins and the load behavior is not set to 2.

from Autonomy support page:

"an error occurred in the com-add-in name 'iManO2k'. Error #429 ActiveX component can't create object Location:[modOffice2000Common][ShowLocalFileSaveAsDlg]

Cause: A shared resource, specifically, the scrrun.dll, has become unregistered or corrupted. Scrrun.dll is a system DLL that provides additional objects for reading and writing text files in a file system.

Resolution: Re-register the scrrun.dll. To register a dll, go to Start | Run and type regsvr32.exe [location of dll] scrrun.dll


More from Autonomy Support: just more of the same scrrun.dll and some long winded, best practices and other explanations of their dll's.

sorry can't be of more help.

share|improve this answer
    
Thanks, tried that. Got DLL "registered successfully", but didn't change the error. –  Ryan Mar 6 '12 at 23:21
1  
They list some other solutions - will update my answer with a few other options from their support site soon. –  Jordan W. Mar 7 '12 at 12:10
up vote 0 down vote accepted

For anyone else who encounters this issue. This was a version mismatch. iManage server was updated, but clients weren't.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.