Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Archive Explorer not listing Public Folders

Created: 03 Oct 2012 • Updated: 23 Oct 2012 | 25 comments
This issue has been solved. See solution.

Hello,

We had a few Public Folders missing from Archive Explorer. Symantec Support went in and did the following to fix it and after that no Public Folders are being displayed for any users in AE:

1. Using ArchiveFolderFix.exe tool
2. Using SQL Script to set ParentFolderRootIdentity of Top of Information Store to NULL.

If I add one user manually to the permissions tab on the Public Folders archive, that one user can see the Public Folders in AE. Symantec Support has spent many weeks trying to figure this out, but so far no progress. The permissions browser looks good as far as I can see, but the top level forlder named \ does not have any permissions listed.

Please advise if you have any clues how to solve this. Thanks.

Discussion Filed Under:

Comments 25 CommentsJump to latest comment

Jeff Shotton's picture

This could either be a mangled archive structure,iis problem or a permissions issue, but what you are saying above is that the permissions for \ are missing.

Have you (or anyone) checked to see what is being synched over when public folder archiving is running?

Can you post a dtrace of the PublicFolderTask process whilst doing a run now 'shortcut processing' (or even archiving if you prefer)

You *can* (if you know what you are doing) fudge in the permissions to a folder, but if the data is being synched over then it will be wiped out next synch anyway.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

Rob.Wilcox's picture

So I just quickly set up public folder archiving to archive a folder structure :

\B1

   \s1

   \s2

   \s3

I have an archived item and a normal item in B1, same in S1..  and nothing in the other two folders.

In PermissionBrowser I see PFArchive (the name of my archive), and when I select it the permissions pane (on the right hand side) shows no permissions.  At the lower left hand side, I see the subfolders of the archive:

When I click on either of the folders, then the right hand side updates to show the permissions on the archive.

These permissions are a mapping from the permissions that would see against the folders in Outlook.  So in Outlook I see:

So my question is...  what do you see ? :)

nils35's picture

Hi,

Thanks for your reply.

Do you know what permissions should look like at \ ?

Support has been gathering dtrace logs, but they don't reveal anything useful as far as I understand. I could post the dtrace log here, but it gets very big quickly during the task running so I don't know how to present it here.

I don't understand what you mean by "fudge in the permissions to a folder". Please clarify if this is something I might be able to do.

Best regards,

Nils

nils35's picture

Rob,

Thanks for your reply.

I can see this:

Selecting "Public Folder Vault Store" shows no permissions, selecting "\" shows now permissions, selecting "BGO" and other folder below "\" shows the same permissions as in Outlook client settings, for instance:

Header:
      AceType: ACCESS_ALLOWED_ACE_TYPE
      AceFlags:
    Mask: 0xB
      DV_DS_READ_FOLDER
      DV_DS_ADD_ITEM
      DV_DS_READ_ITEM
    Sid:
      SID: S-1-5-11
      Name: Authenticated Users
      DomainName: NT AUTHORITY

    Header:
      AceType: ACCESS_ALLOWED_ACE_TYPE
      AceFlags:
    Mask: 0x2
      DV_DS_ADD_ITEM
    Sid:
      SID: S-1-5-7
      Name: ANONYMOUS LOGON
      DomainName: NT AUTHORITY

Kind regards,

Nils

Rob.Wilcox's picture

So you have targetted the 'top' level public folder for archiving, and that's giving you the \ folder?

nils35's picture

No, I have targeted like this. I did some censoring there, but they are all subfolders below \ so I dont know why \ is in the permissions browser.

Jeff Shotton's picture

hmmmm SO a null record has been inserted for you!

The problem is that your public folders do NOT have a TOP OF INFORMATION STORE

but im guessing someone in support inserted one for you

and it doesnt have any perms because it doesnt exist to sync!

All your public folders are therefore chained together when they should be showing as separate entities.

I'd get back on the phone.....

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

SOLUTION
TonySterling's picture

I second what Jeff said, get back on the phone with support and insist that the case is escalated.

nils35's picture

Thanks! I will let Support know what you are saying and hopefully they know how to fix it...

nils35's picture

By the way, here is what it looks like in Exchange:

This is what it looks like in Archive Explorer when giving a user explicit permissions to the PF archive:

Rob.Wilcox's picture

I think your archive folder structure is all a bit ... wrong now.

ManishN's picture

Nil,

I agree with all that something went wrong with the ArchiveFolderview table, so if you have a backup before the changes made then you could try restoring this table (you may need to take your SQL DBA's help in doing this keeping in mind that no new data is lost from that table)

Once you perform the above activity, you will be back to your previous issue (ArchiveFolder Listing Issue)  & permission issue will be resolved.

I think you may require to take a second look on the Archivefolderview table carefully and fix it accordingly using the following article :

http://www.symantec.com/docs/TECH52763   --- Archive Explorer displays incorrect or incomplete folder listing in the folder list and item list.

The above said article is for mailbox, but the theory remain same for all the archives.

If you follow this article carefully then i strongly believe your issue will be resolved :)

Regards,

MN

nils35's picture

Hello ManishN,

I am not competent to follow your advise to restore a single table and at the same time avoiding new data to be lost. I thought this was what I was paying you for. I do have the SQL backup taken right before your support consultant did the fatal changes, so can you restore this to your environment and compare it with the current table to see what went wrong?

ManishN's picture

Hi Nil,

Could you please share me your Case ID registered with us?

Probably i'll take a look at this one.

Regards,

MN

nils35's picture

Hi,

I will be happy to. It's Case 419-183-723.

Thanks,

Nils

Jeff Shotton's picture

By the way, archivefolderview is a VIEW. Not a table. Restoring a view is a bit pointless, since it just accesses the underlying tables, such as archivefolder.

But then possibly archivefolderfix has made other changes as well.

It has, apparently, been expanded to work with public folder archives: http://www.symantec.com/docs/TECH137230

I hope the right version was run against the database...

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

nils35's picture

Thanks for this information Jeff. ArchiveFolderFix.exe v1.5 was run, and thanks to you, I found the log files from when Symantec ran it against our Public Folders:

12:44:53 ¤ ArchiveFolderFix.exe v1.5 ¤ Symantec Corporation ¤ OCH ¤
12:44:53 ¤ Logging started August 29, 2012 at 12:44:53 PM
12:44:53 Archive to process : 10EBB69F19E63C445B89F6A438E6F1AC11110000bgo_vault
12:44:53 Logging enabled : True
12:44:53 · Logging enabled to file:
12:44:53 · C:\archivefolderfixPF.log
12:44:54 · Processing Public Folder Archive: 'Public Folder Vault Store'...
12:44:54 verfied the top of information store record
12:45:28 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
12:45:28 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
12:45:59 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
12:45:59 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
12:48:20 ¤ Error: No data exists for the row/column.
12:48:51 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
12:48:51 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
12:49:21 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
12:49:21 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
12:49:52 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
12:49:52 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
12:50:22 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
12:50:22 · Public Folder Archive 'Public Folder Vault Store' has been updated.
12:50:22 · All archives have been processed.
12:50:22 ¤  If the mailbox archive cannot be automatically repaired then please refer totechnote 340554(http://seer.entsupport.symantec.com/docs/340554.htm) for other solutions
12:50:22 ¤ Logging completed August 29, 2012 at 12:50:22 PM

12:59:04 ¤ ArchiveFolderFix.exe v1.5 ¤ Symantec Corporation ¤ OCH ¤
12:59:04 ¤ Logging started August 29, 2012 at 12:59:04 PM
12:59:04 Archive to process : 10EBB69F19E63C445B89F6A438E6F1AC11110000bgo_vault
12:59:04 Logging enabled : True
12:59:04 · Logging enabled to file:
12:59:04 · C:\archivefolderfixPF1.log
12:59:04 · Processing Public Folder Archive: 'Public Folder Vault Store'...
12:59:04 verfied the top of information store record
12:59:35 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
12:59:35 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
13:00:07 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
13:00:07 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
13:00:45 ¤ Error: No data exists for the row/column.
13:01:15 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
13:01:15 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
13:01:46 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
13:01:46 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
13:02:16 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
13:02:16 ¤ Execution of stored procedure UpdateDescendentPublicFolderArchiveFolderPaths failed.
13:02:47 ¤ Error: -2146232009ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired
13:02:47 · Public Folder Archive 'Public Folder Vault Store' has been updated.
13:02:47 · All archives have been processed.
13:02:47 ¤  If the mailbox archive cannot be automatically repaired then please refer totechnote 340554(http://seer.entsupport.symantec.com/docs/340554.htm) for other solutions
13:02:47 ¤ Logging completed August 29, 2012 at 01:02:47 PM

Regards,

Nils

nils35's picture

The Symantec consultant also ran a number of queries in SQL. Do you know if these queries are logged anywhere so that we can see what she did?

Thanks,

Nils

ManishN's picture

Nil,

I did some test in my lab and here are my findings

1.Created a Public Folder Archive Container named 'Public Folder Archive'. (see in the VaultAdmin console- Evsite>Archives>Exchange PublicFolder)

 

2. I then added two public folder as targets namely:

   a. Marketing

   b. Sales

3.See below a screenshot of how it should reflect in Archiveexplorerui.asp (that is when browsing the link using IE). The two tagetted public folders(marketing & Sales) are reflecting under Public Folder Archive container(called Public Folder Archive)

 

4.I then had a look at SQL and found the parentfolderrootidentity of Marketing & sales = NULL.

Note: For all the public folders which have been targetted(see step 2) the value of their Parentfolderrootidentity MUST be NULL

In your environment, we are seeing two folders(Contacts & Public Folder Vault Store) under your Public folder Archive container(which also is called Public Folder Vault Store). If we require that all the targetted public folders should reflect under this container, then the parentfolderrootidentity of these targeted folders should be NULL.

See the view of archiveexplorer in IE, I think the problem here is the targetted public folders have their parentfolderrootidentity set to a value other than NULL.

Looking at the screenclip taken from Exchange, i would say pick one of the targetted Public folders(eg DUR,DXB) and set their parrentfolderrootidentity = NULL. you should then see these reflecting in archiveexplorer.

Regards,

MN

Jeff Shotton's picture

Looks like the right version of the tool was run. And Manish, you are most likely correct, but I do question whether it was wise to post an update query which could, if wrong, cause even more trouble and a bigger mess to sort out. If you truly want to sort this, might I suggest you get on a webex with nils.

What was posted above is exactly what I anticipate, with the extra point that a  \ record has been inserted as a false root, when it is entirely possible for a public folder archive to have multiple top level folder as multiple archive points can point directly to an archive.

The fact that this is showing correctly when manual permissions are given indicates that the actual underlying structure itself is ok, but to confirm this (and to work out how many records you need to update above) a query should be run to double check.

--The following should return one row, which has a path of '\'

use EnterpriseVaultDirectory

select

AFV.* from Archive A

inner join ArchiveFolderview AFV on AFV.ContainerRootIdentity = A.RootIdentity

where A.ArchiveName = 'Public Folder Vault Store'

and AFV.ParentFolderRootIdentity is null

--This should return multiple rows. Each one should represent a public folder archive point

--as you see in the vault console (assuming no other issues)

use EnterpriseVaultDirectory

select * from ArchiveFolderView where ParentFolderRootIdentity in

(select AFV.RootIdentity from Archive A

inner join ArchiveFolderview AFV on AFV.ContainerRootIdentity = A.RootIdentity

where A.ArchiveName = 'Public Folder Vault Store'

and AFV.ParentFolderRootIdentity is null

)

I could go on and write a query to update the lot in one go, but I think taking precautionary steps such as having a backup and having someone who can interpret the output available (so they know if a rollback or a tweak is needed after the script runs) would be sensible.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

Jeff Shotton's picture

I'd also just point out for anyone else reading this in the future, that the query above was specifically written for nils, and that if you want to investigate something similar, then the select query is entirely safe to run, but you will need to update the ArchiveName within the single quotes with the one that you are using.

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

ManishN's picture

Nil,

As jeff said and i also think that we could initiate a webex on Monday, prior to this i need to take permission from my manager to do so and if permit than i will call you on the case which you had given.

As the case ownership is not with me, so i have to take ownership.

Regards,

MN

nils35's picture

Thanks everyone for spending time on helping with this.

ManishN, maybe you can contact the guy who has the ownership of the case and discuss your findings with him? I will be out of office next week, but my colleague will be available to do a webex.

Best regards,

Nils

ManishN's picture

Nil,

We did webex and seems your issue is resolved, confirmed with your colleague (Tommy).

Regards,

MN

nils35's picture

Hi,

It is only somewhat resolved. Users can now see the Public Folders archive in Archive Explorer, but not all the Public Folders they have permissions to. I have sent an email back to support and hopefully they will reopen the case.

Regards,

Nils