Error In Cocreateinstance 0x80040154
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing
Netbackup Error In Cocreateinstance 0x80040154
Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange err error in cocreateinstance 0x800700c1 Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español
Cocreateinstance Failed 0x80040154
USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Attempts to back up 32-bit SQL on a 64-bit Windows server fail with a CoCreateInstance error message in the dbclient cocreateinstance failed code 0x80040154 log file. Article:000031670 Publish: Article URL:http://www.veritas.com/docs/000031670 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem GENERAL ERROR: Attempts to back up 32-bit SQL on a 64-bit Windows server fail with a CoCreateInstance error message in the dbclient log file. Error Message 08:29:19.401 [3408.1692] <16> CDBbackrec::InitDeviceSet(): ERR - Error in CoCreateInstance: 0x80040154 Solution Overview: Attempts to back up 32 bit Microsoft SQL server databases on a 64 bit Windows server fail with a CoCreateInstance error message in the dbclient log file. Troubleshooting: Enable the dbclient log file on the SQL server and review it for the error message shown below. Log Files: 08:29:19.401 [3408.1692] <16> CDBbackrec::InitDeviceSet(): ERR - Error in CoCreateInstance: 0x80040154.Resolution: Much like the CoCreateInstance error message in the related document below, the sqlvdi.dll file is not properly registered. In this case, however, there are multiple copies of the sqlvdi.dll file, and two Microsoft hotfixes are required to resolve the issue. 1. Begin by downloading and applying the Microsoft hotfix found at: http://su
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : MS-SQL backup fails - Error in CoCreateInstance: https://www.veritas.com/support/en_US/article.TECH48096 0... VOX : Backup and Recovery : NetBackup : MS-SQL backup fails - Error in CoCreateInstance: 0... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution MS-SQL backup fails - Error in CoCreateInstance: 0x80040154 Will_Restore Level 6 03-01-2013 01:29 https://vox.veritas.com/t5/NetBackup/MS-SQL-backup-fails-Error-in-CoCreateInstance-0x80040154/td-p/543686 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content SQL Server 2005; Windows 2008 Server; NetBackup 7.1.0.4 Backup using SQL Studio works fine. OS backup using NetBackup also works. Backup using NetBackup MS-SQL agentfails immediately with Error in CoCreateInstance: 0x80040154 An attempt was made to reference a token that does not exist Working with our Windows admin (I'm more versed in unix) but not much traction on this problem. Search on this forum and others has not turned up much help either. Solved! Go to Solution. Labels: Agent for Microsoft SQL Server Backing Up Backup and Recovery NetBackup Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! I think this is a Microsoft CRZ Moderator Employee Accredited Certified 03-01-2013 02:02 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I think this is a Microsoft issue. It sounds exa
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 11 Oct 2016 16:34:34 GMT by s_wx1094 (squid/3.5.20)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up COM Error: Class not registered (I'm sure it is) up vote 0 down vote favorite 1 I have a large complex program that has a COM problem. I'm attempting to write a much smaller SSCCE program to reduce the problem. However, no matter what I try, the CoCreateInstance in my SSCCE keeps coming back with hr 0x80040154 (Class Not Registered) (For CoCreateInstance) 0x800706B5: The interface is unknown. (for ICalendarPtr constructor) I'm using the same GUIDs and other parameters from the bigger program. (turns out I wasn't using the same guids. Just similar ones) I'm linking to the same libraries, and have the same DLLs available (both locally and properly registered in Program Files). I'm not a Registry expert, but looking through the registry, I do find the Interface and Class GUID look to be properly registered, with a TypeLib-key that refers to a DLL that is present and accessible. Can you think of something I might be missing that would cause one program to create a COM object successfully, but another to say the class isn't registered? Code: _COM_SMARTPTR_TYPEDEF(ICalendar, __uuidof(ICalendar)); int _tmain(int argc, _TCHAR* argv[]) { CoInitialize(NULL); CLSID classID = __uuidof(ICalendar); REFIID iid = __uuidof(IUnknown); LPVOID pRet; HRESULT hr = CoCreateInstance(classID, NULL, CLSCTX_INPROC_SERVER, iid, &pRet); // Result: 0x80040154 Class not registered GUID guid = __uuidof(ICalendar); ICalendarPtr pDtTm(guid); // Result: First-chance exception at 0x773dc41f in COMTest.exe: 0x800706B5: The interface is unknown. return 0; } c++ com registry share|improve this question edited Nov 13 '13 at 17:21 asked Nov 13 '13 at 17:05 abelenky 37k1465119 Same architecture? (32/64bit) ? You could always check the registry to see if it is, in fact, registered properly? –WhozCraig Nov 13 '13 at 17:06 Yes, same physical computer. Compiled with /MACHINE:X86 in both cases. My look at the registry does