Automation Error - 2147019886
Contents |
already exists This error code, 80071392 occurs when the printer or network drive already exists. A wild guess, you are running the script for the second time. If so, you could consider error correcting code, see example opendsobject 2 below. Introduction to Error Code 80071392 This is an easy error code to adsdsoobject troubleshoot. Code 80071392 usually occurs when you execute a VBScript. Most likely the object has already been created, perhaps you are running
Adsi
the script for a second time. The Symptoms You Get 80071392 The script does not execute as you hoped, instead you get a WSH error message. One possibility is that you are using a WSCRIPT and the object is already in Active Directory. The Cause of Code 80071392 Active Directory already knows about the user, OU or computer that you are trying to create. The problem is you are trying to create another object with the same name. Check the Line: number. Char 1: often lies! it just means that the whole line will not execute. The Solutions 1) Delete the object and start again. 2) Add this line in the script: on error resume next. ‡ Example 1 - Script with 80071392 error Note: The error is reported as Line 7, however it is actually the previous line where the problem was created. objUser.SetInfo just causes the error to emerge. ''Script to Create a new Contact account in the BulkImport OU 'Script created by Guy Thomas 'Feel free to adapt names Set objOU = GetObject("LDAP://OU=BulkImport, dc=cp, dc=com") Set objUser = objOU.Create("contact", "cn=SalesMan") objUser.SetInfo Wscript.Echo "Success new Contact " © Example 2 - Adding Error Correcting Code to deal with Code Error 80071392 This script offers something a little different, not so much an error as example of error correcting code.In this example I am creating a child OU. To handle the error I divided the OU path into strParent and strContainer. Most of the error correcting takes place in the subroutine called GuyError(). ' VBSCript to create a child OU (Organizational Unit)' With Error Correcting code' Author Guy Thomas http://computerperformance.co.uk/' Version 2.4 - September 2010' ----------------------------------------------------------' Option ExplicitDim objRoot, objDomain, objOUDim strContainer, strParent err.number = vbEmpty ' Section to bind to YOUR Active Directory.Set objRoot = GetObject("LDAP://rootDSE")objDomain = objRoot.Get("defaultNamingContext")Set objDomain = GetObject("LDAP://" & objDomain)' Section to create the OU defined by strContainer strParent ="OU=Accounts3"strContainer ="OU=Child9," & strParentOn Error Resume nextSet objOU = objDomain.Cre
General Discussions View all Getting Started with the Community Community News Get Connected Business Strategy & Best Practices Suggestions for this Community Technical Discussions View all Announcements Visualization Gallery Tech Corner Idea Exchange Platform (Installation & Deployment) Object Development Reporting, Dashboards, and Document Development MicroStrategy Desktop Clients (Interfaces & Visualizations) Administration Tools Intelligence Server Mobile Enterprise Assets (Data Sources & Gateways) MicroStrategy Software Development Kit (SDK) Security (Usher) Performance Events View all Events Blog Symposia 2016 Symposia 2015 Education World 2016 Discussions World 2015 http://www.computerperformance.co.uk/Logon/code/code_80071392.htm Discussions World 2015 Track Sessions & Customer Presentations Community Menu Register · Sign In · Help Object Development MicroStrategy > Technical Discussions > Object Development > "Automation error" error message appears when attempting to update the schema in MicroStrategy Desktop 9.4 x running on ... CommunityCategoryBoardKnowledge BaseUsers turn on https://community.microstrategy.com/t5/Object-Development/quot-Automation-error-quot-error-message-appears-when-attempting/td-p/253740 suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. "Automation error" error message appears when attempting to update the schema in MicroStrategy Desktop 9.4 x running on Windows 7 Reply Topic Options Float Topic for All Users Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page « Message Listing « Previous Topic Next Topic » amarnathreddy Newcomer Posts: 2 Registered: 07-25-2015 "Automation error" error message appears when attempting to update the schema in MicroStrategy Desktop 9.4 x running on Windows 7 Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Content 07-31-2015 08:41 AM Hi All , After creation of any schema object (Attribute or Facts) when I try to update schema, "Automation error" error message appears when attempting to update the schema in MicroStrategy Desktop 9.4. Can any one please let me know the root cause and assist. Solved! Go to Solution. Erro
User Rights to https://support.novell.com/docs/Tids/Solutions/10099582.html Active Directory for SecureLogin symptom Error: -2147019886 when Extending Active Directory Schema Error: -2147019886 when Assigning User Rights to Active Directory Unable to Extend Active Directory Schema for SecureLogin fact Microsoft Active Directory Novell SecureLogin fix To automation error extend the Active Directory schema and subsequently Assign User Rights you need to run adsschema.exe as a member of the Schema Administrators group,onaDomain Controller. You can thensubsequently transfer the schema FSMO to the other Domain Controllers.For automation error - more information how to accomplish thisplease see the documentation at http://novell.com/documentation under SecureLogin. document Document Title: "Error: -2147019886" Extending Active Directory Schema for SecureLogin Document ID: 10099582 Solution ID: NOVL104158 Creation Date: 07Nov2005 Modified Date: 07Nov2005 Novell Product Class:Netware Client disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.