Automation Error Unspecified Error Adobe 4.0
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 01 Oct 2016 18:57:38 GMT by s_hv978 (squid/3.5.20)
Buffington [MSFT]August 15, 201229 0 0 0 This article applies toWord, Access, Excel and PowerPoint. MS12-060 is a security update that was released Tuesday, August 14, 2012. This update replaced MS12-027. You may now be seeing one of the following errors: "Unspecified Automation Error" when running or compiling your Microsoft Office VBA code after installing MS12-060; or "Errors were detected while saving ‘filename.xlsm'. Microsoft Office Excel may be able to save the file by removing or repairing some features. To make the repairs in a new file, click Continue. To cancel saving the file, click Cancel." clicking continue you will see "Document failed to save" http://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_other/automation-errorunspecified-error/2c75ea54-981f-4634-ad25-f11647034000 or similar error. Update - 9/26/2012. See this blog post for the latest update. Fixit Available There is a fixit available for this problem: Office 2010 w SP1 - http://support.microsoft.com/kb/2597986 Office 2007 w SP2 or SP3 - http://support.microsoft.com/kb/2687441 Office 2003 w SP3 or Office 2003 Web Components w SP3 - http://support.microsoft.com/kb/2687323 Steps to fix the problem manually Alternatively, the manual fix for https://blogs.technet.microsoft.com/the_microsoft_excel_support_team_blog/2012/08/15/unspecified-automation-error-after-applying-ms12-060-updated-926/ this problem is to re-register MSCOMCTL.OCX. To do this, follow these steps: 1. Open an administrative-level command prompt. The command prompt MUST be on the administrative level for this to work. Click START, and type RUN in the run command line. On Windows Vista and Windows 7 you will see CMD.EXE appear in the quick searchlist. Right click CMD.EXE and left click Run As Administrator. A black command prompt opens. On Windows XP, there is no built-in run-as-admin, but you can use the run as menu option (or runas command line) to execute an admin command from a Limited User Account. 2. If on a 64-bit machine, type the following: regsvr32.exe /u C:\Windows\SysWOW64\MSCOMCTL.OCX Hit ENTER then type regsvr32.exe C:\Windows\SysWOW64\MSCOMCTL.OCX If on a 32-bit machine, type the following: regsvr32.exe /u C:\Windows\System32\MSCOMCTL.OCX hit ENTER then type regsvr32.exe C:\Windows\System32\MSCOMCTL.OCX Your Office program should work again after doing this. (Updated) 3. NOTE: The following step is done at your own risk. Microsoft doesn't know about any side effects to deleting this registry key. In cases where the re-registration doesn't work and you still get the error, you will need to open the registry editor (START > RUN > REGEDIT) and find andDELETE the following registry key: HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0 to HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000
Recognition Issues What do you do when QuickTest Professional (QTP) doesn’t automatically recognize an object in your application? In my experience, these are the first six things to try/check. https://www.joecolantonio.com/2010/08/12/quicktest-object-recognition/ 1.Check the loaded add-ins: It’s pretty basic, but be sure you have the correct add-ins selected. If QTP is only recognizing your objects as standard WinObject this may be a sign that you need to use an add-in. Sometimes QTP’s ‘Display Add-in’ Manager on start-up option, under Tools\Options\General may not be selected. This setting may cause you to start QTP on a machine and mistakenly assume that all of automation error the correct add-ins have been chosen. Double-check by opening your script and selecting File\Settings under Properties ‘Associated add-ins:’ verifying that all the needed add-ins are listed. Also make sure QTP is started before the application under test. QTP will sometimes not recognize a web application if the browser was opened before QTP. HP’s Knowledge base: Research the issue. If your add-ins are fine, the next step is to search automation error unspecified the HP’s Knowledge base. Again, this may seem obvious, but a surprising number of people fail to do this. There’s nothing worse than spending hours on a script only to discover later that there is a patch (for example see patch that resolves some QTP 11 object issues) available or a posted solution that will solve the problem. I'm sometimes hailed as an automation genius by fixing something that an engineer may have been struggling with for days, based on information I found in the KB. Often, even after I tell the engineer how I solved the issue, they still don’t check the KB the next time they have a problem. Do me a favor -- don't be that guy (or gal)! Check the KB. (If nothing is found in the KB, another great resource to check is SQAForums. 3. Using .Object: Look at all the available object’s operations (both the “identification properties” and “native properties” methods). You'll be surprised what you'll find lurking around in an object’s properties that may help to automate it. Using .Object try as many operations as possible-even ones that may not seem remotely relevant to the action you want to perform. For example: I was having a problem recognizing text