• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1192
  • Last Modified:

OWA 2003 - Blank Reminder pops up every 15 minutes.

I have a user with this weird problem.  She uses webmail exclusively, and when she logs in she gets a blank reminder window that pops up, with sound and everything, and she clicks dismiss or close and it goes away, then 15 minutes later it pops back up.  there is nothing in the window, no entries in her calendar or tasks.

If I log on as her to a regular outlook client connected to the exchange server, she doesnt get the reminders.  this is only webmail, and to my knowledge only with her.

http://fallert.net/reminder.jpg

thats a screenshot of the reminder.

Any ideas would be appreciated.

Thanks!
0
tfallert
Asked:
tfallert
  • 4
  • 2
1 Solution
 
SembeeCommented:
Configure Outlook to use her account as the default, then close Outlook.
Click start, run and type:

OUTLOOK.EXE /Cleanreminders

Press enter.
This will reset the reminders.

Simon.
0
 
tfallertAuthor Commented:
Okay she doesnt use Outlook as a client at all, she uses Webmail as her client.

I went to the email server, changed outlook settings to hers, then ran OUTLOOK.EXE /cleanreminders, it opened outlook, but when I went into webmail after that, it still popped up the blank reminder windows in OWA.
0
 
SembeeCommented:
I fully appreciate that the user doesn't use Outlook. However it is the primary client for Exchange and sometimes you have to use the full client to correct errors.

Was the Outlook client that you used Outlook 2003 in cached mode? If so it may not have replicated the changes back.

Otherwise I cannot think of any cause for this message to come up - especially as it doesn't come up in Outlook.

Simon.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
tfallertAuthor Commented:
No, it isnt Outlook 2003, it is outlook 2000, would that be a reason that the / command wasnt doing anything?
0
 
tfallertAuthor Commented:
Actually I ran the / command with an outlook 2003 client and it didnt help either
0
 
tfallertAuthor Commented:
Increading the points, hopefully someone will come up with an answer
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now