Free Busy Feature -- hash marks?

[Mel]

Hi,

When a user tries to schedule a meeting using the Outlook Calendar Meeting
Request option, scheduled users are not populating their free busy
information.

"Free Busy Feature of Outlook Shows Hash Marks Instead of Calendar
Information" as reported by one specific user.

Is this caused by Outlook not recognizing the name with which you typed in
the schedule field? If not, what might cause this?

thx,

Mel

 

[Nikki]

There are a few things that can cause this to occur.
- The calendar/inbox has not been initiated. In other words the
active directory account has never been opened in a profile.
- The delivery point of the client is not set to the exchange server.
If the delivery of mail is set to a PST then the free/busy is not
published.
- Exchange Server is not publishing free/busy. May need to fix
the free/busy at the server level. (See Exchange list for info).
- Client free/busy is corrupt. (See info below)

You may want to try the following at the client level.Try opening
Outlook using a switch:

The command line looks like:

"C:\Program Files\Microsoft Office\Office11\Outlook.exe " /CleanReminders

Note: Paths that include spaces between words must be enclosed in quotation
marks (") and are case sensitive.

OL2003: Command-Line Switches by Microsoft Office Assistance:
http://office.microsoft.com/en-gb/assistance/HP010031101033.aspx

Below are the switches that I suggest you try:

a.. /CleanReminders - Cleans and regenerates reminders.
b. /CleanFreeBusy - Cleans and regenerates free/busy information.

Please write back and let me know if this helped you.

Nikki Peterson

 

[Jim]

I will give them a try today. I will also check the server side as you
suggest. I will report back my results.

thx,

Jim

 

[Jim]

Your client suggestion fixed the issue...in addition we took the client out
of cache mode before running the Outlook cleanup.

thx,

Jim

 

[Nikki]

Glad to hear. =)

Your client suggestion fixed the issue...in addition we took the client
out
of cache mode before running the Outlook cleanup.

thx,

Jim