If you can’t connect to your SharePoint server using SharePoint designer, one of the possibilities of what happened is that you have a remove tag added after after the add ScriptResource.axd. To solve try this:
- Use fiddler2 to determine issue. Download it from here www.fiddler2.com
- Check the error messages
- If you see access denied (http response code 401) to /_vti_bin/usergroup.asmx then it might be that you added AJAX support and the entries are in incorrect order in the web config
Description of the problem
<remove verb=”*” path=”*.asmx” /> is inserted automatically after <add verb=”GET,HEAD” path=”ScriptResource.axd” <add verb=”*” path=”*.asmx” validate=”false” type=”System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31BF3856AD364E35″/>
This Means the .asmx pages do not work on the sharepoint server after adding the feature. This also prevents you edit the site using sharepoint designer because /_vti_bin/usergroup.asmx will give a 401 access denied error.
The issue is here:
<remove verb=”*” path=”*.asmx” />
Simply remove the tag and it will work
Check out the resolution here http://features.codeplex.com/WorkItem/View.aspx?WorkItemId=6623
If you can’t create your my site in sharepoint and you are the admin, check the self service creation in the central administration
It can save you a lot of time.
You need to enable self service creation. To do so:
-Click Start -> All Programs -> Administrative Tools -> SharePoint Central Administration.
-Go to Virtual Server Configuration, click Configure virtual server settings.
-Click virtual server to enable on the virtual server page.
-Under Automated Web Site Collection Management, click on Configure Self-Service Site Creation.
- Then select On in the Enable Self-Service Site Creation section
Also, if you are deploying for the extranet you might consider hosting the sites under port 80 instead of the default 82. Check out this post by Chris Johnson on how to move your sites to port 80. http://blogs.msdn.com/cjohnson/archive/2006/09/15/754902.aspx. One note on this steps, please remember to browse to the newly create site for the my site host and click on “set as my site host”. And don’t forget to apply theme and master page.
If you are having trouble accessing your sites from the outside, also check the My Site trusted locations and finally don’t forget about the alternate access mappings.
Well… so many things required to set up my sites to work properly in SharePoint 2007….
If you are installing SharePoint and you bump into the issue that ASP Net v2.0 is not in the Web Server Extensions, then you could do a research and find out that you installed a newer version of the framework, namely SP1.
According to Microsoft, you need to uninstall SP1, install .Net 2.0 and then move from there: http://support.microsoft.com/default.aspx/KB/906894
Sounds a bit dumb
But don’t worry, go to
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727> or C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727> for 64 bit
Type aspnet_regiis.exe –i
A lot easier!