Post by michael412 on Oct 27, 2011 7:45:25 GMT -6
I have just migrated a WSS3.0 system from a production server to a test server. They are not equivalent servers - production 64bit on domain with WID, test 32bit on workgroup with SQL2008ExpressAdvSvcs. Nevertheless I have it mostly working. I had to define my test server local Windows account as having Full Control using web site policy in Central Admin.
I can browse around OK, but when I do Site Actions->Site Settings I get the good old Access Denied page.
The IIS log shows this:
2011-10-27 12:21:39 W3SVC1461731931 192.168.2.99 GET /_layouts/settings.aspx - 8080 - 192.168.2.129 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.1;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0;+MDDS;+.NET4.0C;+.NET4.0E) 401 1 0
This doesn't tell me much but maybe will tell someone else more.
Perhaps the problem is related to the group structure. The production server is a Windows Small Business Server 2008 platform. It comes with some groups already set up for WSS use. Within WSS (which on a SBS2008 system is by default given the URL "companyweb") is a collection of groups "Companyweb Visitors", "Companyweb Owners", "Companyweb Members" and these are hooked through to Windows domain groups "Windows SBS SharePoint_VisitorsGroup", etc. I could try setting these groups up on my test server buth that would be a waste of time because WSS is tied to the groups on a specific domain.
I tried defining my local account as the owner of the site collection using the following command (note that my site is deliberately on port 8080):
stsadm -o siteowner -url http://testsvr1:8080 -ownerlogin testsvr1\Administrator
But this produced the error message:
Object reference not set to an instance of an object.
If nothing else we know that .Net is being used
I tried adding another local user account to the CompanyWeb Owners group using the command:
stsadm -o adduser -url http://testsvr1:8080 -userlogin testsvr1\abc001 -useremail blahblah@mycompany.com -group "CompanyWeb Owners" -username "ABC" -siteadmin
That resulted in:
Exception from HRESULT: 0x80040E14
Visual Studio's error lookup tool cannot find this code.
So, any smart person out there got any more ideas that I can try? I can't see anything else in the stsadm command set that looks like it might help, but I can miss stuff...
Michael
I can browse around OK, but when I do Site Actions->Site Settings I get the good old Access Denied page.
The IIS log shows this:
2011-10-27 12:21:39 W3SVC1461731931 192.168.2.99 GET /_layouts/settings.aspx - 8080 - 192.168.2.129 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.1;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0;+MDDS;+.NET4.0C;+.NET4.0E) 401 1 0
This doesn't tell me much but maybe will tell someone else more.
Perhaps the problem is related to the group structure. The production server is a Windows Small Business Server 2008 platform. It comes with some groups already set up for WSS use. Within WSS (which on a SBS2008 system is by default given the URL "companyweb") is a collection of groups "Companyweb Visitors", "Companyweb Owners", "Companyweb Members" and these are hooked through to Windows domain groups "Windows SBS SharePoint_VisitorsGroup", etc. I could try setting these groups up on my test server buth that would be a waste of time because WSS is tied to the groups on a specific domain.
I tried defining my local account as the owner of the site collection using the following command (note that my site is deliberately on port 8080):
stsadm -o siteowner -url http://testsvr1:8080 -ownerlogin testsvr1\Administrator
But this produced the error message:
Object reference not set to an instance of an object.
If nothing else we know that .Net is being used
I tried adding another local user account to the CompanyWeb Owners group using the command:
stsadm -o adduser -url http://testsvr1:8080 -userlogin testsvr1\abc001 -useremail blahblah@mycompany.com -group "CompanyWeb Owners" -username "ABC" -siteadmin
That resulted in:
Exception from HRESULT: 0x80040E14
Visual Studio's error lookup tool cannot find this code.
So, any smart person out there got any more ideas that I can try? I can't see anything else in the stsadm command set that looks like it might help, but I can miss stuff...
Michael