401 Unauthorized error

hi i just started using growl and this plugin and am having problems configuring the setup. i just checked and i am infact running the latest version just released yesterday of OWA monitor. Initially when i configured the setup i was getting one error, which then for some reason switched to another error, and today morning when i tried again the error had changed.
The initital error i got was: "
the url property on exchangeservice object must be set"


After getting this error many many times for some reason the error changed to "
Error >
is an unexpected token"


I gave up on this yesterday after continually getting error #2, and today when trying again, i get the error "
error: request failed. the remote server returned an error: (401) Unauthroized"


I am not sure wahts going on. my server i beleiove is the normal URL: exchange.domain.com. i tried manually entering the URL aswell making sure its https etc but same error. when i right click on the icon nad tell it to go to "
Open OWA"
it correctly goes to the website to login so i am not sure hwy this is not working.

any help would be appreciated.
thanks

Hi,

OK, let's take this a stage at a time...

1. Which version of Exchange are you running?
2. Please email me a screenshot of your main screen.

If that doesn't give me any clues then would it be possible to allow me temporary access to your an email account on your server and I can test from here?

Let me know.

OK, the first error can be reproduced by setting the Override URL in Advanced and then having a blank URL field.

Please can you ensure both Advanced options are OFF and the 'On Domain' is unchecked. Double-check your server address, user &
pass, Click Stop then Start and let me know what happens now.

If it still fails, please send me a screenshot of your settings.

Thanks.

Hi, i checked the buttons in advanced both were unchecked as well as was the third checkbox you mentioned. it is very wierd but yet again i pressed stop and then start again and for some reason it started working. The only thing i can think different this time was i left domain blank, which im sure i did previously as well but didnt work last time. anyway it started working fine ive been doing some testing. if i get problems again ill give you screenshots and/or account info to login and test out.

OK, zank, keep me posted.

It's possible I have left a bug or 2 in this release as I was kind of rushing it out to help a couple of other users.

Glad it's working ATM.

PS, make sure you SAVE your config now that it's working

thanks will do. another quick question...when i get growl notifications on my ipohone through prowl, currently the notification says"
OWA tray monitor: new messsage from...."
wouold it be psosible to add option to customize this at some point. i only use growl/prowl for push email from my various accounts, (outlook, OWA, gmail), and i'd like to have these all act consistently. Instead of receiving a message that says OWA Tray monitor...id like to be able to atleast customize waht the notification says, i.e. my company domain name, rather than "
OWA tray monitor"
, and best case scenario be able to customize the "
new messsage from"
part to just say "
FirstName LastName"
, and maybe customize how to show them, i.e. From, subject, body, or Subject, from, body, ... as it stands owa, outlook and gmail plugins all use their own style of notification would be great to be able to customize this. im loving owa tray monitor so far though great work.

Getting the message Body through this interface, believe it or not, is still a big deal. I put a good few hours into trying to get this to work before Christmas and gave up.

I'll revisit it though as the new versions roll-out from Microsoft.

Keep the suggestions coming though

I also received the same 401: unauthorised error but found that if I click "
Start"
and let the program minimize it works anyway.
I unticked both advanced options and unticked the domain option.

I'm using Windows Vista SP2 without Growl or Snarl.

I'll sit on this in lieu of further evidence of issues being posted