Access Denied error when entering survey

Posted on March 30, 2011 by Alisa Whitley

After creating a custom survey or list, users get “Access Denied” error when trying to complete. The error is received when clicking on “Next” if branching is enabled, or when clicking on “Finish” if branching is not enabled. The user has minimum of “contribute” access on the list, but still receives “Access Denied” error.

 
 

This error is received when the user does not have permission to create or edit responses. To resolve, click on Settings > Survey Settings > Advanced Settings, then under Create and Edit Access select Create responses and edit responses that were created by the user. The user should now be able to complete the survey without receiving the Access Denied error.

 
 

Filed under: Error, SharePoint 2010 | Leave a Comment »

SharePoint 2010 HTTP 1.1 200 error

Posted on March 30, 2011 by Alisa Whitley

HTTP/1.1 200 OK Server: Microsoft-IIS/7.0 Date: CurrentDateAndTime GMT Connection: close http://YourSiteName.com/

I received this error when I tried to browse to a newly created SharePoint 2010 site. Other newly created sites were responding as expected – only one was throwing this error. Searching the error returned several hits that were related to detaching and reattaching a database and a few other more complicated situations, but none that I could find were about the error on a newly created site.

After taking a looking in Central Admin, I realized that I had not created a top level site for this particular web app. That was the problem. After creating the top level web app, the site responded as expected.

I realize this was a simple issue to resolve, but the lack of any hits regarding the error with a new site prompted me to do a blog entry to possibly save someone else some time. So, if your site is a newly created one and you get this error, make sure your top level site exists. If it does and you’re getting the error, you can continue on with the other recommendations for the more complicated issues.

Filed under: Error, SharePoint 2010 | Tagged: , | 3 Comments »

Error enabling 2010 visual upgrade

Posted on February 13, 2011 by Alisa Whitley

You attempt to do a visual upgrade to a MOSS 2007 site that was upgraded to SharePoint 2010 and you get the error:

“Visual Upgrade failed. The default master page for this user interface could not be found at “/teams/xxxxx/_catalogs/masterpage/v4.master”. Add the requested master page at this path and try again.”

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: a4ead41e-8c93-4d9d-ae0e-580902b71714

The problem is that SharePoint is looking for a masterpage that isn’t in the master page library. This missing masterpage is usually the v4.master page.

To add the v4.master page to the library:

1. Go to the upgraded 2010 site, and create a subsite

2. Download a copy of the v4.master page. (Site Settings > Galleries > Master Pages)

3. Go to the top level site (or any site where the error is) and upload the copy of the v4.master into the master page gallery. (Site Settings > Galleries > Master Pages)

4. Try the visual upgrade again.

Once the v4.master page is added to the master page library, the visual upgrade to the SharePoint 2010 look and feel should work.

Filed under: Error, SharePoint 2010 | Tagged: | 2 Comments »

Business Data Connectivity Metadata Store is currently unavailable / There is no Business Data Connectivity Service associated with the current web context

Posted on February 13, 2011 by Alisa Whitley

When accessing External Content Types in SharePoint Designer 2010, the error “The Business Data Connectivity Metadata Store is currently unavailable” was received.

When clicking on New External Content Type the error “There is no Business Data Connectivity Service associated with the current web context” was display.

The BDC service was started in Central Admin. The service application was also showing as selected in Central Admin >Manage Web Applications > Service Applications.

Since the web app was using the default associations, I tried creating a custom group from the dropdown and selected all the service applications.


Returned to SharePoint Designer 2010 and the External Content Types displayed.

Clicking on New External Content Type no longer gave an error and page to manage external content types displayed.

 

 

 

Filed under: Error, SharePoint 2010 | Tagged: , , | 10 Comments »

SharePoint Designer 2010 error – List and Libraries “No items to display”

Posted on February 13, 2011 by Alisa Whitley

You have a SharePoint 2010 site that was migrated by the database upgrade method from MOSS 2007. The site has several lists and libraries. You open the site in SharePoint Designer 2010, click on List and Libraries in the left navigation, and instead of seeing all of your list and libraries, you get a message saying “No items to display”. When opening the Lists and Libraries of sites created in SharePoint 2010 you do not receive this message.

 

Most answers that I found online to this problem indicated a hotfix was needed for the server. This may be true if you are getting the “No items to display” message on all of your sites, regardless of whether they were upgraded or created in SharePoint 2010. My servers already had the hotfix and I was only getting the message on one upgraded site. Other site’s Lists and Libraries opened fine in SharePoint Designer 2010.

 
 

I consulted my friend Woody Windischman (co-author of Beginning SharePoint Designer 2010) and he suggested checking the Site Collection Administrators on the upgraded site collection since it was upgraded from MOSS 2007. I checked and the Site Collection Admins were different than the empty top level site and other sites that I was not having problems with. I changed the Site Collection Admin to the SP2010 accounts and still got the error when trying to access Lists and Libraries in SPD2010.

 
 

Woody also suggested that the original root collection of the site might by blocked by the default one in the new web application, so I tried deleting and recreating the top level root site – everything started working!

 
 

Thanks for all your help Woody! Woody has a lot of great info on his SharePoint blog, The Sanity Point. You can also follow him on Twitter, @woodywindy, and on FaceBook, for lots of helpful SharePoint info.

 
 

 
 

Filed under: Error, SharePoint 2010 | Tagged: , | 8 Comments »

Creation of Project Server PWA instance fails, timer jobs, clearing the cache….

Posted on October 26, 2009 by Alisa Whitley

I recently attempted to create two new Project Server PWA instances through Central Admin on a MOSS 2007/Project Server farm. I went to the SSP and clicked on Project Web Access Sites under Project Server. I then clicked on “Create Project Web Access Site” and filled out all the required information, including unique database names for the new site. The creation of the site would start, then it would spin and spin and spin….after a few minutes it would fail with a message saying “Failed – check Event Logs.”  The event logs showed no errors. Nothing at all related to the PWA instance failing.

The ULS logs did show errors indicating two of the three servers in the farm were trying to update the SSP and were causing conflict. There was nothing else to indicate what was causing the error.

I searched the internet and found nothing that applied to our situation. As a matter of fact, there was very little on the error at all. There were a couple of posts about the binaries not being installed on the server that housed Project Server, but that was about it. MOSS 2007 was installed on the same server and I had successfully created PWA instances in the past.

After reviewing everything on the server to make sure there weren’t any problems, I got Microsoft involved. They told me that to prevent each server from having to make SQL calls to pull information from the configuration database, data is cached on the servers. Sometimes this data will become corrupt and have to be cleared out and rebuilt. The process for clearing the cache can be found here.

Although the article states it resolves issues with timer jobs failing and does not state this will resolve the issue of PWA instance creations failing, it did do the trick. After the steps were followed new PWA instances could be created without errors.

I did a little more research on timer jobs and found the PWASSPSubmitSiteCreationTimerJob is responsible for creating new PWA instances. Apparently this was the timer job the corrupted cache was interfering with.

Now there is an article that ties the failing of PWA instance creation to timer job failures and clearing the cache. Maybe it will save someone else some time. ;)

Filed under: Error | Tagged: , , , | 1 Comment »

Follow

Get every new post delivered to your Inbox.