SWA calendar (Solved!)

[keywestcity]

That might work for rooms, but it won't work for other shared calendars used buy the police and DOT.

Why have public folders if you can't use them, and believe you me that as soon as I say we can't do that they will say "exchange could do it".

[beaner1111]

First, I have a mixed environment, one of my sites is still on version 10, therefore resource items are not available on all servers.

Second, this worked FINE on version 11. It's a new BUG that was introduced on version 11.3

And yes, this is a bug, not a problem with the environment, not a problem with MY server or configuration. This is a BUG with your software. If the ability to create a calendar with access control in the public folders exists, it should work. Period.

We do not use this to enter schedules for resources, we use it to create departmental calendars. And now this is broken.

And finally, I can also confirm that deleting the calendar entries from the public folders resolves the issue. And I can also confirm that my CFO's going to be pissed.

[Valerion]

If this is something that changed behaviour between releases, then I suggest you take it up with Scalix Support. They would be able to assist you much faster than the community can do here.

[keywestcity]

This has been solved. This is what a scalix tech sent me and it turned out to be the problem:

To get a potential cause out of the way (other than the current java installation), there was a recent bug similar to this in which the cause was a calendar with an Ampersand in it's name. A bug was logged for this issue however it's possible you are affected as well as I noticed a Public Calendar with an & symbol in it's name.
Is it possible we can just change the name of it and see if that fixes it.
The one in question is named:
Fire Station No. 3 Conference Room (Kennedy & Flagler)

Maybe change it to:
Fire Station No. 3 Conference Room (Kennedy and Flagler)

I took the & out of the public calendar name as well as any other odd symbols like . or # and restarted tomcat. After that we were able to enter appointments again.

Thank you everyone for the help, and a special thank you to scalix support!