


I believe the error may be related to a change in references due to version changes but I am not sure. Set ieButton = ie.Document.getelementbyid(""submitbutton"")Īpplication.Wait (Now + TimeValue(""0:00:01"")) If frm Is Nothing Then Set frm = ie.Document.getElementsByName(""searchCriteriaForm"").Item(0)Ĭase ""searchVO.acbsObligor"": element.Value = obligorNumber Set frm = ie.Document.getelementbyid(""myFormID"") While ie.ReadyState 4: DoEvents: Wend ' 4: DoEvents: Wend Ie.Navigate https:/ Opens a new window / mlending.*******.com/ CFIWeb/ logout.do Set ie = CreateObject(""InternetExplorer.Application"") WouldYouLikeToContinue 'Msgbox letting user know they are leaving spreadsheet ObligorNumber = Sheets(""QC Checklist"").Range(""ObligorNumber"") I did modify some items for privacy reasons. I'm sorry it's so long but I didn't want to leave anything out. The object involved has disconnected from it clients.īelow is my code. When I attempt to run the same code on the new system I receive an Automation Error. I have code that currently runs well that will open a webpage and do a search for a number that was entered on the spreadsheet. My department will soon be transitioning from Win Xp/Office 2007 to Win 7/Office 2013. If you find any, close Microsoft Project, then kill the Excel processes in Task Manager, then reopen for Project.VBA - How to eliminate an Automation Error resulting from transitioning from Excel 2007 to Excel 2013? Use Task Manager to check for any Excel.exe processes that don't have visible windows. If you're using for Project release 4.1.4 (not release 6.x/7.x) and you have any background processes of Excel running, RISK may be unable to connect to Excel and you may get this error.

Follow the instructions in Removing Outdated References to Office from the System Registry to remove them. You may have COM registrations pointing to versions of Microsoft Office Excel or Project that aren't actually installed on your computer. If your simulation is not very large, switch to Multiple CPU: Disabled on the General tab of Simulation Settings.Ī couple of customers, who had multiple versions of Excel installed, reported that they got this error in Excel 2013 but not 2010 or 2007, with the same model. See Find and Fix Startup Conflicts (Excel 2007–2016). Following are strategies that have worked for different customers in resolving this error.Ĭlose everything and restart Windows – not just log off and on, but a full system restart.ĭoes this happen with more than one model? Check your active add-ins and try disabling them, then adding them back one by one. "Run-time error '-2147417856 (80010100)' "ĭifferent conditions can give rise to this error.
