Dev Team Assemble » error

Variations Failed: An error was encountered performing this operation. You may re-try the operation…

Calvin — Fri, 30 Oct 2009 20:16:27 +0000

So I got this error the other day when putting together a dev site collection usign varations:

An error was encountered performing this operation. You may re-try the operation, and you may need to clean up the half-created data first before re-trying. If the problem persists, please contact your system administrator

This was actually a fairly easy fix for me. I simply had to enable the publishing features in my site. Which is funny...because they should have been on but I must have overlooked that.

Technorati Tags: Configuration, error, moss 2007, SharePoint, variations

503 Error SharePoint – Service Unavailable

Calvin — Wed, 09 Sep 2009 03:32:28 +0000

I started getting this error recently on my development box after I started using WSP Builder. I really like this program but I was a little put off by this error. Obvisouly it is recycling the worker process or something along those lines (too lazy to look it up). I am fine with it when it comes back online after a few seconds but I was having instances where it was hanging there...stuck in 503 limbo.

Turns out the problem is the application pool is stuck in a stopped state and the fix is simply enough to restart it.

Technorati Tags: error, IIS, SharePoint, wsp builder

Error: Adding Web Part to a page

Calvin — Sun, 26 Jul 2009 19:45:48 +0000

I got the following error the other day (it has been shortened...):

"the web part you attempted to add no longer exists in the closed web parts gallery."

This was a pretty disturbing error...there was no real apparent cause for this problem...nothing in the logs. After messing about with it for a while I figured out that it was a dll version in the GAC that was causing the problem. On my dev box I had an updated version but the version in our prod envs is different.

It would be nice if the server was a little more helpful with its error messages....HTH if you come across it

Technorati Tags: controls, error, gac, SharePoint, web parts

SharePoint – Unexpected Error

Calvin — Sun, 26 Jul 2009 19:43:22 +0000

If you are like me and have experienced this amazing error...here is how you can pinpoint the problem....change the SafeMode tag in the web.config file to enable the CallStack attribute

Then turn the customErrors mode to OFF. This should help you determine the problem.

Technorati Tags: ASP.NET, Development, error, SharePoint

SharePoint and its so called Designer…ARRRRRGGGGGHHHHH

Calvin — Sun, 26 Jul 2009 19:19:02 +0000

I have never in my life dealt with or had the "pleasure" of using a tool quite like Sharepoint Designer. First off I am a developer...so can they roll this thing into Visual Studio already? maybe then it will behave like my usual IDE...you know intellisense, fade away tool boxes and solution explorer. (Some of these issues are sharepoint itself but...this app is where i figured it out so i am adding it here)
So what makes me hate it?

...hmm did you know that you have to leave the ListFormWebPart on all the edit, insert and display forms for a list even if you want to customize them? Seems kind of odd to me and quite frankly where is this documented...shouldn't SPD at least say something to that effect...or dammit MS add it as a comment on the page somewhere.

...how about leaving my HTML code alone when i am done formatting it please!!!! Its like I am working in VS2002 again...no thanks

...the CustomListForm web part does not give you the ability to attach files...even though its right there on the toolbar it gives you the nice "You cannot attach a file because the form was customized". Thanks captain obvious...I think this is one of those sick jokes where every time you click on it a counter in Redmond increments by one and some sick developer is there laughing his ass off...heres to you buddy! Kudos to Marc Davis for his workaround posted here

...isn't it funny how the css file core.css is always the last css added to the list. Sure you can bypass it with the Alternate stylesheeet and/or using a hard coded link tag...but that just seems dumb to me.

...can I have an easier way to develop and debug code in sharepoint...sure I know I can build, deploy to the GAC and attach....but its a bit of a pain in the ass.

...Customized file and uncustomized files. Yes i get the gist of it and i believe this is a good thing....scenario - I have made numerous edits to a file - I choose to revert to the site definition - I don't get my original file back...I get some hybrid bastardized file that is completely useless to me...ummmm....again...not funny.

- I had a problem with one of my lists (pertaining to the ListFormWebPart not being there) and I was looking around on the internet...here is what I found this article here you can read it if you want but it basically says hey...just delete your list and recreate it....HA HA HA I love those simple "fixes".

...theres been other things but I cant remember them right now....too tired.

So these are my ramblings...I am kinda stuck with SharePoint now but if they could fix some of these very-time consuming problems it would make mine and judging from the problems people are having online a lot of other peoples jobs a lot easier. I mean isn't that what Microsoft has been promising all this time...

I'll stop now...happy SharePointing.

Technorati Tags: Development, error, SharePoint, SharePoint Designer

SharePoint Inline Code

Calvin — Sun, 26 Jul 2009 18:56:58 +0000

Inline code is disabled in sharepoint 2007 (not sure about SPS 2003) with the exception of files in the _layouts directory and will throw an error. I was researching this a while back and thought I would throw it up here so I don't forget...maybe you can get some use out this article:

http://msdn.microsoft.com/en-us/library/bb862025.aspx

Essentially you need to add a PageParserPath entry to the web.config file for the web application

Technorati Tags: error, IIS, SharePoint

Access Denied – Enabling Publishing Features in SharePoint

Calvin — Sun, 26 Jul 2009 18:53:26 +0000

This is kind of of a weird error and it didn't make sense to me at first (still doesn't really). The best workaround I could find on the net was to temporarily change the application to run in the application pool of the central admin site.

Steps:

Change the AppPool for the app to be the same as the Central Admin site (Home Directory tab in IIS website properties).
Reset IIS or at the very least do an %systemroot%\system32\iisapp.vbs /a "apppoolname" /r (not sure if the iisapp.vbs method will work but cant see why not).
Activate the publishing infrastructure.
Set the app pool back to normal.
repeat step 2.

Enjoy!

Technorati Tags: error, IIS, Security, SharePoint