OLE Error
Publicado: Vie Sep 28, 2007 5:32 am
Howdy
I have a wierd issue. I'm not really expecting anyone to have a simple
answer. I'm not really sure wether's it a bug in my code, the OLE32 xh
interface or Outlook 2003 OLE interface
I have a little app that loops through a list of public folders in outlook
that hold appointments (they are timesheet entries)
This is basically 3 outlook calendars
We track our time in them all day every day . This little app connects to
Outlook and basically loops through each calendar with an inner loop that
loops through the appointments in each
If I run it for a day it works fine, if I run it for a fews days sometimes
it works fine. if I try and run it for a large date range the OLE return an
E_FAIL error.
The weird bit is that it fails trying to retrieve the category of the
apppointment. What makes it even weirder is when I then go to outlook and
try and look at the appointment it fails on, I cannot access the appointment
or any further on in that Calendar. If I restart Outlook all is well again,
I get a trace, here it is
**************************** Error log file ********************************
Date: 28/09/07
Time: 11:36:02
Available Memory: 324360
Current Area: 1
---------------------------- Compiler
Information -----------------------------
Xailer Version: Xailer 1.4.0 Version 1.4
Compiler: xHarbour build 0.99.61 Intl. (SimpLex) PCode Version: 7
C/C++ Compiler: Borland C++ 5.5.1
Windows Platform: Windows XP Professional 5.01.2600 Service Pack 2
--------------------- Internal Error Handling
Information ---------------------
Subsystem Call:
Outlook.Application:GETNAMESPACE:GETDEFAULTFOLDER:FOLDERS:IT EM:ITEMS:FINDNEXT
System Code: 16389
Default Status: .F.
Description: E_FAIL
Operation: CATEGORIES
Arguments:
Involved File:
Dos Error Code: 0
Trace Through:
TOLEAUTO:CATEGORIES (0)
OUTLOOK:CALENDARLOOP (124)
OUTLOOKSUMMARYFRM:QUERYOUTLOOK (67)
TBUTTON:ONCLICK (0)
TBUTTON:CLICK (99)
(b)XCONTROL:XCONTROL (140)
TBUTTON:COMMAND (0)
TSCROLLINGWINCONTROL:WMCOMMAND (253)
OUTLOOKSUMMARYFRM:WMCOMMAND (884)
RUNFORM (0)
TAPPLICATION:RUN (209)
MAIN (15)
**************************** Error log file ********************************
The thing is, the line it fails on, I call every time I loop. The like above
this line pulls the date out of the appointment and it doesn;t fail, this
means the appointment object should be ok.
If I restart Outlook and run the app for just the day I had the issue with
it will run fine and not crash
I don't know much about OLE so I wonder am I overloading OLE maybe,do I need
slow the app down so it doesn;t flood the OLE? Is there memory limits I need
to be aware of
Maybe Exchange isn't keeping up, that may be the cause
Something about the trace
OUTLOOK:CALENDARLOOP (124) is where I request the category
Subsystem Call:
Outlook.Application:GETNAMESPACE:GETDEFAULTFOLDER:FOLDERS:IT EM:ITEMS:FINDNEXT
This was at least 3 OLE calls back, basically the end of the previous
appointment, why is it in the trace
Any idea, however remote would be appreaited
Nick
I have a wierd issue. I'm not really expecting anyone to have a simple
answer. I'm not really sure wether's it a bug in my code, the OLE32 xh
interface or Outlook 2003 OLE interface
I have a little app that loops through a list of public folders in outlook
that hold appointments (they are timesheet entries)
This is basically 3 outlook calendars
We track our time in them all day every day . This little app connects to
Outlook and basically loops through each calendar with an inner loop that
loops through the appointments in each
If I run it for a day it works fine, if I run it for a fews days sometimes
it works fine. if I try and run it for a large date range the OLE return an
E_FAIL error.
The weird bit is that it fails trying to retrieve the category of the
apppointment. What makes it even weirder is when I then go to outlook and
try and look at the appointment it fails on, I cannot access the appointment
or any further on in that Calendar. If I restart Outlook all is well again,
I get a trace, here it is
**************************** Error log file ********************************
Date: 28/09/07
Time: 11:36:02
Available Memory: 324360
Current Area: 1
---------------------------- Compiler
Information -----------------------------
Xailer Version: Xailer 1.4.0 Version 1.4
Compiler: xHarbour build 0.99.61 Intl. (SimpLex) PCode Version: 7
C/C++ Compiler: Borland C++ 5.5.1
Windows Platform: Windows XP Professional 5.01.2600 Service Pack 2
--------------------- Internal Error Handling
Information ---------------------
Subsystem Call:
Outlook.Application:GETNAMESPACE:GETDEFAULTFOLDER:FOLDERS:IT EM:ITEMS:FINDNEXT
System Code: 16389
Default Status: .F.
Description: E_FAIL
Operation: CATEGORIES
Arguments:
Involved File:
Dos Error Code: 0
Trace Through:
TOLEAUTO:CATEGORIES (0)
OUTLOOK:CALENDARLOOP (124)
OUTLOOKSUMMARYFRM:QUERYOUTLOOK (67)
TBUTTON:ONCLICK (0)
TBUTTON:CLICK (99)
(b)XCONTROL:XCONTROL (140)
TBUTTON:COMMAND (0)
TSCROLLINGWINCONTROL:WMCOMMAND (253)
OUTLOOKSUMMARYFRM:WMCOMMAND (884)
RUNFORM (0)
TAPPLICATION:RUN (209)
MAIN (15)
**************************** Error log file ********************************
The thing is, the line it fails on, I call every time I loop. The like above
this line pulls the date out of the appointment and it doesn;t fail, this
means the appointment object should be ok.
If I restart Outlook and run the app for just the day I had the issue with
it will run fine and not crash
I don't know much about OLE so I wonder am I overloading OLE maybe,do I need
slow the app down so it doesn;t flood the OLE? Is there memory limits I need
to be aware of
Maybe Exchange isn't keeping up, that may be the cause
Something about the trace
OUTLOOK:CALENDARLOOP (124) is where I request the category
Subsystem Call:
Outlook.Application:GETNAMESPACE:GETDEFAULTFOLDER:FOLDERS:IT EM:ITEMS:FINDNEXT
This was at least 3 OLE calls back, basically the end of the previous
appointment, why is it in the trace
Any idea, however remote would be appreaited
Nick
