I am using this reference: MSDN
Basically, the issue is that SBS2008 Event Log does not give the same amount of information that Windows XP did, so the users are being forced to look in the text activity log. Am I forced to loop through the log for new items, or can I actually catch errors as they come?
My ultimate goal is to send an email report with the erroneous fax information (destination#, error reason, code, body or attachment).
So essentially I need to figure out how to catch fax errors as they arise, by listening (this will be a VB.NET console app), and then I can take it from there.
Private Sub GetOutgoingArchiveMessages()
Dim objFaxServer As New FAXCOMEXLib.FaxServer
Dim vMessages As FAXCOMEXLib.FaxOutgoingMessageIterator
objFaxServer.Connect("") ' Add server name '
vMessages = objFaxServer.Folders.OutgoingArchive.GetMessages
If Not vMessages.AtEOF Then
With vMessages
vMessages.MoveFirst()
Do While Not vMessages.AtEOF
' Here get all the properties of the message '
' vMessages.Message.DocumentName
' vMessages.Message.Id
' vMessages.Message.Transmissionend
' vMessages.Message.Transmissionend
' vMessages.Message.Delete
vMessages.MoveNext()
Loop
End With
End If
End Sub
This is what I am using to get the outgoing archive messages, but I either need to reliably get an error when it happens there, or get one on demand. I would much rather just poll the fax service for the information if I can.
Thanks a lot.

New Topic/Question
Reply



MultiQuote



|