After installing Office 2010 on my computer (both laptop and desktop) running Windows 7 RTM, I had a problem opening any Office files stored in our SharePoint 2007 environment. I would click on a file to open it or edit it, the Office 2010 application would open, however, the file wouldn’t open.
I could download the document to my desktop, open it, edit it, and re-uploaded it, but this fare far from ideal. I could link the site to Colligo, but I don’t want to have connect to a site every time I want to open a document.
Finally, today I ran across this helpful string of comments on the TechNet forum – http://social.technet.microsoft.com/Forums/en-US/office2010general/thread/230fc30a-8922-4c75-a8fc-540b0282dff8
In short, the solution is to make a fake proxy in IE:
- Open up Internet Explorer
- Click Tools –> Internet Options
- Click the Connections tab
- Click LAN settings
- Check “Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections).”
- Enter 127.0.0.1 for the address
- Click Advanced
- In the Exceptions type: *.*
- Click OK, OK and OK
You should now be able to browse to a SharePoint site, click an Office document and have it successfully open in your Office 2010 client. This successfully worked for me with MOSS and reports in the TechNet forum are that it works with WSSv3 as well.
admin Office 2010, SharePoint, SharePoint 2007 Documents, Office 2010, SharePoint, SharePoint 2007, WSSv3
I was working with a client over the last few days on building a Project Workspace site template. We were nearly finished and had to make a couple last edits to a web part when we hit the JavaScript error. When expanding the details of the error it was similar to:
line: 2135
Char: 4
Error: ’style.display’ is null or not an object
code: 0
This error was keeping us from adding web parts and modifying current web parts (we could still delete web parts, but only by using http://url/default.aspx?contents=1 to get to our web part maintenance page).
I did some researching and thanks to this thread, I found this solution:
1) Place page in edit mode
2) Edit the content of the content editor web part by selecting the
‘modify web part’ drop down menu
3) Select the Rich Text Editor and copy the text if you do not want
to lose it.
4) Select Source Editor button, this opens the HTML source code for
the CE Web Part
5) Remove the source code. Our source code had a conflicting ID.
6) Update CE web part and make sure source code does not have auto
generated code, or just add a new content editor web part.
The thread varies on what web parts people had on the page, in our case, we only had one content editor web part and then several list web parts. Once we removed our single content editor web part, everything worked beautifully.
Ben SharePoint CEWP, Content Editor, Javascript, MOSS, SharePoint, Web Parts, WSS, WSSv3
True to their word, Microsoft release SP2 for their Office suite today. It includes SP2 for Office 2007, WSSv3 and MOSS 2007. For a little more detail on the updates, SharePoint Joel has a great blog post.
Of, if you just prefer to go straight to the downloads the links are below:
Office 2007 SP2
Office 2007 Language Pack SP2
WSSv3 SP2
WSSv3 Language Pack SP2
MOSS 2007 SP2
MOSS 2007 Language Pack SP2 (x86)
MOSS 2007 Language Pack SP2 (x64)
Ben SharePoint MOSS, Office, Office 2007, Service Pack 2, Service Packs, SharePoint 2007, SP2, WSS, WSSv3
I’ve done it … I’ve successfully performed my first integration/configuration of WSSv3 and Search Server 2008 Express. It is a powerful combination that gives you all the search features of MOSS while running in a WSSv3 environment. It is really a straight forward configuration to perform and Microsoft has published a great TechNet article on it here.
It really is that simple, install WSSv3 (with SP1), run configuration wizard, install Search Server Express, run configuration wizard again, set up search server (including indexing) and you’re ready to go. When I did it for the first time, after setting up search, I was getting an error that Search Server could only be run on a single application server. I was doing a single server install so I couldn’t figure out what was going on. Apparently, I had forgotten the indexing setup of Search Server and for some reason, not having indexing turned on and configured throws this error. After finishing up the indexing piece everything worked like a charm.
This does bring up, what will probably be one of the primary downsides of Search Server, is that you can only have one Search Server per farm. Using the Express version you are unable to load balance your search servers. If you wish to set up a Search Server farm, you will need to purchase the full version of Search Server.
As I continue to utilize Search Server, I’ll be posting more on some of the features and configuration possible. A comparison of MOSS, Search Server 2008 Express and Search Server 2008 can be seen here.
Ben SharePoint Search Server Express, SharePoint, WSSv3