After crash, OWA access for some but not others. - Microsoft Exchange
This is a discussion on After crash, OWA access for some but not others. - Microsoft Exchange ; I'm not sure where this lands, OWA, IIS or Exchange but here goes.(using
Win2k server, Ex2k fully updated and patched)
After a raid dual disk failure (neither drive would work as master, odd
in itself) I cloned one of the ...
-
After crash, OWA access for some but not others.
I'm not sure where this lands, OWA, IIS or Exchange but here goes.(using
Win2k server, Ex2k fully updated and patched)
After a raid dual disk failure (neither drive would work as master, odd
in itself) I cloned one of the drives with a hardware device and then put it
into an XP machine to chkdsk it, it spent about 20 minutes "resetting
security attributes" and other issues common with a disk failure. Then I put
it in the server. After tweaking a few things and restoring a few missing
files the system started up , but Exchange didn't.
I manually started each of exchange services and after finding the right
sequence they all came up (!) (They still don't start on reboot and have to
be started manually. Alas I'll look at that more as well, perhaps it's
related.
Mail seems to be flowing now and lan and dial-up users can get their mail
just fine. OWA users however are not so lucky.
I can get into OWA and read my mail but when I log off I get a server error
500 and the error events:
"Event ID 36 server failed to load application /lm/w3svc/1/root,. The error
was general access denied error"
"Event ID 10001 Unable to start DCOM server { guid...} ... the error: access
denied."
Many other users are denied access completely. I have checked their account
permissions and all is well.
For curiousity I want looking for the storage and found the M: drive
contains folders with everyones name as well as a public folder. So I poked
a bit and find that I can open my folder and all the folders of the people
who CAN use OWA, and I can't open the folders of the ones that can't. Ah
hah I think!. I find the problem!. The error I get when I open the security
tab for the folders in question is "You do not have permission to view or
edit current permissions for xxx".
Since I am the top admin I should have all the permission in the world, but
since the M: Drive is created by Exchange and not a "real" drive I don't
know what exactly to look for next. Perhaps the "security atttributes" that
were fixed have created more issues?
Any help anyone... anyone... Bueller?
-
Re: After crash, OWA access for some but not others.
FWIW the problem was Authenticated Users not having the right permissions to
\system32 and \Common files folders.
Read and Execute are needed, not just Read which is what every online
resource I found had listed.
<churchmouse@noemail.nospam> wrote in message
news:e%23eD1HOPGHA.2628@TK2MSFTNGP15.phx.gbl...
> I'm not sure where this lands, OWA, IIS or Exchange but here goes.(using
> Win2k server, Ex2k fully updated and patched)
>
> After a raid dual disk failure (neither drive would work as master, odd
> in itself) I cloned one of the drives with a hardware device and then put
> it into an XP machine to chkdsk it, it spent about 20 minutes "resetting
> security attributes" and other issues common with a disk failure. Then I
> put it in the server. After tweaking a few things and restoring a few
> missing files the system started up , but Exchange didn't.
>
> I manually started each of exchange services and after finding the
> right sequence they all came up (!) (They still don't start on reboot and
> have to be started manually. Alas I'll look at that more as well, perhaps
> it's related.
>
> Mail seems to be flowing now and lan and dial-up users can get their mail
> just fine. OWA users however are not so lucky.
>
> I can get into OWA and read my mail but when I log off I get a server
> error 500 and the error events:
> "Event ID 36 server failed to load application /lm/w3svc/1/root,. The
> error was general access denied error"
> "Event ID 10001 Unable to start DCOM server { guid...} ... the error:
> access denied."
>
> Many other users are denied access completely. I have checked their
> account permissions and all is well.
>
> For curiousity I want looking for the storage and found the M: drive
> contains folders with everyones name as well as a public folder. So I
> poked a bit and find that I can open my folder and all the folders of the
> people who CAN use OWA, and I can't open the folders of the ones that
> can't. Ah hah I think!. I find the problem!. The error I get when I open
> the security tab for the folders in question is "You do not have
> permission to view or edit current permissions for xxx".
>
> Since I am the top admin I should have all the permission in the world,
> but since the M: Drive is created by Exchange and not a "real" drive I
> don't know what exactly to look for next. Perhaps the "security
> atttributes" that were fixed have created more issues?
>
> Any help anyone... anyone... Bueller?
>
Similar Threads
-
By Application Development in forum ADO DAO RDO RDS
Replies: 0
Last Post: 09-18-2007, 04:22 PM
-
By Application Development in forum ADO DAO RDO RDS
Replies: 1
Last Post: 09-02-2007, 08:22 AM
-
By Application Development in forum DOTNET
Replies: 0
Last Post: 05-07-2007, 01:53 PM
-
By Application Development in forum Adobe Photoshop
Replies: 0
Last Post: 01-10-2007, 01:57 PM
-
By Application Development in forum Pegasus
Replies: 1
Last Post: 04-11-2006, 11:35 AM