1. Was the issue ever reported to Microsoft's Sustained Engineering
team for Exchange 2003? via PSS incident reports, etc. If the issue
doesn't get reported, it certainly has no chance to get fixed. And no,
Microsoft cannot possibly scour the Web or newsgroups looking for user
bug reports; one has to report the bug to Microsoft.
2. Just because there is a bug does not mean it ever gets fixed. This
is a reality of the software industry that one has to accept.
3. Testing is never responsible for catching all issues. It should
catch the issues important to most users
4. "Fundamental" is completely relative.
I realize that when a bug affects a part of what you do, you consider
it fundamental because it blocks you, but you may be just the
unfortunate ten in a million who happen to find the other nine
sufferers and hence think the issue is fundamental when it is only
0.001% usage case.
I'm not trying to make light of the situation -- I'm just offering an
alternative view of the same information
//David
http://w3-4u.blogspot.com
//
charliebrown wrote:
Just an update to let you know I have found a workaround for my problem.
After doing a little bit of Google searches on this thread:
http://groups.google.nl/group/micros...14cce2859581ab
I found out that it is just another Microsoft bug.
I (also) don't understand why Microsoft does not acknowledge this bug, since
it's pretty fundamental.
How on earth did this get past beta testing???
The workaround is as following:
** ** ** ** ** ** **
Enable Cached mode and make sure you have the check box for "download public
folder favourites checked.
Then add any public folder you want to view to the public folder favourites.
You can then view them from that location.
I don't think this is a very good solution but until one is found, that
should at least get to the point of viewing them.
Hopefully an actual fix will come out soon*.
** ** ** ** ** ** **
Found the solution at:
http://groups.google.nl/group/micros...2ec6ac da0e84
* Note that it was posted around November 6'th 2003 === And still not any
hotfix available from Microsoft!
Don't think the will do so, since they already start beta testing of Office
2007 and Exchange 2007 which do not have Public Folders by default.
I understand Microsoft is "de-emphasizing" Public Folders.......... (why are
the doing this.......)
--
«·´`·.(*·.¸(`·.¸ ¸.·´)¸.·*).·´`·»
«.............. CHARLIE ..............»
«·´`·.(¸.·´(¸.·* *·.¸)`·.¸).·´`·»
charlie brown schreef in bericht
...
Hi Rich,
The NTFS permission are in line with the MAPI permissions.
--
«·´`·.(*·.¸(`·.¸ ¸.·´)¸.·*).·´`·»
«.............. CHARLIE ..............»
«·´`·.(¸.·´(¸.·* *·.¸)`·.¸).·´`·»
"Rich Matheisen [MVP]" schreef in bericht
news
charlie brown wrote:
Have also tried to make some new folders as well. Still users ware not
able
to open the e-mails within in this folder.
Have also given the users Owner rights for one night, but once the
permissions where set back to Reviewer the problems where back again.
Is there any chance you're working in Exchange mixed-mode?
When you look at the Client Permissions you're seeing what *should* be
the set of permissions. Try Ctrl+Click on that button and see what the
NTFS permissions really are.
Access control lists in Exchange public folders [330508]
Don't change the permissions from there, though.
If the permission NTFS perms you see don't agree with what you see in
the MAPI perms you have a problem. That probmlem may be that the MAPI
perms aren't in canonical order, or that there's a problem that's
preventing the conversion of the mailbox names to SIDs.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address
Or to these, either: