I was trying to provision a site under Web Databases categories (Assets Web Database, Charitable Contribution Web, Contacts Web Database, Issue Web Database, and Project Database) and every time I got the following message:
Preparing Site ...
Someone has recently made changes to this site and the site is being updates. If the site remains offline for an extended period if time, contact a site owner.
Wait a moment and refresh your browser.
I have tried the steps provided in the following Blog and it kinda worked, however, when I provisioned the site I got the following error in the middle of the newly provisioned site:
"Access Service is unable to process the request. click here to try again"
In my scenario I used the manual way to provision the Access Services using a dedicated application pool. I have tried different account and even used farm service account to no avail. Finally, I got it to work by using the configuration wizard.
Not sure why by running the configuration wizard resolved the issue, but I will need to investigate the issue further once I have the time.
Monday, November 15, 2010
Tuesday, October 12, 2010
"Add document" link is missing after migrating document libraries from SharePoint 2007 to SharePoint 2010
After we had migrated from SharePoint 2007 to SharePoint 2010 we noticed that some document libraries didn't have the Add document" link and the small tick box. The following screen shots show comparison between a working and non-working document library:
Working Document Library:
Non-working Document Library:
At this point, the quick fox was to create a new standard view and make it as the default view. I will try to investigate the issue and update the post.
Working Document Library:
Non-working Document Library:
At this point, the quick fox was to create a new standard view and make it as the default view. I will try to investigate the issue and update the post.
Wednesday, August 18, 2010
A single user gets "Access Denied" on SharePoint Site
I came across permission issue, were only a single user gets "Access Denied" on SharePoint site. The user was able to access the site (his was added to the Visitors group) for one day, then all of a sudden he cannot access the site. I checked his permission and I could not see any reason for this user to get the error. I even tried to give him full control and that didn't work. I have created a new site collection and added him as a Visitor and he could access the newly created site collection. Since troubleshooting permission issues are difficult, I did download third party tool (i got the 14 days trial version) and installed it on a development machine, then moved the site to the development farm and the user still got the access denied error. I ran the tool and could not see any special permissions. So after further trials and errors, I came to the following resolution:
1. Added the user to the Site Collection Administrator (SCA) group, and now the user is able to access the site without issues.
2. Removed the user from the SCA group and that removed all his permissions, and he got the access denied error.
3. Added the user back to the Visitors group and now he could access without issues.
Not sure why the above steps fixed the issue, but I suspect by adding him to the SCA group and removing him, which remove the user's permissions from all SharePoint objects, and by adding the user again is like adding him for the first time. I guess at this point we will have to wait and see if the user runs into this issue again.
1. Added the user to the Site Collection Administrator (SCA) group, and now the user is able to access the site without issues.
2. Removed the user from the SCA group and that removed all his permissions, and he got the access denied error.
3. Added the user back to the Visitors group and now he could access without issues.
Not sure why the above steps fixed the issue, but I suspect by adding him to the SCA group and removing him, which remove the user's permissions from all SharePoint objects, and by adding the user again is like adding him for the first time. I guess at this point we will have to wait and see if the user runs into this issue again.
Subscribe to:
Posts (Atom)



