Public folders have disappared.

[Jackmetickler]

I wonder if any one can point me in the right direction for a problem I am having with Public Folders

My public folders are mounted and db files in exchsrvr/mdbdata look fine although I have not use eseutil or isinteg on them yet.

From my exchange drive (M) I cannot connect to the Public Folder directory - unable to enumerate files and directories - the system cannot find specified path.
other folders OK

From ESM - all looks fine - Public Folder directory OK but Folders directoty does not contain my public folders and if I try and create a new public folder then I get a http conflict occured c103b403 ensure your default virtual server is running.

From IIS - all folders connect except Public - the folder was moved or removed.

PFDavAdmin does not locate public folders
Outlook clients unable to display.

Google pointed me in the direction of permissions but I am unable to find folder to check this.

Would I benefit from running isinteg to see if pub.edb is clean.

Any assistance gratefully received.

Regards
Jack

 

[MarkArnold]

You should never, ever, touch, look at, in or around the M:\
You should never virus scan it or look at the permissions, much less change them.

We can assume the Information Store is running but is the Public Folder store mounted?

When you look at the Public Folders within Outlook or Outlook Web Access, what do you get?

Have you got anything running against the M:\ ?

 

[Jackmetickler]

Mark
Many thanks for your assistance.

I did not do anything from the M: drive but I did look there when I started having problems with the PF.
Information store is running and public folder is mounted.

Virusscan does not scan m:drive.

From outlook - unable to display folders. MS Outlook could not access specified location. An unexpected error has occured.

Any pointers gratefully received.

Jack

 

[MarkArnold]

That's a good thing then about the M. Keep it that way
Have you yet recreated the PUBLIC directory in IIS and is the EXADMIN folder there as well?

 

[Jackmetickler]

Mark

Exadmin in IIS.
Public showing in IIS but will not connect.

Should I recreate - what is best way to go about this?

Many thanks
Jack

 

[MarkArnold]

There are a few ways ranging from simply recreating and repointing the paths to delving into the metabase and building from the ground up.

http://technet.microsoft.com/en-gb/library/aa996098.aspx

is what I use to remember the old 2003 steps. Take a look and see. The "backofficestorage" folder path should be fairly intuitive to you.

 

[Marcs41]

As an side remark, it is not suuficient to NOT scan the M: drive, but you should also exclude the REAL path from being scanned.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC![/sub]

 

[Jackmetickler]

Just to keep you in the picture - I am progressing through MarkArnolds link but have not solved it yet.
Will let you know how it goes.
For Marc - thanks, I have excluded ALL exchange directories on server - is it wise to exclude all or should it just be the 'real path' and what exactly is that.

Many thanks
Jack

 

[Marcs41]

Just the MDBDATA folders is fine.
I don't know your exact path, but it is something like
C:\EXCHSRVR\MDBDATA (Replace C: with the real drive)

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC![/sub]