If the below does not resolve your issue please see my other blog which has the same symptoms (Do read this linked entry before discarding).
After lots of digging around I found that this was due to the web.config in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\ADMIN.
The web.config shown below shows the issue:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configuration>
<system.web>
<compilation batch="false" />
<customErrors mode="On" />
<httpRuntime executionTimeout="1200" />
<authorization>
<allow roles="BUILTIN\Administrators" />
<allow roles="EXTRANET\WSS_ADMIN_WPG" />
<deny users="*" />
</authorization>
</system.web>
<location path="vsgeneralsettings.aspx">
<system.web>
<httpRuntime executionTimeout="3600" />
</system.web>
</location>
<location path="targetwebapplication.aspx">
<system.web>
<httpRuntime executionTimeout="3600" />
</system.web>
</location>
<location path="configureupgradedatabases.aspx">
<system.web>
<httpRuntime executionTimeout="3600" />
</system.web>
</location>
</configuration>
I noticed that ‘EXTRANET’ was the name of the old server and the new server was called for example ‘SERVER1’ (noting that this is the name of the local server and not the domain name so this will differ on each server in the farm).
I updated the line with the following:
<allow roles="SERVER1\WSS_ADMIN_WPG" />
I carried out an IISRESET and farm administrators could now log onto SharePoint Central Administration.
Credit to MVP Andreas Stenhall’s blog which helped me track down this issue.
0 comments:
Post a Comment