benjbong

Sorry for the delay, the errors I was getting were @error = 1 and @extended = -2147352567 which were the generic COM error codes

For anybody else who stumbles across this, the problem was indeed related to Symantec Endpoint Protection 12.1, see this thread below: The problem is with the SONAR engine scan while UPX compression was enabled while compiling the exe. The fix for me was: 1. In Aut2Exe go to Compression > Uncheck "UPX Compress .exe Stub" 2. Check the box for x64 - The first time I tried I didn't check this, and it didn't fix it until I checked it the 2nd time 3. Create an application exception in SEPM and push to your clients if you're in a domain environment.

I was also having this problem with SEP 12.1 and AutoIT 3.3.6.1 What fixed it for me was: In Aut2Exe v3 go to Compression > Uncheck UPX Compress .exe Stub Check the box for x64 - The first time I tried without checking x64 it didn't work. Started working after that (all my machines are 64 bit) Set an application exception for the .exe in SEPM Compiled scripts that were taking for some people 15 minutes to load are loading in a couple seconds now.

This was the call to _OL_FolderAccess I was making before Global $cal = _OL_FolderAccess($oOL, "Secondary Sourcing CalendarCalendar", $olFolderCalendar) It would fail unless I had full access permissions on the mailbox AND it was mapped as a mailbox in outlook. If i had full access permissions and disabled the automapping in outlook it would also fail. I don't have visual studio so I can't look at what the COM object looks like for either instance to be able to say what is different.

It now looks like it hasn't fully fixed the problem. The first couple of times I tried opening it It was quicker but now it still takes about 15 seconds for it to open. Are there any other things I could try?

Yeah, mine doesn't account for sub folders, folder type, or other users but when I fed the same parameters to _OL_FolderAccess I was getting the generic COM failure message instead of the expected outcome. It's possible I wasn't passing it correctly but I thought I would mention it to you.

That seemed to do it, thanks. Still takes a couple seconds but it's much faster now. I'll set an exception in the AV setting to it before I roll it out company wide.

I have a script using GUI that takes a long time to load after it's been built. If I run the script from the script editor it opens almost instantly. If I build the script then run the exe, it takes up to 30 seconds to load. The file itself isn't very big @483kb. Here is the list of includes: #include <GUIConstantsEx.au3> #include <GUIComboBox.au3> #include <StaticConstants.au3> #include <EditConstants.au3> #include <OutlookEX.au3> #include <Date.au3> #include <WindowsConstants.au3> #include <GUIComboBox.au3> #include <mysqllite.au3> #include <DateTimeConstants.au3> #include <ad.au3> I tried setting a splash screen to at least show a loading window when the tool is coming up, but it just flashes instantly then loads the screen after waiting to load. So it appears as though the issue is there is a delay loading the file into memory and starting the script, not the script running slowly itself. I've also tried this on other computers, same result though the load time varies. Any thoughts on this?

I think there may be an issue with your _OL_FolderAccess function, I removed all permissions from the mailbox except the ability to create items in the calendar folder, and created the object manually using the code below instead of using the FolderAccess function: $nameSpace = $oOL.GetNamespace("MAPI") $calName = $nameSpace.CreateRecipient("Secondary Sourcing Calendar") $calName.Resolve $calFolder = $nameSpace.GetSharedDefaultFolder($calName, $olFolderCalendar) And this worked without incident. I used the link here to get some information on the procedure in case it helps anybody else http://msdn.microsoft.com/en-us/library/office/ff869575.aspx I found this was not an issue with the autoit script. On the exchange 2010 console there are two settings in the properties of the resource mailbox under Properties > Resource Information that need to be adjusted. "Delete the subject" and "Add the organizer's name to the subject" should be unchecked.

Hi water, I'm trying to figure out what permissions I need to set on another mailbox to be able to create items in their calendar. Currently the only way I can successfully create an item in another user's mailbox is if my account has full access permission on the other mailbox. The script i'm using is below: Global $cal = _OL_FolderAccess($oOL, "Secondary Sourcing CalendarCalendar", $olFolderCalendar) ; Create an appointment and set some properties $oItem = _OL_ItemCreate($oOL, $olAppointmentItem, $cal[1], "", _ "Subject=" & GUICtrlRead($subject), "Start=" & GUICtrlRead($startDate) & " " & GUICtrlRead($startTime) & ":00", _ "Duration=" & $duration, "Location=" & GUICtrlRead($location), _ "RequiredAttendees=" & $emailAddr, "MeetingStatus=1", "Body=" & GUICtrlRead($notes)) _OL_ItemRecipientAdd($oOL, $oItem, Default, $olResource, $oLoc) _OL_ItemSend($oOL, $oItem) ; Close connection to Outlook _OL_Close($oOL) The mailbox in question is the "Secondary Sourcing Calendar" mailbox. I tried adding the create item permission on the calendar as well as a few other permissions, and nothing works unless i have full access permission to the mailbox. Also, in the _OL_ItemRecipientAdd line if the added user is a specific mailbox it will get the invitation, but it displays the subject line as "Secondary Sourcing Calendar" (which is the mailbox sending the invitation) instead of the subject defined in the $oItem object. It only does that for one mailbox, any of the others work as expected. Any thoughts? UDF version is 0.7.1.1

That did the trick, i didn't know _OL_FolderAccess returned an array. Thanks for the help! For anyone else Display NameFolder is the correct syntax

@error = 1, @extended = 1 after itemcreate

The results of the debug window are: COM Error Encountered in caltest.au3 OutlookEx UDF version = 0.7.1.1 @AutoItVersion = 3.3.6.1 @AutoItX64 = 0 @Compiled = 0 @OSArch = X64 @OSVersion = WIN_7 Scriptline = 3466 NumberHex = 80020009 Number = -2147352567 WinDescription = Description = Could not open the item. Try again. Source = Microsoft Outlook HelpFile = HelpContext = 0 LastDllError = 0 Yes I can manually create items in that mailbox's calendar. how does the mailbox name need to be formatted? The "firstname namefolder" is very vague. For example if my name is joe cool and my email is jcool@domain.com would it be: joe coolcalendar jcool@domain.localcalendar > domain account name jcool@domain.comcalendar > email address jcoolcalendar > domain username any of these permutations don't work. If I leave the default as *Calendar it creates the item in my calendar just fine. If i try to manually set my own name in any of the combinations above it doesn't work - I think the problem is with the formatting of the name in referencing the mailbox and folder

I was able to fix this by commenting out the error message box portion of the inetsmtpmailcom.au3 include. The lines are: #cs If @error Then MsgBox(0, "Error sending message", "Error code:" & @error & " Description:" & $rc) EndIf #ce Obviously you would want to make sure everything is working before removing your error checking , since everything was working properly for me I didn't see it as a problem.

I'm having an issue with using the _ol_createitem UDF to create the item in another mailbox. If I leave the folder as the default it works just fine, but I want all items created to be created in this other mailbox by default. The script is: ; Open the connection to Outlook Global $oOL = _OL_Open() ;Open the calendar folder for the secondaries sourcing calendar mailbox Global $cal = _OL_FolderAccess($oOL, "Secondary Sourcing CalendarCalendar", $olFolderCalendar) msgbox(0,"",@error & " " & @extended) ; Create an appointment $oItem = _OL_ItemCreate($oOL, $olAppointmentItem, $cal, "", _ "Subject=" & GUICtrlRead($subject), "Start=" & GUICtrlRead($startDate), _ "Duration=" & GUICtrlRead($duration) & '"', "Location=" & GUICtrlRead($location), _ "RequiredAttendees=user@mail.com", "MeetingStatus=1", "Body=" & GUICtrlRead($notes)) _OL_ItemSend($oOL, $oItem) msgbox(0,"",@error & " " & @extended) ; Close connection to Outlook _OL_Close($oOL) But it doesn't work. The first message box after running the folder access UDF I get @error = 0, @extended = 0. After the item is created and sent I get @error = 1 and @extended = -2147352567 Why is there no problem accessing the folder but then creating the item has problems? I set the calendar in question to allow anonymous users to create items in the calendar, since there doesn't seem to be a way to specify which user account you are using to connect. Also the documentation just says "check @extended for _ol_folderaccess", but gives no further information on how to learn what the @extended code means. Any help?