Hello Everyone,

I'm trying to install Ex2k7 on a w2k3 domain that is migrated from w2k.

Setup starts fine, until het gets to the Client Access Role. Then I get the
following error:

'Requested Registry Access is not allowed'

and:
--------------------------------------------------
Summary: 3 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:39

Client Access Role
Failed

Error:
Requested registry access is not allowed.

Warning:
An unexpected error has occurred and a Watson dump is being generated:
Requested registry access is not allowed.

Elapsed Time: 00:00:39

Mailbox Role
Cancelled

Unified Messaging Role
Cancelled
--------------------------------------------------

And the the installation stops with the creation of a Watson file. These are
the last lines in this log:

--------------------------------------------------

[5/17/2007 2:20:30 PM] [1] Processing component 'OWA Configuration'
(Configuring Outlook Web Access for Client Access role.).
[5/17/2007 2:20:30 PM] [1] Executing '$InternalOwaUrl="https://" +
$RoleFqdnOrName + "/owa"; new-OwaVirtualDirectory -DomainController
$RoleDomainController -InternalUrl $InternalOwaUrl;', handleError = False
[5/17/2007 2:20:30 PM] [2] Launching sub-task '$error.Clear();
$InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl
$InternalOwaUrl;'.
[5/17/2007 2:20:30 PM] [2] Beginning processing.
[5/17/2007 2:20:30 PM] [2] Administrator Active Directory session settings
are: View Entire Forest: 'True', Configuration Domain Controller:
'xxx-xxx-2k3.xxxxx.xxx', Preferred Global Catalog: 'xxx-xxx-2k3.xxxxx.xxx,
Preferred Domain Controllers: '{ 'xxx-xxx-2k3.xxxxx.xxx }'
[5/17/2007 2:20:30 PM] [2] Searching objects "'xxx-xxx-2k3.xxxxx.xxx" of
type "Server" under the root "$null".
[5/17/2007 2:20:30 PM] [2] Previous operation run on domain controller
'xxx-xxx-2k3.xxxxx.xxx.
[5/17/2007 2:20:30 PM] [2] Processing object "'xxx-xxx-2k3\owa".
[5/17/2007 2:20:30 PM] [2] [WARNING] An unexpected error has occurred and a
Watson dump is being generated: Requested registry access is not allowed.
[5/17/2007 2:20:30 PM] [2] [ERROR] Requested registry access is not allowed.
[5/17/2007 2:20:42 PM] [1] Exception :
System.Management.Automation.CmdletInvocationException: Requested registry
access is not allowed. ---> System.Security.SecurityException: Requested
registry access is not allowed.
at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
at
Microsoft.Exchange.Management.Metabase.IisUtility.IsSupportedIisVersion(String serverName)
at Microsoft.Exchange.Management.Metabase.IisVersionValidCondition.Verify()
at
Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
at
Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
at System.Management.Automation.Cmdlet.DoProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
The Zone of the assembly that failed was:
MyComputer
--- End of inner exception stack trace ---
at
System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Parser.PipelineNode.Execute(Array input,
Pipe outputPipe, ArrayList& resultList)
at System.Management.Automation.Parser.StatementListNode.Execute(Array
input, Pipe outputPipe, ArrayList& resultList)
[5/17/2007 2:20:42 PM] [1] [WARNING] An unexpected error has occurred and a
Watson dump is being generated: Requested registry access is not allowed.
[5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
[5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.

--------------------------------------------------
I guess it has something to do with registry access when he wants to create
the Virutal Directories for OWA, and he needs access for that.

The old w2k domain had some freaky group policy on it, which I disabled
already, but no luck at all.

Who can give me the hint what registry key I need to change (rights) to get
the installation finished?

Regards, Dirk

RE: Ex2k7 Client Access Role Installation - Registry Error by Dirk

Dirk
Thu May 17 10:28:01 CDT 2007

Here is a little update...

I have been looking for this error on the internet, and I found some results
on "System.Security.SecurityException".

I tried adding full rights to the registry key, no luck. I tried changing
the Identity of the application pool, no luck. Even reinstalled IIS, and now
reinstalling .NET.

Is there anyone who has a clue how we can get this problem away?

Regards, Dirk

"Dirk" wrote:

> Hello Everyone,
>
> I'm trying to install Ex2k7 on a w2k3 domain that is migrated from w2k.
>
> Setup starts fine, until het gets to the Client Access Role. Then I get the
> following error:
>
> 'Requested Registry Access is not allowed'
>
> and:
> --------------------------------------------------
> Summary: 3 item(s). 0 succeeded, 1 failed.
> Elapsed time: 00:00:39
>
> Client Access Role
> Failed
>
> Error:
> Requested registry access is not allowed.
>
> Warning:
> An unexpected error has occurred and a Watson dump is being generated:
> Requested registry access is not allowed.
>
> Elapsed Time: 00:00:39
>
> Mailbox Role
> Cancelled
>
> Unified Messaging Role
> Cancelled
> --------------------------------------------------
>
> And the the installation stops with the creation of a Watson file. These are
> the last lines in this log:
>
> --------------------------------------------------
>
> [5/17/2007 2:20:30 PM] [1] Processing component 'OWA Configuration'
> (Configuring Outlook Web Access for Client Access role.).
> [5/17/2007 2:20:30 PM] [1] Executing '$InternalOwaUrl="https://" +
> $RoleFqdnOrName + "/owa"; new-OwaVirtualDirectory -DomainController
> $RoleDomainController -InternalUrl $InternalOwaUrl;', handleError = False
> [5/17/2007 2:20:30 PM] [2] Launching sub-task '$error.Clear();
> $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
> new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl
> $InternalOwaUrl;'.
> [5/17/2007 2:20:30 PM] [2] Beginning processing.
> [5/17/2007 2:20:30 PM] [2] Administrator Active Directory session settings
> are: View Entire Forest: 'True', Configuration Domain Controller:
> 'xxx-xxx-2k3.xxxxx.xxx', Preferred Global Catalog: 'xxx-xxx-2k3.xxxxx.xxx,
> Preferred Domain Controllers: '{ 'xxx-xxx-2k3.xxxxx.xxx }'
> [5/17/2007 2:20:30 PM] [2] Searching objects "'xxx-xxx-2k3.xxxxx.xxx" of
> type "Server" under the root "$null".
> [5/17/2007 2:20:30 PM] [2] Previous operation run on domain controller
> 'xxx-xxx-2k3.xxxxx.xxx.
> [5/17/2007 2:20:30 PM] [2] Processing object "'xxx-xxx-2k3\owa".
> [5/17/2007 2:20:30 PM] [2] [WARNING] An unexpected error has occurred and a
> Watson dump is being generated: Requested registry access is not allowed.
> [5/17/2007 2:20:30 PM] [2] [ERROR] Requested registry access is not allowed.
> [5/17/2007 2:20:42 PM] [1] Exception :
> System.Management.Automation.CmdletInvocationException: Requested registry
> access is not allowed. ---> System.Security.SecurityException: Requested
> registry access is not allowed.
> at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
> at
> Microsoft.Exchange.Management.Metabase.IisUtility.IsSupportedIisVersion(String serverName)
> at Microsoft.Exchange.Management.Metabase.IisVersionValidCondition.Verify()
> at
> Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
> at
> Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory.InternalValidate()
> at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
> at System.Management.Automation.Cmdlet.DoProcessRecord()
> at System.Management.Automation.CommandProcessor.ProcessRecord()
> The Zone of the assembly that failed was:
> MyComputer
> --- End of inner exception stack trace ---
> at
> System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
> at System.Management.Automation.Parser.PipelineNode.Execute(Array input,
> Pipe outputPipe, ArrayList& resultList)
> at System.Management.Automation.Parser.StatementListNode.Execute(Array
> input, Pipe outputPipe, ArrayList& resultList)
> [5/17/2007 2:20:42 PM] [1] [WARNING] An unexpected error has occurred and a
> Watson dump is being generated: Requested registry access is not allowed.
> [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
> [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
>
> --------------------------------------------------
> I guess it has something to do with registry access when he wants to create
> the Virutal Directories for OWA, and he needs access for that.
>
> The old w2k domain had some freaky group policy on it, which I disabled
> already, but no luck at all.
>
> Who can give me the hint what registry key I need to change (rights) to get
> the installation finished?
>
> Regards, Dirk
>
>

RE: Ex2k7 Client Access Role Installation - Registry Error by ncawley

ncawley
Sun Jun 03 04:49:01 CDT 2007

Did you manage to find a solution to this one?
I have exactly the same problem and it appears you may have done everything
i have too.


"Dirk" wrote:

> Here is a little update...
>
> I have been looking for this error on the internet, and I found some results
> on "System.Security.SecurityException".
>
> I tried adding full rights to the registry key, no luck. I tried changing
> the Identity of the application pool, no luck. Even reinstalled IIS, and now
> reinstalling .NET.
>
> Is there anyone who has a clue how we can get this problem away?
>
> Regards, Dirk
>
> "Dirk" wrote:
>
> > Hello Everyone,
> >
> > I'm trying to install Ex2k7 on a w2k3 domain that is migrated from w2k.
> >
> > Setup starts fine, until het gets to the Client Access Role. Then I get the
> > following error:
> >
> > 'Requested Registry Access is not allowed'
> >
> > and:
> > --------------------------------------------------
> > Summary: 3 item(s). 0 succeeded, 1 failed.
> > Elapsed time: 00:00:39
> >
> > Client Access Role
> > Failed
> >
> > Error:
> > Requested registry access is not allowed.
> >
> > Warning:
> > An unexpected error has occurred and a Watson dump is being generated:
> > Requested registry access is not allowed.
> >
> > Elapsed Time: 00:00:39
> >
> > Mailbox Role
> > Cancelled
> >
> > Unified Messaging Role
> > Cancelled
> > --------------------------------------------------
> >
> > And the the installation stops with the creation of a Watson file. These are
> > the last lines in this log:
> >
> > --------------------------------------------------
> >
> > [5/17/2007 2:20:30 PM] [1] Processing component 'OWA Configuration'
> > (Configuring Outlook Web Access for Client Access role.).
> > [5/17/2007 2:20:30 PM] [1] Executing '$InternalOwaUrl="https://" +
> > $RoleFqdnOrName + "/owa"; new-OwaVirtualDirectory -DomainController
> > $RoleDomainController -InternalUrl $InternalOwaUrl;', handleError = False
> > [5/17/2007 2:20:30 PM] [2] Launching sub-task '$error.Clear();
> > $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
> > new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl
> > $InternalOwaUrl;'.
> > [5/17/2007 2:20:30 PM] [2] Beginning processing.
> > [5/17/2007 2:20:30 PM] [2] Administrator Active Directory session settings
> > are: View Entire Forest: 'True', Configuration Domain Controller:
> > 'xxx-xxx-2k3.xxxxx.xxx', Preferred Global Catalog: 'xxx-xxx-2k3.xxxxx.xxx,
> > Preferred Domain Controllers: '{ 'xxx-xxx-2k3.xxxxx.xxx }'
> > [5/17/2007 2:20:30 PM] [2] Searching objects "'xxx-xxx-2k3.xxxxx.xxx" of
> > type "Server" under the root "$null".
> > [5/17/2007 2:20:30 PM] [2] Previous operation run on domain controller
> > 'xxx-xxx-2k3.xxxxx.xxx.
> > [5/17/2007 2:20:30 PM] [2] Processing object "'xxx-xxx-2k3\owa".
> > [5/17/2007 2:20:30 PM] [2] [WARNING] An unexpected error has occurred and a
> > Watson dump is being generated: Requested registry access is not allowed.
> > [5/17/2007 2:20:30 PM] [2] [ERROR] Requested registry access is not allowed.
> > [5/17/2007 2:20:42 PM] [1] Exception :
> > System.Management.Automation.CmdletInvocationException: Requested registry
> > access is not allowed. ---> System.Security.SecurityException: Requested
> > registry access is not allowed.
> > at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
> > at
> > Microsoft.Exchange.Management.Metabase.IisUtility.IsSupportedIisVersion(String serverName)
> > at Microsoft.Exchange.Management.Metabase.IisVersionValidCondition.Verify()
> > at
> > Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
> > at
> > Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory.InternalValidate()
> > at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
> > at System.Management.Automation.Cmdlet.DoProcessRecord()
> > at System.Management.Automation.CommandProcessor.ProcessRecord()
> > The Zone of the assembly that failed was:
> > MyComputer
> > --- End of inner exception stack trace ---
> > at
> > System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
> > at System.Management.Automation.Parser.PipelineNode.Execute(Array input,
> > Pipe outputPipe, ArrayList& resultList)
> > at System.Management.Automation.Parser.StatementListNode.Execute(Array
> > input, Pipe outputPipe, ArrayList& resultList)
> > [5/17/2007 2:20:42 PM] [1] [WARNING] An unexpected error has occurred and a
> > Watson dump is being generated: Requested registry access is not allowed.
> > [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
> > [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
> >
> > --------------------------------------------------
> > I guess it has something to do with registry access when he wants to create
> > the Virutal Directories for OWA, and he needs access for that.
> >
> > The old w2k domain had some freaky group policy on it, which I disabled
> > already, but no luck at all.
> >
> > Who can give me the hint what registry key I need to change (rights) to get
> > the installation finished?
> >
> > Regards, Dirk
> >
> >

RE: Ex2k7 Client Access Role Installation - Registry Error by Dirk

Dirk
Sun Jun 03 05:47:00 CDT 2007

Yes, I have solved this problem. It had to do with giving rights to some
registry keys (I love upgrading from w2k to W2k3!).

Here is the whole story I got back from my MS Engineer:

I'd like to explain this issue may occur if the Local Service and Exchange
server doesn't have sufficient permission for the following registry key:

HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winre
HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\AllowedExactPaths
HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\AllowedPaths

For the time being, please perform the following steps to try to resolve
this issue:

1). On the server, open registry editor.
2). Right click the key "winreg" and select permissions.

Make sure we put full permission for, LOCAL SERVICE, SYSTEM and
"<YourDomain>\administrator".

3). Please also check the key "AllowedExactPaths" and "AllowedPaths".
4). Restart the server and try to reinstall the Exchange.

I do not know what your situation is at this moment (did you upgrade from
w2k?). Because I could not install, I tried some things as mentioned in my
previous mails, also reinstalling the IIS. That was not too smart, because it
then also deleted the IIS settings already set in the first roles you already
installed with Exchange 2007.

My syggestion is: before doing the above, uninstall exchange 2007, then make
the registry settings, then totally reinstall exchange 2007.

Hope this works, let me know the result.

Regards, Dirk




"ncawley" wrote:

> Did you manage to find a solution to this one?
> I have exactly the same problem and it appears you may have done everything
> i have too.
>
>
> "Dirk" wrote:
>
> > Here is a little update...
> >
> > I have been looking for this error on the internet, and I found some results
> > on "System.Security.SecurityException".
> >
> > I tried adding full rights to the registry key, no luck. I tried changing
> > the Identity of the application pool, no luck. Even reinstalled IIS, and now
> > reinstalling .NET.
> >
> > Is there anyone who has a clue how we can get this problem away?
> >
> > Regards, Dirk
> >
> > "Dirk" wrote:
> >
> > > Hello Everyone,
> > >
> > > I'm trying to install Ex2k7 on a w2k3 domain that is migrated from w2k.
> > >
> > > Setup starts fine, until het gets to the Client Access Role. Then I get the
> > > following error:
> > >
> > > 'Requested Registry Access is not allowed'
> > >
> > > and:
> > > --------------------------------------------------
> > > Summary: 3 item(s). 0 succeeded, 1 failed.
> > > Elapsed time: 00:00:39
> > >
> > > Client Access Role
> > > Failed
> > >
> > > Error:
> > > Requested registry access is not allowed.
> > >
> > > Warning:
> > > An unexpected error has occurred and a Watson dump is being generated:
> > > Requested registry access is not allowed.
> > >
> > > Elapsed Time: 00:00:39
> > >
> > > Mailbox Role
> > > Cancelled
> > >
> > > Unified Messaging Role
> > > Cancelled
> > > --------------------------------------------------
> > >
> > > And the the installation stops with the creation of a Watson file. These are
> > > the last lines in this log:
> > >
> > > --------------------------------------------------
> > >
> > > [5/17/2007 2:20:30 PM] [1] Processing component 'OWA Configuration'
> > > (Configuring Outlook Web Access for Client Access role.).
> > > [5/17/2007 2:20:30 PM] [1] Executing '$InternalOwaUrl="https://" +
> > > $RoleFqdnOrName + "/owa"; new-OwaVirtualDirectory -DomainController
> > > $RoleDomainController -InternalUrl $InternalOwaUrl;', handleError = False
> > > [5/17/2007 2:20:30 PM] [2] Launching sub-task '$error.Clear();
> > > $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
> > > new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl
> > > $InternalOwaUrl;'.
> > > [5/17/2007 2:20:30 PM] [2] Beginning processing.
> > > [5/17/2007 2:20:30 PM] [2] Administrator Active Directory session settings
> > > are: View Entire Forest: 'True', Configuration Domain Controller:
> > > 'xxx-xxx-2k3.xxxxx.xxx', Preferred Global Catalog: 'xxx-xxx-2k3.xxxxx.xxx,
> > > Preferred Domain Controllers: '{ 'xxx-xxx-2k3.xxxxx.xxx }'
> > > [5/17/2007 2:20:30 PM] [2] Searching objects "'xxx-xxx-2k3.xxxxx.xxx" of
> > > type "Server" under the root "$null".
> > > [5/17/2007 2:20:30 PM] [2] Previous operation run on domain controller
> > > 'xxx-xxx-2k3.xxxxx.xxx.
> > > [5/17/2007 2:20:30 PM] [2] Processing object "'xxx-xxx-2k3\owa".
> > > [5/17/2007 2:20:30 PM] [2] [WARNING] An unexpected error has occurred and a
> > > Watson dump is being generated: Requested registry access is not allowed.
> > > [5/17/2007 2:20:30 PM] [2] [ERROR] Requested registry access is not allowed.
> > > [5/17/2007 2:20:42 PM] [1] Exception :
> > > System.Management.Automation.CmdletInvocationException: Requested registry
> > > access is not allowed. ---> System.Security.SecurityException: Requested
> > > registry access is not allowed.
> > > at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
> > > at
> > > Microsoft.Exchange.Management.Metabase.IisUtility.IsSupportedIisVersion(String serverName)
> > > at Microsoft.Exchange.Management.Metabase.IisVersionValidCondition.Verify()
> > > at
> > > Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
> > > at
> > > Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory.InternalValidate()
> > > at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
> > > at System.Management.Automation.Cmdlet.DoProcessRecord()
> > > at System.Management.Automation.CommandProcessor.ProcessRecord()
> > > The Zone of the assembly that failed was:
> > > MyComputer
> > > --- End of inner exception stack trace ---
> > > at
> > > System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
> > > at System.Management.Automation.Parser.PipelineNode.Execute(Array input,
> > > Pipe outputPipe, ArrayList& resultList)
> > > at System.Management.Automation.Parser.StatementListNode.Execute(Array
> > > input, Pipe outputPipe, ArrayList& resultList)
> > > [5/17/2007 2:20:42 PM] [1] [WARNING] An unexpected error has occurred and a
> > > Watson dump is being generated: Requested registry access is not allowed.
> > > [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
> > > [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
> > >
> > > --------------------------------------------------
> > > I guess it has something to do with registry access when he wants to create
> > > the Virutal Directories for OWA, and he needs access for that.
> > >
> > > The old w2k domain had some freaky group policy on it, which I disabled
> > > already, but no luck at all.
> > >
> > > Who can give me the hint what registry key I need to change (rights) to get
> > > the installation finished?
> > >
> > > Regards, Dirk
> > >
> > >

RE: Ex2k7 Client Access Role Installation - Registry Error by ncawley

ncawley
Sun Jun 03 07:23:00 CDT 2007

Hi Dirk,

Thanks very much for that pointer and i'm pleased to say it worked for me
too.

Thanks again

"Dirk" wrote:

> Yes, I have solved this problem. It had to do with giving rights to some
> registry keys (I love upgrading from w2k to W2k3!).
>
> Here is the whole story I got back from my MS Engineer:
>
> I'd like to explain this issue may occur if the Local Service and Exchange
> server doesn't have sufficient permission for the following registry key:
>
> HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
> HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\AllowedExactPaths
> HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\AllowedPaths
>
> For the time being, please perform the following steps to try to resolve
> this issue:
>
> 1). On the server, open registry editor.
> 2). Right click the key "winreg" and select permissions.
>
> Make sure we put full permission for, LOCAL SERVICE, SYSTEM and
> "<YourDomain>\administrator".
>
> 3). Please also check the key "AllowedExactPaths" and "AllowedPaths".
> 4). Restart the server and try to reinstall the Exchange.
>
> I do not know what your situation is at this moment (did you upgrade from
> w2k?). Because I could not install, I tried some things as mentioned in my
> previous mails, also reinstalling the IIS. That was not too smart, because it
> then also deleted the IIS settings already set in the first roles you already
> installed with Exchange 2007.
>
> My syggestion is: before doing the above, uninstall exchange 2007, then make
> the registry settings, then totally reinstall exchange 2007.
>
> Hope this works, let me know the result.
>
> Regards, Dirk
>
>
>
>
> "ncawley" wrote:
>
> > Did you manage to find a solution to this one?
> > I have exactly the same problem and it appears you may have done everything
> > i have too.
> >
> >
> > "Dirk" wrote:
> >
> > > Here is a little update...
> > >
> > > I have been looking for this error on the internet, and I found some results
> > > on "System.Security.SecurityException".
> > >
> > > I tried adding full rights to the registry key, no luck. I tried changing
> > > the Identity of the application pool, no luck. Even reinstalled IIS, and now
> > > reinstalling .NET.
> > >
> > > Is there anyone who has a clue how we can get this problem away?
> > >
> > > Regards, Dirk
> > >
> > > "Dirk" wrote:
> > >
> > > > Hello Everyone,
> > > >
> > > > I'm trying to install Ex2k7 on a w2k3 domain that is migrated from w2k.
> > > >
> > > > Setup starts fine, until het gets to the Client Access Role. Then I get the
> > > > following error:
> > > >
> > > > 'Requested Registry Access is not allowed'
> > > >
> > > > and:
> > > > --------------------------------------------------
> > > > Summary: 3 item(s). 0 succeeded, 1 failed.
> > > > Elapsed time: 00:00:39
> > > >
> > > > Client Access Role
> > > > Failed
> > > >
> > > > Error:
> > > > Requested registry access is not allowed.
> > > >
> > > > Warning:
> > > > An unexpected error has occurred and a Watson dump is being generated:
> > > > Requested registry access is not allowed.
> > > >
> > > > Elapsed Time: 00:00:39
> > > >
> > > > Mailbox Role
> > > > Cancelled
> > > >
> > > > Unified Messaging Role
> > > > Cancelled
> > > > --------------------------------------------------
> > > >
> > > > And the the installation stops with the creation of a Watson file. These are
> > > > the last lines in this log:
> > > >
> > > > --------------------------------------------------
> > > >
> > > > [5/17/2007 2:20:30 PM] [1] Processing component 'OWA Configuration'
> > > > (Configuring Outlook Web Access for Client Access role.).
> > > > [5/17/2007 2:20:30 PM] [1] Executing '$InternalOwaUrl="https://" +
> > > > $RoleFqdnOrName + "/owa"; new-OwaVirtualDirectory -DomainController
> > > > $RoleDomainController -InternalUrl $InternalOwaUrl;', handleError = False
> > > > [5/17/2007 2:20:30 PM] [2] Launching sub-task '$error.Clear();
> > > > $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
> > > > new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl
> > > > $InternalOwaUrl;'.
> > > > [5/17/2007 2:20:30 PM] [2] Beginning processing.
> > > > [5/17/2007 2:20:30 PM] [2] Administrator Active Directory session settings
> > > > are: View Entire Forest: 'True', Configuration Domain Controller:
> > > > 'xxx-xxx-2k3.xxxxx.xxx', Preferred Global Catalog: 'xxx-xxx-2k3.xxxxx.xxx,
> > > > Preferred Domain Controllers: '{ 'xxx-xxx-2k3.xxxxx.xxx }'
> > > > [5/17/2007 2:20:30 PM] [2] Searching objects "'xxx-xxx-2k3.xxxxx.xxx" of
> > > > type "Server" under the root "$null".
> > > > [5/17/2007 2:20:30 PM] [2] Previous operation run on domain controller
> > > > 'xxx-xxx-2k3.xxxxx.xxx.
> > > > [5/17/2007 2:20:30 PM] [2] Processing object "'xxx-xxx-2k3\owa".
> > > > [5/17/2007 2:20:30 PM] [2] [WARNING] An unexpected error has occurred and a
> > > > Watson dump is being generated: Requested registry access is not allowed.
> > > > [5/17/2007 2:20:30 PM] [2] [ERROR] Requested registry access is not allowed.
> > > > [5/17/2007 2:20:42 PM] [1] Exception :
> > > > System.Management.Automation.CmdletInvocationException: Requested registry
> > > > access is not allowed. ---> System.Security.SecurityException: Requested
> > > > registry access is not allowed.
> > > > at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
> > > > at
> > > > Microsoft.Exchange.Management.Metabase.IisUtility.IsSupportedIisVersion(String serverName)
> > > > at Microsoft.Exchange.Management.Metabase.IisVersionValidCondition.Verify()
> > > > at
> > > > Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
> > > > at
> > > > Microsoft.Exchange.Management.SystemConfigurationTasks.NewOwaVirtualDirectory.InternalValidate()
> > > > at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
> > > > at System.Management.Automation.Cmdlet.DoProcessRecord()
> > > > at System.Management.Automation.CommandProcessor.ProcessRecord()
> > > > The Zone of the assembly that failed was:
> > > > MyComputer
> > > > --- End of inner exception stack trace ---
> > > > at
> > > > System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
> > > > at System.Management.Automation.Parser.PipelineNode.Execute(Array input,
> > > > Pipe outputPipe, ArrayList& resultList)
> > > > at System.Management.Automation.Parser.StatementListNode.Execute(Array
> > > > input, Pipe outputPipe, ArrayList& resultList)
> > > > [5/17/2007 2:20:42 PM] [1] [WARNING] An unexpected error has occurred and a
> > > > Watson dump is being generated: Requested registry access is not allowed.
> > > > [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
> > > > [5/17/2007 2:20:42 PM] [1] [ERROR] Requested registry access is not allowed.
> > > >
> > > > --------------------------------------------------
> > > > I guess it has something to do with registry access when he wants to create
> > > > the Virutal Directories for OWA, and he needs access for that.
> > > >
> > > > The old w2k domain had some freaky group policy on it, which I disabled
> > > > already, but no luck at all.
> > > >
> > > > Who can give me the hint what registry key I need to change (rights) to get
> > > > the installation finished?
> > > >
> > > > Regards, Dirk
> > > >
> > > >