A Site owner of a Sub site cannot save any list as Template gets Access Denied.

I am working with a new organization now and we deal more in the user interface then the server side and you know what its definitely a learning experience when you stand at the other side, we truly ignore what would an action on the server result at the users end and it a great learning curve here.

From now on my posts will me more of client specific rather then server because not everyone using SharePoint has an access to server but they do have issues
Most of the users face “Access Issue” we as administrators inherit and break permissions, play with the item and list levels and it some times does impact the customers the issue I had recently was


A Site owner of a Sub site cannot save any list as Template gets Access Denied.


Here we have a site collection with site admins and we have some sub sites under it, every sub site is governed by different site owners (and admin’s as well but they do not step into another territory)

When a site owner tries to save any list as template he gets AcceSS denied

The issue lies with the List template gallery in the Main site o look at that logon to main site > site actions > site settings > Galleries > List template gallery

We saw that the Site collection admin was running it with unique permissions and the site owner for the sub site was given Read access out there

We then added him as contribute on list template gallery and it fixed the issue for us

1. On windows 2008 servers we installed the Desktop experience feature and started the web client service


2. Then we went to the IIS 7.0 manager page

3. On the Module section we removed the WebDav module

4. Explorer view started working on the windows Integrated sites

5. but not on FBA , we noticed via fiddler that site was running into authentication loops when browsed with FBA

6. while signing in the browser on FBA we checked the Checkbox ""sign me in automatically "

Explorer view gives "Internet Explorer Cannot dispal this webpage" on Server 2008

Search does not work for me since I splitted the indexer and the query server

I came across a rather interesting problem yesterday,
I came to know that we were not able to search the portal site since we decided to have a dedicated Search server in the farm.

The environment was
1 Application server 32 BIT Windows Server 2008 also running search query service
1 Search server 32 BIT Windows Server 2008 running Search Indexing Service
1 Database server which was SQL 2005
Interesting catch was that everything was running under FQDN

The search started getting rude to us since we added a search server to the farm and gave it an Indexer role. also the search was set crawl all the Dedicated WFE (which might not be a good idea)

First thing you have to check is the Crawl logs, which might give you a better direction, mine gave me error as - could not access the url
The site was browse able on the client and the application server
we RDP'd to the Index server and tried browsing the site & it did not show up
Tried pinging, tracert, nslookup; no response- by this time we were sure that it was a network problem

What's the catch ?

The Domain Controller was running on Windows Server 2003, which means IPv4 we saw that Sharepoint was running on Server 2008 which is IPv6.
when you give role to a server as Indexer it writes entries to the host file with the url of the sites and from there we saw that it was IPv6
we disabled the IPV6 networking layer on Sharepoint and the sites were now browseable and searchable
checkout the following links to support that :

http://support.microsoft.com/kb/215383
http://technet.microsoft.com/en-us/library/cc748826.aspx


Golden Point to remember:

Incase you have separate Query and Index server in the farm make sure that the site should be up and browse able on the Indexer server

"The path for the index location is not valid"

"The path for the index location is not valid"

I recently faced this issue with the Sharepoint on the Central administration page that gives "The path for the index location is not valid" error message on the Manage search settings page on Application management

Reason:
================
The problem occurs when you have changed the default location of the index file path

Resolution:
================

+ Either you can try bringing the index location back to where it was
+ Try stopping and starting the Osearch service give it the new location, and start it again, to do this make command line your friend.
+ To stop and start WSS search with command line use http://technet.microsoft.com/en-us/library/cc288507.aspx
+ To stop and start Office search with command line use http://technet.microsoft.com/en-us/library/cc262920.aspx
+ Try giving WPG group as full permissions on the index file location folder
+ Also give permissions to the C:\windows\tasks folder
+ As its a system folder and it will not give you permissions to edit the attributes on the command prompt run attrib -s C:\windows\tasks the go to security tab and add permissions and then again on command prompt run attrib +s C:\windows\tasks, to get the system folder attributes in place


Assume that the new index location you have provided is Drive D,
so go to the D drive and add the network service and the Worker Process Group (WPG) group as the following permissions listed

Permissions:

Traverse Folder / Execute File, List Folder / Read Data, Read Attributes, Read Extended Attributes, and Read Permissions

And I bet it going to work, if you are wondering why, this is because O search is controlled by a service named Office server web services and this service runs with the service account as Network service.

you can determine this from the IIS