Posts Tagged ‘SharePoint’

h1

SharePoint: Adding a company logo

March 29, 2011

It shouldn’t take 2+ hours to figure out how to add a company logo to a SharePoint site! But that’s how long it took me the other day.

I’ve got SharePoint installed on my server (I think it’s SharePoint 2007, but as there’s no ‘branding’ that I can see, I have no idea which version it is). I wanted to set up an internal website in preparation for some software that I’ll be installing in the next few weeks that links into SharePoint. I’ve used SharePoint before, but way back in the early days. I found it very clunky to configure at the time, and, as a user of another company’s SharePoint 2003 installation, I found it incredibly hard to search because so much ‘stuff’ got dumped into multiple SharePoint subsites, it was hard to figure out where you were. I hated it.

So, into the breach!

I opened up my default SharePoint installation (http://companyweb) from Internet Explorer on my PC and went looking at the settings. I wanted to change the name of the site from CompanyWeb to CyberText and I wanted to change the default logo to my company logo. You’d think that would be easy, right? Well, changing the name was simple, but not the logo.

So for anyone else struggling to figure out how to do this, here’s what I did to get it to work. Note: Your version of SharePoint may have slightly different screen shots and wording to those below.

Change SharePoint site name

  1. On any page, click Site Actions in the top right.
  2. Select Site Settings.
  3. Click the Title, Description and Icon link.
  4. Enter the new name in the Title field, then click OK.

That’s the easy bit. Changing the logo is not so easy…

Change logo

  1. Repeat Steps 1 to 3 above, and leave Internet Explorer open at that page — you’ll come back to it in Step 7.
  2. Find the image of the logo you want to use and either copy it or put it on a thumb drive.
  3. Now, go to the server where SharePoint is installed. You may need your admin person to do this. I have my own server, so I just went in via Remote Desktop.
  4. On the server, open Explorer (right-click on the Start button).
  5. Navigate to C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/TEMPLATE/IMAGES. Please note: If you’re using SharePoint 2010, you will see a 14 folder instead of 12 — select 14.
  6. Paste your logo into the IMAGES folder. You’re finished with the server now.
  7. Go back to your PC and, in the URL field on the Title, Description and Icon page, type /_layout/images/<name of the image file you just pasted>
  8. Click the Test link to make sure the logo displays, then click OK.

Thanks to Nik Patel for pointing me in the right direction: http://nikspatel.wordpress.com/2010/08/07/sharepoint-site-logo-url-limitations-site-pages-vs-web-part-pages/

It really shouldn’t be that hard! Why isn’t there a Browse button next to that field? Why can’t you insert an image object into SharePoint, then link to that object as the logo? Why do you have to copy the image file to a server location manually?

BTW, I don’t like CompanyWeb as the URL, but changing it looks like a nightmare for someone who isn’t a web admin person. Details here: http://www.sharepointnutsandbolts.com/2007/11/change-sharepoint-site-url.html

[Link last checked March 2011]

h1

IE7 crashes when open Office document in SharePoint

May 6, 2008

I’ve been using a client’s SharePoint 2003 for some months now, and have been swearing at its clunky workflow. My default browser is Firefox—as a result I can’t get all the extras for managing documents directly in SharePoint through it. So I’ve learned to open the client’s SharePoint portal in IE7. However, every time I tried to open an Office 2003 document within SharePoint (let alone edit one), IE7 crashed on me. Well, finally I had enough! I had two choices: continue feeding my SharePoint frustrations (and making the air blue as a result), or find the solution. Off to trusty Google and within minutes I had my answer.

It seems Office 2007 and Office 2003 and SharePoint don’t play well together. But, pondered I, I don’t have Office 2007 installed and have never installed it on this machine, though I have installed the font compatibility pack. Perhaps that was it? Nope. In my case, it was the installation of Microsoft Expression some time back that added some Office 12 components to my system—particularly this file: OWSSUPP.DLL. It seems if you have more than one of these beasties on your machine, IE7 can get tied up in knots and crash when you try to open an Office document in IE7. Who’d have thought? (DLL hell revisited, anyone?)

So on the advice of several websites, here’s what I did to fix the problem:

  1. Searched for all instances of OWSSUPP.DLL on my system. I found two—one under the Office 11 installation (expected), and one under C:\Program Files\Microsoft Expression\Office12.
  2. Went to C:\Program Files\Microsoft Expression\Office12 and renamed the DLL to original_OWSSUPP.DLL.
  3. Ran the Office diagnostics on my system to replace any old or missing OWSSUPP.DLL files with a new one from Microsoft (Start > Programs > Microsoft Office > Microsoft Office Tools > Microsoft Office Diagnostics). This process took a few minutes.

That was it! As soon as I’d done that, I checked the OWSSUPP.DLL file in the Office12 folder and it had updated with a recent one. I opened SharePoint and voila! I could open and edit Office documents within the SharePoint workspace. And I could stop swearing at SharePoint and IE7, at least for now.

Thanks to these websites for pointing me in the right direction:

Update 9 July 2008: IE7 doesn’t even report a crash now when I try to open a Word document via SharePoint—it just disappears entirely! I wonder if it’s to do with getting SP3 installed on my Windows XP machine last week? Following my own advice, I checked what I did last time (see above), searched for OWSSUPP.DLL and lo and behold I found TWO instances of it in C:\Program Files\Microsoft Expression\Office12 and one in my Office 11 folder. One in the Expression folder was the renamed file from last time, and the other was a clean instance. Now how did that get there?

I ran the Microsoft Office Diagnostics again. One issue was reported as found and fixed though there were no details as to what the issue was and what they did to fix it. So I’ll try again… But before doing so I’ll check that Expression folder again—yep, it’s back! This time I just deleted it from the Expression folder without running the diagnostics.

Then I opened SharePoint and tried to open a Word document—and it worked.

Now, to try and solve the problem once and for all… It seems there’s a fix for this problem which updates the OWSSUPP.DLL file in the Office 12 location to the latest version. You can read the details on the Microsoft Support website, and download/install the hot fix from there too; it appears to work: