Upgraded to Service Pack 2. Flyout menus don’t work.

Upgraded to MOSS Service pack 2 the other day. Seemed like a no brainer to me as we contemplate preparing for SharePoint 2010.

Upgrade went okay… Afterwards the flyout menus on all pages with our custom branding did not work!

Took a lot of searching to finally find an answer…

turns out the Core.js file has a line that says:
var flyoutsAllowed=false;

Change the false to true, and flyouts were working again!


Thanks to these guys:



Renaming SharePoint Servers

I made a virtual dev environment for SharePoint because visual studio demanded we have it installed on a SharePoint server if we wanted to make web parts with it and VSeWSS. That part went okay. Next step was either build 2 more from scratch for the rest of the team, or copy and rename the one I already built. I chose to copy and rename (don’t want duplicate machine names on the network).

The server was a MS virtual PC machine running Server 03 R2 x86, MOSS 2007, and SQL express 2005 (or whatever a standalone install of SharePoint installs).

Renaming the server is the easy part. So I changed my server name from spdev-old to spdev-new like it was NBD (don’t restart yet). Wasn’t sure how to make SharePoint know I made the change though…

As it turns out… that’s easy too! Yay!
win+r | cmd | Enter

then type:
stsadm –o renameserver –oldservername spdev-old –newservername spdev-new

If that command doesn’t work… then you didn’t add the 12 hive BIN to your system’s path, and you’ll need to change directories to the 12 hive before running the stsadm command. The command to navigate to the directory is:
cd %programfiles%/common files/microsoft shared/web server extensions/12/Bin

However, I recommend adding it to your path because stsadm is a handy tool that you will use a lot. 
To do this:
right click My Computer > Properties > Advanced Tab > Environment Variables > find “path” under system variables > edit
At the very end of the variable value add:
;C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

You can restart after the stsadm command completes successfully.
shutdown –r –t 00

Now we’re almost done… just need to change the alternate access mappings in SharePoint Central Admin.

Open Central Admin. It fails. Change the name in the address bar to the new name. It works, Congratulations!

Go to: Operations | Alternate Access Mappings

Click on each address and change it to the new name.

If the browser doesn’t respond when you click OK on changing the name… then add the new computer name to your intranet sites in internet options | Security tab.

Once you’ve changed all 3 applications to the new system name(Central Admin site, SSP site, and default site) you are done.

Some people had trouble with user permissions after that… I did not. If you do, you will need to update your farm admin username to reflect the new machine name.


Error 6482

Are your SharePoint error logs full of 6482?


Are your audiences failing to compile?

Did you try resetIIS and that only helped for a little bit, if at all?

Then you need Microsoft Hotfix 946517!!

Available now on web browsers worldwide!!

Get yours today, Click here!

Thanks to this thread: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/7aeab1ba-0b16-43ee-b0c0-aafcc90ae293


kickoff/registry hack

well. i hate writing intros so this won't really be one. but i just thought i should start out by saying hi. hi?

**awkward transition**

lately, i've been trying to figure out how to build web parts for sharepoint. almost every article/walkthrough i found referred to sharepoint tools in visual studio. visual studio 2010 (release candidate now available for download) has built-in tools for sharepoint development, and from what i can tell they look pretty cool and versatile. however, i wasn't able to "create" a sharepoint project in 2010 because i don't have a sharepoint server on my machine - and why would i? the other glitch was that the built-in tools are for sharepoint 2010, and i'm currently working with 2007.

new plan: i discovered that microsoft provides sharepoint extensions for visual studio 2008. when i tried installing, i got a similar error - no sharepoint services on my machine (which requires windows server OS). while searching online for a solution, i came across a brilliant registry hack that beautifully accomplished what i needed.

the idea here is to trick your machine into thinking it has sharepoint services installed, which will then allow you to install the visual studio extensions. it took about three seconds to perform, and worked like a charm. i haven't tested it on windows 7, but i know it works on xp and (apparently) vista.

here it is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0] "Sharepoint"="Installed"