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
Sometimes after a long day of working with SharePoint, encountering a crazy SharePoint problem, or dealing with frustrations around SharePoint you just need a good laugh.
Today I ran across The ‘Fantastic 40; SharePoint Jokes by Paul Swider today and some of them just made me laugh. Head on over to his blog and check them out. Some of them are pretty funny.
To quote Paul, “take it for what it is”…..
Ben SharePoint Jokes Consultants SharePoint
Just this morning, I was working with a client who had some errors pop up in their SharePoint farm. I looked at the Windows Event log and didn’t find a whole lot of helpful info. So, I moved on to the ULS logs, to my dismay, they were almost all 0 KB with a couple of files that were 2 KB or 3 KB.
I opened up the files that appeared to have some text in them and found the following entry:
“08/20/2009 10:38:58.08 wsstracing.exe (0×07A0) 0×07CC ULS Logging Unified Logging Service uls1 Monitorable Tracing Service lost trace events. Current value 5.”
Naturally I went to Google with my error as I had never seen this before and found this blog post: http://weblogs.asp.net/jimjackson/archive/2008/05/13/sharepoint-logs-tacing-service-lost-trace-events.aspx by Jim Jackson. I restarted the Windows SharePoint Services Tracing service just as he suggested and bingo! My ULS logs started recording events again. Thanks Jim!
Ben SharePoint 2007 SharePoint, SharePoint 2007, ULS Logs, Windows SharePoint Service Tracing