Ole Error Code 0x80010105
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Microsoft: Visual FoxPro Forum at Tek-Tips HomeForumsProgrammersDBMS PackagesMicrosoft: Visual FoxPro Forum Excel2007 automation error - the server threw an exception thread184-1429628 Forum Search FAQs Links MVPs Excel2007 automation error - the server threw an exception Excel2007 automation error - the server threw an exception BenAir (Programmer) (OP) 26 Nov 07 05:19 Hi there:My client application creates an excel file (using COPY TO (filename) TYPE XL5) then uses automation to do some reformatting.This has always worked fine but, since upgrading to Excel 2007, the client now sees this error when VFP (version 7) attempts the automation:-OLE Error Code 0x80010105: The server threw an exceptionHere is the beginning of my automation code:-oXL=CREATEOBJECT("Excel.Application")oXL.displayalerts=.F.oWB=oXL.Workbooks.add(filename)oModel=oXL.ActivesheetoSheet=oModeloSheet.Name="New Name"But it doesn't get this far as the excel file has not had the worksheet name changed.Any ideas people please? RE: Excel2007 automation error - the server threw an exception white605 (TechnicalUser) 30 Nov 07 20:47 Your code threw an error in my xl 2003.I changed the code a bit to just add a new workbook, then immediately name it by saving as, then proceeded to change the name of the sheet in the workbook and it seems to work."not t
OLE error code 0x80010105: The server threw an exception. My code that sets it off is in the "THISFORM.oOutlook.send code" line seen below: THISFORM.oOutlook.init() THISFORM.oOutlook.show() THISFORM.oOutlook.New() THISFORM.refresh IF EMPTY(txtto) MESSAGEBOX("Needs Email Address") ELSE THISFORM.oOutlook.SetTo(txtto) ENDIF IF EMPTY(txtCC) ELSE THISFORM.oOutlook.SetCC(txtCC) ENDIF IF EMPTY(txtSubject) STORE NULL TO txtSubject ELSE THISFORM.oOutlook.SetSubject(txtSubject) ENDIF IF EMPTY(EdtText) MESSAGEBOX("Please include a message") ELSE THISFORM.oOutlook.SetBody(EdtText) ENDIF IF EMPTY(txtAttach) ELSE THISFORM.oOutlook.AddAttachment(txtAttach) ENDIF THISFORM.oOutlook.send THISFORM.oOutlook.destroy THISFORM.RELEASE MESSAGEBOX("EMAIL SENT") I am doing this program as Rod Paddock is his book, "Visual Foxpro 6 http://www.tek-tips.com/viewthread.cfm?qid=1429628 Enterprise Development" (awesome book by the way) says to handle the OLE automation. As a matter of fact I am using his code as my framework. I know his code should work. I have a feeling it might be outlook acting up. In the init method of my form I use the following line: SET PROC TO OFFICAPI THISFORM.AddObject("oOutlook", "cusOutlookAutomation") The program blows http://computer-programming-forum.com/2-vfp/e1f1deed61ae1dfa.htm up the first time it is run but it works fine during subsequent times. It also seems to run fine on my boss's computer. Anyone have any ideas. I thought I fixed it when I applied the Visual Studio's latest upgrade. Is a MAPI SESSION a better way to go??? By the way, it works fine if Outlook is already open. Thanks for any help you might give. Jeff White CTI programmer/analyst TelSpan Inc. 1-800-631-6565 Ext 200. Sat, 22 Dec 2001 03:00:00 GMT Jeffrey Whit#2 / 3 OLE error code 0x80010105 Never mind. I found the answer. Hidden away on, but not installed automatically by the SR2 for Office is an OLE32 upgrade. It totally fixed the problem. Now why didn't they explain this anywhere???? JW Quote: >I thought I had it fixed but no luck. I am getting, now an intermittant OLE >server error: OLE error code 0x80010105: The server threw an exception. >My code that sets it off is in the "THISFORM.oOutlook.send code" line seen >below: >THISFORM.oOutlook.init() >THISFORM.oOutlook.show() >THISFORM.oOutlook.New() >THISFORM.refresh >IF EMPTY(txtto) >MESSAGEBOX("Needs Email Address") >ELSE >THISFORM.oOutlook.SetTo(txtto) >ENDIF >IF EMPTY(txtCC) >ELSE > THISFORM.oOutlook.SetCC(txtCC) >ENDIF
using the downloadable Ole Error Code 0x80010105 Repair Kit to fix Ole Error Code 0x80010105 errors The following discussion features detailed instructions for fixing Ole Error Code 0x80010105 errors in Windows system files. Both manual and http://thewinwiki.org/ole-error-code-0x80010105/ automated techniques are described that are designed for novice and advanced users, respectively. The overview also provides basic troubleshooting procedures to follow in order to resolve typical causes of Ole Error Code 0x80010105 error codes. What are http://www.pcreview.co.uk/threads/ole-server-error-related-to-office-2007-installation.3903004/ Ole Error Code 0x80010105 errors? A Ole Error Code 0x80010105 error code is caused by a Hexadecimal formatting error. That format is the most common one that software programmers employ for Windows system files and Windows ole error OS-compatible hardware drivers and software apps. Manufacturers and developers of software apps and hardware drivers use different codes to indicate various types of errors. The Ole Error Code 0x80010105 error message appears as a long numerical code along with a technical description of its cause. In many instances, a Ole Error Code 0x80010105 error code could have multiple Ole Error Code 0x80010105 parameters. Each hexadecimal code denotes a different memory address location that ole error code loaded instructions when the error was generated. Additional messages associated with this matter: Install Ole Error Code 0x80010105 Reinstall Ole Error Code 0x80010105 Ole Error Code 0x80010105 crash Ole Error Code 0x80010105 is missing Remove Ole Error Code 0x80010105 Download Ole Error Code 0x80010105 Ole Error Code 0x80010105 virus How are Ole Error Code 0x80010105 error codes caused? Most Ole Error Code 0x80010105 errors are due to damaged files in a Windows operating system. Windows system file entry corruption is a serious matter, as it often means a malfunction that may pose a major security risk. If left unchecked, it could result in total and permanent loss of all data and inoperability of the storage media and/or PC device. Numerous events may trigger system file errors. Most common examples include: 1) incomplete software installation; 2) incomplete software uninstallation; 3) improperly deleted hardware drivers, and 4) improperly deleted software applications. Also, Ole Error Code 0x80010105 errors are very common during PC restarts that immediately follow a previous improper shutdown and recent virus or malware infection recovery. Such incidents often result in the corruption or even total deletion of essential Windows system files. When system files are missing or corrupted, data that is essential to run software applications properly cannot be linked correctly. Specific causes and solutions for Ole Err
An Excel automation process that has worked dependably with Excel 2000 and 2003 for over 3 years no longer works for a client on systems that have been upgraded to Office 2007 - but continues to work on their systems where Office 2003 is installed. The application works on my development system and on other systems here where Office 2007 is also installed. The error is "OLE error code 0x80010105: The server threw an exception." The code is: oX=Createobject("Excel.application") oBook= oX.Workbooks.Add() (fails on this line every time) Any thoughts? E F Leo, Oct 8, 2009 #1 Advertisements Barb Reinhardt Guest I'd change it to Set oX=Createobject("Excel.application") Set oBook= oX.Workbooks.Add() HTH, Barb Reinhardt "E F Leo" wrote: > An Excel automation process that has worked dependably with Excel 2000 and > 2003 for over 3 years no longer works for a client on systems that have been > upgraded to Office 2007 - but continues to work on their systems where > Office 2003 is installed. The application works on my development system > and on other systems here where Office 2007 is also installed. > > The error is "OLE error code 0x80010105: The server threw an exception." > > The code is: > > oX=Createobject("Excel.application") > oBook= oX.Workbooks.Add() (fails on this line every time) > > Any thoughts? Barb Reinhardt, Oct 10, 2009 #2 Advertisements E F Leo Guest Sorry I did not mention the language is MS Visual FoxPro (VFP) so this suggestion will not work. The thing is that in VFP the syntax in use is equivalent to your suggested change. I now have more information from the client. The installation of MS Office 2007 was customized by their IT department. At this point I'm theorizing they did not include files needed for automation when they built that installation for general distribution (huge organization) and only 30 people use the VFP custom app and a handful of those need the automation. How does that stand up as a theory? "Barb Reinhardt" wrote: > I'd change it to > > Set oX=Createobject("Excel.applicati