25 September 2007

Why won’t my site Quick Launch navigation accept relative URLs?


OK, so you're trying to customize your site and then you try to add a relative URL to the Quick Launch menu.
You start by going to Site Action/Site Settings and then under the Look and Feel section, you clicked the "Navigation" link.


Editing the navigation as in this screen shot, you clicked "Add Link".




Now you try to add the relative URL as in this screen shot, but you get the error depicted. What gives?



Well, it's quite simple really. The answer is that you're editing a sub web of a Collaboration Portal. Collaboration Portal sub webs have different navigation functionality in the Quick Launch than normal Site Collection sub webs do.
If we repeat the process, but this time on a Site Collection sub web instead, it would look like this…
We'd start off with Site Actions/Site Settings again, but this time in the Look and Feel section the link won't be called "Navigation", but rather "Quick Launch".



Editing the menu you'll see a much different interface:



And adding a relative URL is fully supported as can be seen here:



Of course, that leaves you begging the question, so how do I change one site for the other?
Actually, that's easier than you may think, provided you have a top level site collection to house the sub web.
Simply follow these steps:
  1. Save the sub web as a template.
  2. Download the .stp file from the Site Template Collection library.
  3. Navigate to the target site collection root site.
  4. Through SA/SS access the Site Template Collection library.
  5. Upload the .stp file to the library.
  6. Create a new sub web using the newly uploaded template.
That's it. SharePoint will provide the new interface to the Quick Launch automatically which should allow you to create your relative links.
Later
C

24 September 2007

WSS 2.0 SP 3 available NOW!


OK, if you have not taken the leap to WSS 3.0 yet (why not?), then you'd probably want to get SP3 for WSS 2.0.
It is available now from Microsoft downloads at:
Later
C

Cowboys & Colts keep rolling, Bears are soft, Lions back in form, Patriots crowned WAY too early!

OK, it’s week 3 in the NFL and I just have to get some things off my chest…
COWBOYS DOMINATE
The Cowboys torched the Bears last night. They always seem to start slow in the first half, but then explode in the second. I’m not going to crown them a Super Bowl contended any time soon, but Tony Romo is the real deal and the ‘Boys look good.
COLTS KEEP ROLLING
Peyton Manning and the Colts just keep on doing what they need to do to keep winning. The Colts D looks much better than last year during the regular season and even though they’re not blowing people out, they keep winning. That was the same situation last year when the Colts were flying under the radar late in the season. Nobody, and I mean NOBODY, picked them to win it all. Instead, all you heard was “They’ll lose in the next round”. But they never did and took home the trophy. This year, nobody’s picking the Colts to repeat, which is just the way they like it. Keep ignoring the Colts and keep picking the cheaters, er… I mean Patriots to win it all. Time will tell…
BEARS ARE SOFT
Sorry Scott, but either the Cowboys are extremely tough and hard on opponents, or the Bears are soft. Yeah, you heard me. I said it. The Bears are soft. How do you explain losing LB Lance Briggs, CB Nathan Vasher, DT Tommie Harris and G Ruben Brown all to injury! All Pro-Bowlers too! I think the Bears are about to self destruct. I have great respect for Lovie Smith, but if he doesn’t draft a QB this coming off season, he can kiss his team goodbye. That’s if the Bears don’t self destruct before the end of the season. I understand backing your man Rex, but even the most optimistic of people eventually stop backing a losing horse. Grossman’s days are numbered and if Lovie ties himself to that anchor, he’ll go down with him. I wouldn’t want to see that because I think Lovie has done some great things in Chicago. I guess we’ll see when the draft comes…
LIONS BACK IN FORM
Well, I see the Lions are back in form. (Sorry Chris!) They just go pummeled yesterday by, an embattled QB and an average team. Ouch! But then again, they beat the Raiders and Vikings in their first two games. And people got excited about THAT! Come on people! I figure the Lions will do better this season than last, but I still don’t put then much beyond maybe a 7-9 team.
PATRIOTS CROWNDED WAAAAAY TOO EARLY!!!
OK, so it’s no secret I can’t stand the Pats. So obviously, my opinion is a little tainted, but come on people! The talking heads on NFL Network are already crowning the Patriots as Super Bowl champs, UNDEFEATED no less! WHATEVER! Let me see, we’ve played how many games? Oh yeah, that’s right… THREE!!! That’s not even 1/5 of the games yet! And they’re already being crowned champs?! We had the same thing happen with the Bears last year and it sure worked for them! What is really rubbing me the wrong way is the fact that people are saying the Pats are going to go “undeafeated”! Mmm… last time I checked, they still had to beat a very hot Bengals team, IN Cincy! Oh, and don’t forget that in week 6 they have to travel to Texas Stadium and try and dispense the Cowboys! Good luck with that one… But wait, that’s not all… in week 9, they have to go on the road to Indy to face the CURRENT, DEFENDING CHAMPION Colts! If that’s not enough, Peyton has OWNED the Pats over the last couple of years! Ever since he snapped that losing streak in NE, he’s had their number every year! Then in week 13, the Pats again have to go on the road and face the Ravens, and the next week, they host the Steelers who’s looking mighty good too!
No, no, no my friends… crowning the Patriots with an undefeated season this early is a mistake. Besides, if I’m wrong and the Bears are NOT soft, but instead the Cowboys are just very rough on opponents, then I’d be looking forward to some major injuries on the Pats roster in week 6.
OK, so I’ve got it off my chest… now… are you ready for some football! BRING ON THE SEASON!!!


Cheers
C

Don’t panic! Site migration disparity is an elution…

OK, I’ve spent the last year of my life buried in SharePoint migrations. I’ve learned many, many things and even wrote my “Step-by-Step – A REAL world upgrade of a SharePoint Portal Server 2003 (SPS) farm to Microsoft Office SharePoint Server 2007 (MOSS)” document to help others out who had to fight through the process. One thing I had not noticed before but just picked up on is related to WSS site migrations. If you look at the following screen print…


092407_1342_DontpanicS1

You will notice that the WSS site in question has two document libraries, General and Protected. There are 83 items listed in the General library and only 1 item in the Protected library. After migrating this site to WSS 3.0/MOSS 2007, and selecting the “View All Site Contents” link, I noticed the following…


092407_1342_DontpanicS2

As you can see, on the migrated site, SharePoint is reporting 117 items in the General library and 18 in the Protected library. This really perplexed me so I dug a little deeper. I refused to believe that there was a problem with the migration process and that I might be losing data… I was right.
As it turned out, WSS 3.0 reports folders as Items too! ðŸ˜‰
So, in this case, where the Protected library contains 1 document and 17 folders in its folder structure, WSS 3.0 is reporting it as 18 items whereas WSS 2.0 reported it as only 1 item.
So, if you run across this, never fear. The explanation is simple enough…


Cheers
C

19 September 2007

WSS 2.0 SP 3 available NOW!


OK, if you have not taken the leap to WSS 3.0 yet (why not?), then you'd probably want to get SP3 for WSS 2.0.
It is available now from Microsoft downloads at:
Later
C

04 September 2007

SPS to MOSS migration error - Cannot locate the list definition required for upgrade


If you're migrating a SPS 2003 portal to MOSS 2007 that has customized area definitions, you'll have to revert all those are definitions back to a standard are template before the migration would be successful.
After installing MOSS and running the PRESCAN tool you get stuck with this nasty error message:
09/04/2007 15:01:16 Cannot locate the list definition required for upgrade. Check to ensure you have all templates and language packs installed.
09/04/2007 15:01:16 Error: Exception scanning web: http://SERVER/Annual Enrollment
09/04/2007 15:01:16 System.IO.FileNotFoundException: The system cannot find the file specified.
at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateSchemaAllListsOfWeb(String bstrUrl)
at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPWeb(SqlConnection connection, String vsUrl, SPVirtualServer vs, SPSite site, SPWeb web)
The problem here is that PRESCAN cannot find the definitions of the areas that are specified in the database. You need to also restore the original WEBTEMPSPS.XML file to the \60\TEMPLATE\1033\XML folder before PRESCAN would run successfully.
Later
C

SPS to MOSS migration error – Cannot locate the list definition required for upgrade

If you’re migrating a SPS 2003 portal to MOSS 2007 that has customized area definitions, you’ll have to http://support.microsoft.com/kb/555858 revert all those are definitions back to a standard are template before the migration would be successful. After installing MOSS and running the PRESCAN tool you get stuck with this nasty error message:
09/04/2007 15:01:16 Cannot locate the list definition required for upgrade. Check to ensure you have all templates and language packs installed. 09/04/2007 15:01:16 Error: Exception scanning web: http://SERVER/Annual Enrollment 09/04/2007 15:01:16 System.IO.FileNotFoundException: The system cannot find the file specified. at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateSchemaAllListsOfWeb(String bstrUrl) at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPWeb(SqlConnection connection, String vsUrl, SPVirtualServer vs, SPSite site, SPWeb web)
The problem here is that PRESCAN cannot find the definitions of the areas that are specified in the database. You need to also restore the original WEBTEMPSPS.XML file to the \60\TEMPLATE\1033\XML folder before PRESCAN would run successfully.


Cheers
C

SharePoint Remote Event Receivers are DEAD!!!

 Well, the time has finally come.  It was evident when Microsoft started pushing everyone to WebHooks, but this FAQ and related announcement...