Object Creation worked... Now it doesn't...

[BinaryBrother]

I posted a thread over here...

#660470

But I hadn't realized just how dead the COM/Obj forums were compared to the General Help and Support... I never received any help.

The fact of the matter is...

I am 110% sure this code WAS working on "Windows Server 2008"

$oMessenger = ObjCreate("Messenger.UIAutomation.1")
If Not IsObj($oMessenger) Then
    MsgBox(0,"Debug","Objection Creation Fail")
    Exit
Else
    $oMessenger.AddContact (0,"Test@test.com")
EndIf

Now this code does not work, with no changes being made to WLM or MsgPlus... Any ideas?

@ExtendedInfo:

Number is: 80004005
Windescription is: Unspecified Error

I'm racking my brains on this... What was tampered with? Why did the Object just quit working? Why would an object just quit working?

Edited April 8, 2009 by BinaryBrother

[Skruge]

I posted a thread over here...

#660470

But I hadn't realized just how dead the COM/Obj forums were compared to the General Help and Support... I never received any help.

That forum is for using AutoItX with other languages, so that's probably why you didn't get much help.

I don't have a 2K8 box to test with, so these are just a few thoughts:

Check the registry on a working machine to see which exe/dll/ocx constitute the object. Unregister/re-register it.

I read somewhere that you may also need Windows Messenger (non-live) installed.

Maybe another vulnerability was found and MS broke the object with a hotfix. If so, you may find more info at their site.

[BinaryBrother]

1.) Unregistered, registered almost all MSN related DLL's with no avail.

2.) Window Live Messenger works perfect on 2 separate Win7 machines, and was working on the "Windows Server 2008".

3.) I have Automatic Updates off...

Thanks for your suggestions! I really do appreciate everything.

This isn't the only issue with WLM Objects... The above code doesn't work at-all with Windows XP...

[Authenticity]

Maybe this is the object you want?

Dim $oObj = ObjCreate('Messenger.MessengerApp')
$oObj.LaunchLogonUI

$oObj = 0

Object Methods:

Property Application As Object   ###read-only###
Sub AutoLogon()
Property CachedPassword(bstrUser As String, bstrPassword As String, pService As IMsgrService) As Boolean
Property FirstTimeCredentials(bstrUser As String, bstrPassword As String, pService As IMsgrService) As Long
Property FullName As String   ###read-only###
Property Height As Long
Property HWND As Long   ###read-only###
Property IMWindows As IMessengerIMWindows   ###read-only###
Sub LaunchAddContactUI(bstrEMail As String)
Sub LaunchAudioTuningWizard(hwndParent As Long)
Sub LaunchFindContactUI(bstrFirstName As String, bstrLastName As String, [vbstrCity], [vbstrState], [vbstrCountry])
Function LaunchIMUI(vUser) As IMessengerIMWindow
Sub LaunchLogonUI()
Sub LaunchOptionsUI(MOPTDLGPAGE As MOPTDLGPAGE)
Sub LaunchPhoneUI(vUser, ePhoneNumber As MUSERPROPERTY)
Property Left As Long
Property Name As String   ###read-only###
Property Parent As Object   ###read-only###
Property Path As String   ###read-only###
Sub Quit()
Sub RequestURLPost(muType As MURLTYPE, [vbstrAdditionalInfo])
Property StatusBar As Boolean
Property StatusText As String
Property TaskbarIcon As Boolean
Property ToolBar As Boolean
Property Top As Long
Property Visible As Boolean
Property Width As Long

[ResNullius]

3.) I have Automatic Updates off...

Sure it doesn't have anything to do with this http://www.microsoft.com/technet/security/...n/MS08-050.mspx ? Edited April 9, 2009 by ResNullius

[BinaryBrother]

@ResNullius

Non-Affected Software

Operating System

Windows Vista and Windows Vista Service Pack 1

Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1

Windows Server 2008 for 32-bit Systems

Windows Server 2008 for x64-based Systems

Windows Server 2008 for Itanium-based Systems

Not to mention.

Published: August 12, 2008

I am absolutely sure this is not the cause, That hotfix is not listed under my updates, and like I said, I've had updates off since I purchased the server, it did of course come stock with Updates enabled, which managed to slide a few in before I turned it off...

I tested this MSN Script months after Updates were disable, and have been disabled during/before/after testing.

@Authenticity

I'll take a look at that.. but as I've stated, "Messenger.UIAutomation.1" Worked perfect before...