We had a custom master page installed where we made minor modifications but we knew should have worked. We created the Records Center site after applying this master page, and most everything worked, except this page. We managed to resolve it by resetting all of the sites master pages to v4.master, opening up the Records Center Management page, and then resetting them all back to our custom master page. (NOTE: if you're on a site without publishing features enabled you can just add /_layouts/ChangeSiteMasterPage.aspx to the end of your site's url to get there)
A resource for tips and solutions involving SharePoint and .NET Development
Monday, February 24, 2014
An error occurred during the processing of rcconsole.aspx Code blocks are not allowed in this file.
When in a Records Center site, I was trying to to Manage Record Center via the Site Actions menu but I was getting the following error message:

We had a custom master page installed where we made minor modifications but we knew should have worked. We created the Records Center site after applying this master page, and most everything worked, except this page. We managed to resolve it by resetting all of the sites master pages to v4.master, opening up the Records Center Management page, and then resetting them all back to our custom master page. (NOTE: if you're on a site without publishing features enabled you can just add /_layouts/ChangeSiteMasterPage.aspx to the end of your site's url to get there)
We had a custom master page installed where we made minor modifications but we knew should have worked. We created the Records Center site after applying this master page, and most everything worked, except this page. We managed to resolve it by resetting all of the sites master pages to v4.master, opening up the Records Center Management page, and then resetting them all back to our custom master page. (NOTE: if you're on a site without publishing features enabled you can just add /_layouts/ChangeSiteMasterPage.aspx to the end of your site's url to get there)
Thursday, January 16, 2014
Publishing Nintex Workflows gives a “This workflow already exists” error.
If you’re trying to publish a Nintex Workflow and you get
a message saying they already exist, yet you don't see them in the UI, just open up SharePoint Designer and delete
them in two spots: 1) The Workflows list, and 2) Under All Files
-> Nintex Workflows.
Nintex Workflow stuck in “Starting” state
If you find your Nintex workflow never leaving the "Starting" state, set the value in the Form Library settings: ‘Require documents to be checked out before
they can be edited’, to “No”. This is a known
Nintex bug: http://connect.nintex.com/forums/thread/29961.aspx
Thursday, June 27, 2013
List View Error: "Attempted to use an object that has ceased to exist."
I was copying a SharePoint list from 2007 to 2010, and all appeared well until I clicked on the List View, which gave me the following error:
I could see the items just fine using Site Manager, but everytime I looked at a view I would get the above error.
From looking in the logs it pointed me to check my List View Threshold, which I had happened to exceed. So going to Central Admin and raising the threshold for my web application did the trick.
Attempted to use an object that has ceased to exist. (Exception from HRESULT: 0x80030102 (STG_E_REVERTED))
I could see the items just fine using Site Manager, but everytime I looked at a view I would get the above error.
From looking in the logs it pointed me to check my List View Threshold, which I had happened to exceed. So going to Central Admin and raising the threshold for my web application did the trick.
Downloading InfoPath Form .XSN from SharePoint
I'm posting this when you need to download the latest InfoPath form for editing directly from SharePoint and can never remember where to find it. Not saying that it happens to me often, but it might.
- Go to the list where the InfoPath form is published.
- Click on the Library tab in the ribbon, and click on Library Settings
- Go to Advanced Settings
- In the Document Template section, underneath the Template URL, click on the Edit Template link.
Thursday, March 21, 2013
Rich Text Editor Stripping Absolute Urls
If you're using a Multiple lines of text column and select Rich Text, SharePoint turns any absolute urls that point to the server into relative urls. I've had cases where I'm referring to that text from other web applications, and I've found the easiest workaround is to just use a TinyUrl...
Thursday, January 10, 2013
SharePoint "Validation of viewstate MAC failed"
I had a button on a SharePoint page and was posting back to the page with the ID of the item I was using, so my page was: /Pages/Order.aspx?ID=5 and I kept getting the following error:
"Validation of viewstate MAC failed"
After toying around a bit I realized that the ID parameter is a reserved querystring parameter and can't be used, so just changing the name of the parameter fixed the issue.
"Validation of viewstate MAC failed"
After toying around a bit I realized that the ID parameter is a reserved querystring parameter and can't be used, so just changing the name of the parameter fixed the issue.
Subscribe to:
Comments (Atom)