I experienced a few problems today using our internal Microsoft Windows Small Business Server 2003 R2 server and it’s Sharepoint v2 implementation. The first issue was that files weren’t checking in and out properly – as when I checked a file out, Sharepoint didn’t recognise me as the correct user – instead flagging the file as being checked out by an odd variant of my own user account (i.e. ri**********@ne*******.uk instead of ri**********@ne********.com)
So I ‘phoned my “go to” guy for Sharepoint issues – Mr. Sharepoint himself, Andy Parkes. Conveniently, Andy was with fellow Sharepoint guru Vijay Riyait and both were on their way to a Sharepoint Seminar in London – and what’s more, Andy himself had tackled a similar problem to my own that morning!
The fix? Within companyweb, use the Site Settings menu > View Information about Site Users > Click Username > Edit User Information – where I updated the e-mail address of the account in question, and after logging off/on the workstation I was using, the correct Check In/Check Out procedure worked! Andy also suggests that deleting and re-creating the user account will also work if the above doesn’t.
Then I had to tackle some issues using Sharepoint v2 with Office 2007. Specifically when browsing to a companyweb Document library, no icons were being displayed for Office 2007 files, when you went to open those files from Sharepoint – Internet Explorer prompted you to save or download, and most irritatingly, you couldn’t edit those files directly from companyweb – the error…
“Server document: A newer version is available. To modify this document, open the latest version or save a copy”
… appearing every time.
Thankfully, the ever helpful Dave Overton had already drawn together all the bits of information I needed to fix these issues over at his excellent blog under the article “How to get Companyweb (Windows SharePoint Services v2) to work with Office 2007“.
The only things I’d add to Dave’s document are:-
- When the article refers to copying files to C:Program FilesCommon FilesMicrosoft Sharedweb server extensions60, do this on the server – not the client’s workstations experiencing the issue.
- Make sure to copy the relevant .gif files from one of the folders (gif-dark, gif-light) into C:Program FilesCommon FilesMicrosoft Sharedweb server extensions60TEMPLATEIMAGES to make sure 2007 (.docx, .xlsx, etc) files show a correct icon within companyweb.
- Also, stop/restart IISAdmin on the server after these changes to make them “stick”.
Huge thanks to both Andy Parkes and Dave Overton for their assistance – it’s really appreciated guys.
Richard Tubb is one of the best-known experts within the global IT Managed Service Provider (MSP) community. He launched and sold his own MSP business before creating a leading MSP media and consultancy practice. Richard helps IT business owner’s take back control by freeing up their time and building a business that can run without them. He’s the author of the book “The IT Business Owner’s Survival Guide” and writer of the award-winning blog www.tubblog.co.uk
All PostsYou might like:
Comments
2 thoughts on How to get Companyweb (Windows SharePoint Services v2) to work with Office 2007
UNKNOWN
29TH APRIL 2008 23:51:32
Richard, Can I ask the obvious question? Why are you worrying about Sharepoint V2 if you are looking to use it internally? I would think that you be better investing your time getting familiar with Sharepoint V3! Sure if you have clients using Sharepoint 2 I can understand but internally why would you even bother? Sharepoint 3 has all the features of Sharepoint 2 plus a whole heap more. Internally, we've used Sharepoint 3 to replace a huge amount of disparet systems and use it what we have developed extensively. Happy to share our experiences if you want, just drop me a line. Thanks Robert Crane Saturn Alliance
RICHARD
1ST MAY 2008 14:56:01
Hi Robert - thanks for the comment and appreciate the offer of advice - much appreciated. Whilst it's an obvious question, the simple answer is - I needed something to fill the gap at short notice and our existing (but unused) Sharepoint v2 via SBS 2003 setup seemed the ideal candidate. Of course I hit the afore mentioned immediate challenges, but for a first step into Sharepoint useage it certainly did the trick. You're not the first person to mention v3, and I've even had some colleagues express amazement at how I've not explored Sharepoint earlier - but I can honestly say from chatting to others that it's an under-used component of SBS that many others in my position (of a "one man band" business aimed at small business clients) haven't explored. Shame on us, I now say! I'll definitely be looking at moving to Sharepoint 3 in due course but for now it's baby steps and using the on-hand tools to achieve some more pressing immediate goals.