@65 is normally forms not registered.

If it is just one user on an exchange server not being able to access item via OWA then your config should be ok.

I would look to see if there is anything different w/ this users smtp addresses.

Also, you could try moving the user to a different Information Store to see if there is something with it that way.

Thanks Tony. I moved him to another store on the same server and he can now see his KVS icons and archived mail. Is there anything I should look for on his original store?

Can anyone on that store see the icons and view archived items in OWA?

You can look at your owa set up log and see if there are any errors registering the forms for that store.

regards,

OK, this looks like an issue with the mailstore.

I have just installed SP3 and run the back-end configuration (OWA and RPC). A portion of the log file is given below:

09/10/2006 12:36:12 : Info : ConfigureInformationStores : Configuring mailbox information store: MEGS1BE02 SG1-NGN
09/10/2006 12:36:12 : Debug : ConfigureInformationStores : Mailbox information store dn: CN=MEGS1BE02 SG1-NGN,CN=MEGS1BE02 - Storage Group ONE,CN=InformationStore,CN=MEGS1BE02,CN=Servers,CN=Infrastructure,CN=Administrative Groups,CN=MS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=groupservices,DC=co,DC=uk
09/10/2006 12:36:12 : Debug : ConfigureMailboxInfoStore : Registering for info store: CN=MEGS1BE02 SG1-NGN,CN=MEGS1BE02 - Storage Group ONE,CN=InformationStore,CN=MEGS1BE02,CN=Servers,CN=Infrastructure,CN=Administrative Groups,CN=MS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=groupservices,DC=co,DC=uk
09/10/2006 12:36:12 : Debug : ConfigureMailboxInfoStore : System mailbox LDAP query: ;(&(objectCategory=person)(objectClass=user)(displayName=SystemMailbox{*)(homeMDB=CN=MEGS1BE02 SG1-NGN,CN=MEGS1BE02 - Storage Group ONE,CN=InformationStore,CN=MEGS1BE02,CN=Servers,CN=Infrastructure,CN=Administrative Groups,CN=MS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=groupservices,DC=co,DC=uk));displayName,proxyAddresses;subTree
09/10/2006 12:36:12 : Debug : ConfigureMailboxInfoStore : Found 0 matching system mailbox(es)

I moved a user to the NGN Mailstore, and they have no KVS icons in OWA!
I ren the script to remove the virtual directories and forms, then re-ran the back-end configuration but the result was the same. Does anyone know what I should look for next?

Thanks

I have seen this previously where the system mailboxes for a store were deleted. There is a MS kb floating around on how to recreate a system MB, but the easiest thing might be to create a new mailstore, rerun the config, and move all your users out of the old one and into the new one. If you have a bunch of users or don't want to do that you could contact MS to see if they can help you recreate the system mb. I don't have it handy or I would give it to you.

I have created a new mailstore, ran the backend configuration (no errors reported), and moved a mailbox containing archived mail to this store. The user cannot access archived email and there are no vault icons in OWA. Further investigation has shown that vaulted emails and icons are not available for any mailstore that was added after the initial installation of KVS!
Has anyone else had this problem?

TIA
Derrick

That is a curious one! Have you per chanced opened a support case yet? If not you will want to do so.

It looks like we've had exactly the same thing.  We created new storage groups and stores and it seems that after moving some users to them, they can no longer see the EV icons via OWA.

Did you get to the bottom of this?  Is it just a case of running the config script again?

We're on EV 2007 SP3 with Exchange 2003 SP2

Would be good to find out more about this one..

Jason

Yes, if you add Storage Groups / Stores, you have to run the config script again.

Cheers
Michel

thanks for the quick reply, I assume that is literally all?  No need to run the cscript etc as well?

Also, does it need to be run on all the front-end and back-end servers or back-end only?

No need for cscript, correct. Just read the logfile and see if it was successful.

This is backend-only.

Thanks very much, I'll give that a go!