Blog purpose and direction

So i just started my new job as my company's "sharepoint guru" which so far involves administration, supporting, designing, redesigning of all of their sharepoint sites and infopath forms... which happens to span 3 different versions of sharepoint right now.

You heard me right, from STS to MOSS, they have sites running on them all, and the plan is to have me negotate, migrate, and set up all of the old systems to play nice on MOSS.

This is about when i should mention that i dont have previous sharepoint experince, or infopath. I do have a decade+ of webdevelopment experince as a part-time thing, but i have always stayed an arms length from microsoft products. And i am really starting to understand why as i start this long journey.

As i fumble and trip my way through sharepoint administration and yes, migration, i will update this blog in hopes that people who run into the same head-against-wall moments i have had allready, can side step them, and keep moving forward.

My next few blogs will be on the issues I am allready tackling:
  1. A WSS 2.0 single sharepoint site migration to an exsisting MOSS server farm, a real step-by-step type of instruction.
  2. A nasty issue i have allready been presented with the moss server's crawler not indexing one site that was converted over a long time ago, worked fine for a long time, and now broke in the past week. Technet hasn't really helped me much here
  3. Infopath! My anylisys of microsofts mind-boggling choices when it comes to infopath web services and what our choices were for it.
Ya i know, it's only been two weeks and i allready have a ton to blog on about issues that just took me too long to look up by themselves. Hopefully i can save other people their valueable time.. and hair looking for the answers.

Comments

Post a Comment

Popular posts from this blog

CI Build broke after nugit update

One of those moments where your heart drops : Your using CI on a remote hosting service (like AppHarbor) and your build fails. You look into the fail reason and find out it is because you updated the packages in your build. Wait, my update from nuGet broke everything?! Wtf?! The error looks something like this, putting it in here for search engine's : Build started 6/10/2013 12:30:20 AM. 1>Project "D:\temp\xly5bsff.qvp\input\.sln" on node 1 (default targets). 1>ValidateSolutionConfiguration: Building solution configuration "Release|Any CPU". 1>Project "D:\temp\xly5bsff.qvp\input\.sln" (1) is building "D:\temp\xly5bsff.qvp\input\\.csproj" (2) on node 1 (default targets). 2>D:\temp\xly5bsff.qvp\input\\.csproj(880,3): error MSB4019: The imported project "D:\temp\xly5bsff.qvp\input\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" was not found. Confirm that the path in th
Read more

Sharepoint 2007 - Access Denied when you try to edit

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
Read more

Project 2010 and Project Pro 2007

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!
Read more