UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> -2147417856 - Automation Error System Call Failed., Access 2003    
 
   
abnormsol
post Oct 24 2012, 09:21 AM
Post#1



Posts: 216
Joined: 3-March 05



Anyone ever see this error before?
Thanks,
Andy
Go to the top of the page
 
CyberCow
post Oct 24 2012, 09:35 AM
Post#2


UdderAccess Admin + UA Ruler
Posts: 19,557
Joined: 27-April 02
From: Upper MI


In relation to . . . . what? Please provide more details on what brought the error message up. What code was executing? (Show us the code)
Is this in relation to a form, report, module, query? iconfused.gif
We just need more details. hat_tip.gif
Go to the top of the page
 
abnormsol
post Oct 24 2012, 09:50 AM
Post#3



Posts: 216
Joined: 3-March 05



I have no idea what code exactly triggered it at this point I am sorting through logs.
It was the first error in my logs.
Two things going on:
One access database opening others. Email automation occurring. Access to Outlook.
This occurs on a server 2003 using schedule server.
Another error message message that appears (though not logged) is:
Microsoft Visual Basic
'-2147467259 (80004005)':
A dialog box is open. Close it and try again.
So:
-2147417856 - Automation Error System Call Failed.
and
'-2147467259 (80004005)': A dialog box is open. Close it and try again.
Go to the top of the page
 
CyberCow
post Oct 24 2012, 10:34 AM
Post#4


UdderAccess Admin + UA Ruler
Posts: 19,557
Joined: 27-April 02
From: Upper MI


Without an explicit point of error source, our hands are rather tied. Do you have any Error Handling in your code? Can you reproduce the error and instead of just clicking on the error message dialog box, hit "Ctrl-Break" - this will force the VBA editor open to the line delivering the error message. Then you can get an idea of from where the error is provoked.
Is this a regular MDB or an MDE? What OS are you using? How many users? What is the environment description?
You may want to consider injecting some error handling into your code to pinpoint errors when they do crop up.
Go to the top of the page
 
abnormsol
post Oct 24 2012, 12:16 PM
Post#5



Posts: 216
Joined: 3-March 05



I do have error handing code throughout.
quot;-2147417856 - Automation Error System Call Failed" is from the error handling log.
'-2147467259 (80004005)': A dialog box is open. Close it and try again was on the screen of the windows server 2003 computer. But not in the log.
The main database was able to open ALL of the sub databases and execute the code there in.
All of the processes worked fine and produced results except for when the process called to email. The email crashed (gracefully) every time and produced the following error:
2147467259 - A dialog box is open. Close it and try again. - this was logged and code continued.
All of my lead procedures have error handling code as do most other procedures. That logs the error rather than halts the execution.
The code that generated the logged errors:
CODE
Public Function SendEmail(strTo As String, _
                            Optional strCC As String = "", _
                            Optional strBCC As String = "", _
                            Optional strSubject As String = "", _
                            Optional strMessage As String = "", _
                            Optional strTemplate As String = "", _
                            Optional strAttachment As String = "")
    Const C_PROC_NAME = "SendEmail"
    On Error GoTo PROCEDURE_ERROR
    Dim appOutlook As Object
    Dim emlMessage As Object
    Dim objAttachments As Object
    
    Set appOutlook = CreateObject("Outlook.Application")
              
    If strTemplate = "" Then
        Set emlMessage = appOutlook.CreateItem(0)
        emlMessage.Body = IIf(strMessage = "", "", strMessage)
    Else
        Set emlMessage = appOutlook.CreateItemFromTemplate(strTemplate)
    End If
    
    emlMessage.TO = IIf(strTo = "", "", strTo)
    emlMessage.CC = IIf(strCC = "", "", strCC)
    emlMessage.Subject = IIf(strSubject = "", "", strSubject)
            
    Set objAttachments = emlMessage.Attachments
    If strAttachment <> "" Then
        objAttachments.Add strAttachment
    End If
              
    emlMessage.Display
              
    emlMessage.Save
    AppActivate emlMessage
    SendKeys ("%s")
    
    Set objAttachments = Nothing
    Set emlMessage = Nothing
    Set appOutlook = Nothing
    GoTo PROCEDURE_Exit


is it possible that:
'-2147467259 (80004005)': A dialog box is open. Close it and try again was on the screen of the windows server 2003 computer. But not in the log.
is from Outlook?
Have you ever seen these errors before?
Thanks,
Andy
Go to the top of the page
 
CyberCow
post Oct 24 2012, 12:34 PM
Post#6


UdderAccess Admin + UA Ruler
Posts: 19,557
Joined: 27-April 02
From: Upper MI


If you add line numbers to your code and include the erl variable in your output message, it will tell on what specific line the code failed.
lso, can you show the rest of the function as well?
And, no, I've not seen that specific error before. Next time it pops up, check your task bar and/or Task Manager to see what might be up, but possibly hidden behind another window.
Go to the top of the page
 
abnormsol
post Oct 25 2012, 07:57 PM
Post#7



Posts: 216
Joined: 3-March 05



Added line numbers and never saw the error since...
go knows maybe over the next few days...
Thanks for your help and patience.
Andy
Go to the top of the page
 
CyberCow
post Oct 30 2012, 12:28 PM
Post#8


UdderAccess Admin + UA Ruler
Posts: 19,557
Joined: 27-April 02
From: Upper MI


good luck with your project(s)!
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    20th October 2018 - 11:17 PM