My Sharepoint Musings

Been a while since i last updated my blog -- and i know, most people hate the "I am coming back" blog posts that people put up, so sorry for that in advance :) I have had some life changes in the past year - left a job, started a new one, started consulting, moved across the nation, been to several weddings, moved in with the girlfriend, ect. Now that it has all settled down i figure it is a good time to start blogging again! Now the direction of this blog will be changing a little bit. A departure from the sharepoint side of things for a little bit and into Project Server modifications and changes and answers to questions I have had to look up or figure out myself many times over now.  In the past 6 months i jumped into a new job and hit the ground running as they were freshly deploying project server 2010, and the consulting company they brought in simply did not meet the requirements they asked for by the time they left.   I have had the pleasure of deep-div

My new laptop, 2xxxx series HP Envy 17 3D has a small problem if you update the ATI graphics drivers, namely: the Brightness hot keys stop working. What to do? Well step in www.Notebookreview.com forums, and the HP Envy 17 (2xxx) series Owners Lounge and a work-around pointed out by Fiver5- Fiver5 pointed me to a display brightness gadget over at edgylogic - Who happen to also share his source code for his console application, this combined together with AutoHotKey , and we have brightness functions working again! Woot! But now for the point of my post - tweaking! The console application allows you to set the brightness value of the screen with a command line argument, but does not allow you to increment up and down automatically... Pretty simple fix, just need to add two command line arguments to the console application, and then change the window behavior to not display the console when the application is launched: Here's the additions to the original code, not the clea

This is more of a "Coming soon" than it is a detailed post on my next post here. I am going to be making a series post on my experiences trying to solve a problem that I should not have had to solve in the first place: Getting an auto-generated table of contents for sharepoint 2010 Enterprise Wiki Sites. The journey is quite a tale, everything from searching the myriad of solution providers to the scouring the deepest depths of codeplex. Ok maybe not that interesting but it was very puzzling that i could not find a solution to a very basic wiki function. One that should be already included in sharepoint enterprise wiki's to start with! The solution i will be posting about isn't the one i am putting into production but one people can make themselves quickly and easily. It uses JQuery and a plug in, and then some sandbox code to deploy it to a site, and another quick one to put JQuery onto your server farm (I may just point you to smarttools.jquery solution instead how

Just a FYI since no one knew this from what i can tell already: If you are enabling BCM (Backwards Compatibility Mode) for project 2007 to connect to Project Server 2010, there are a few things you should know first. Right off the bat, clients have to be updated to Service Pack 2 . Next, when your setting up your project server, Note this key fact I could not find anywhere, and did not get hint about in the technet forms when i posted about my problems: You CAN NOT use Claims based authentication on your web application that is hosting Project Server 2010. The 2007 Client will not connect to the server. The 2010 client will connect with no problems. Quick and dirty, hope that helps everyone!

I'v had this solution for a little while now but never wrote it down anywhere for people to see. Here is the situation: In a site collection, you make a new list/document library in any sub-site or the main website. You then add a new item/document to the folder, and then attempt to edit the item You then see something along the lines of "Access Denied" , even if you are on the system account. This happens with every new list you create on any site or subsite. Your problem is a corrupted field definition at the site collection level. Specifically the "Effective Permissions Mask" is missing an attribute in it's xml scheme - RenderXMLUsingPattern="TRUE" The fix comes in 3 steps: 1. Update your server to the most recent cumulative update package (Service pack 2 or greater). You can get more information about this from the Sharepoint team blog post on SP2 . Included in SP2 is a hotfix that prevents this from occurring ever again on any other site co

So i have been slacking lately on updating this blog and well, i decided to resolve that now! So today i had an error with an application template on my micrsoft sharepoint moss 2007 server. This came up when i tried to resolve an issue in the bug tracking site template provided by microsoft. Every time i clicked on the yellow button, i got the following error: The resource object with key 'ResolveBugPageTitle' was not found." After some looking around the community, i found this resolution worked perfectly for me: Just type stsadm -o copyappbincontent You do not even need to retract and rebuild sites effected by the problem, after typing the copy command everything starts to work again! Hope this helps other sharepointers!