I just found that I am unable to view a SharePoint list in Datasheet view because I have the 64bit version of Office 2010 installed.
The error message is :
The list cannot be displayed in Datasheet view for one or more of the following reasons:
A datasheet component compatible with Microsoft SharePoint Foundation is not installed.
Your Web browser does not support ActiveX controls.
A component is not properly configured for 32-bit or 64-bit support.
To fix this follow this link to Microsofts Knowledge base article http://support.microsoft.com/kb/2266203
Tuesday, 23 November 2010
Wednesday, 6 October 2010
Show Quick Launch on SharePoint 2010 Webpart Page
When you create a webpart page on SharePoint 2010 or 2007 for that matter, the quick launch will vanish.
With SharePoint 2007 all you needed to do was edit the page in SharePoint Designer and remove the following 2 lines:
< asp:Content ContentPlaceHolderId="PlaceHolderNavSpacer" runat="server"></asp:Content>
< asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server"></asp:Content>
With SharePoint 2010 you also need to delete the following:
< style type="text/css">
body #s4-leftpanel {
display:none;
}
.s4-ca {
margin-left:0px;
}
</style>
The quick launch will now display on the web part page.
With SharePoint 2007 all you needed to do was edit the page in SharePoint Designer and remove the following 2 lines:
< asp:Content ContentPlaceHolderId="PlaceHolderNavSpacer" runat="server"></asp:Content>
< asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server"></asp:Content>
With SharePoint 2010 you also need to delete the following:
< style type="text/css">
body #s4-leftpanel {
display:none;
}
.s4-ca {
margin-left:0px;
}
</style>
The quick launch will now display on the web part page.
Thursday, 19 November 2009
SharePoint 2010 Install Failed
After I tried twice and failed twice to install SP2010, with the same issue both times, I googled the error and found that at the moment SharePoint 2010 cannot be installed on Server 2008 R2.
http://blogs.msdn.com/opal/archive/2009/11/16/installation-notice-for-sharepoint-2010-public-beta.aspx
Yes I was using Server 2008 R2. So now I'll try with Server 2008.
http://blogs.msdn.com/opal/archive/2009/11/16/installation-notice-for-sharepoint-2010-public-beta.aspx
Yes I was using Server 2008 R2. So now I'll try with Server 2008.
Wednesday, 18 November 2009
New Certification
_529_530.png)
With all this Office 2010 excitement, I forgot to brag about my latest certification.
Did 070-630 and scored 1000 from 1000. First time I got the perfect score.
Office 2010
Office 2010 installed with no issues. It looks good, but my best bit so far is the 'send a smile'.
If you like something then you can send a smile to Microsoft and tell them what you liked. You can also send a red sad face when you get some nasty bad thing :o)
Content Editor Links - SharePoint 2007
I have a site that is extended for use externally. The links that are used insite of a content editor web part (CE) do not work externally.
What I noticed is that when a link is clicked it resolves to http://servername/linkxxxxx and not http://extranetaddress/linkxxxxx as expected.
This result occurs even when the link entered into the CE is trimmed to just /linkxxxxx. I am surprised at this behavior as in all other areas, for instance, quick launch items, the links are managed correctly.
One fix that I found works, is to edit the source in the CE web part and remove the http://servername part, instead of removing this part using the rich text editor. After doing this, every works correctly.
The problem with this fix is that every previously created link will have to be manually dealt with after extending a site and also content editors will need extra training to show them how to deal with the issue.
I found that the problem only occurs when using an extended site and a host header, so I have implemented a better fix using AAM (Alternate Access Mapping).
Firstly I removed the extended site from IIS and then added extranet.co.uk as an AAM for the extranet zone. This is done within Central Admin.
All now works correctly.
What I noticed is that when a link is clicked it resolves to http://servername/linkxxxxx and not http://extranetaddress/linkxxxxx as expected.
This result occurs even when the link entered into the CE is trimmed to just /linkxxxxx. I am surprised at this behavior as in all other areas, for instance, quick launch items, the links are managed correctly.
One fix that I found works, is to edit the source in the CE web part and remove the http://servername part, instead of removing this part using the rich text editor. After doing this, every works correctly.
The problem with this fix is that every previously created link will have to be manually dealt with after extending a site and also content editors will need extra training to show them how to deal with the issue.
I found that the problem only occurs when using an extended site and a host header, so I have implemented a better fix using AAM (Alternate Access Mapping).
Firstly I removed the extended site from IIS and then added extranet.co.uk as an AAM for the extranet zone. This is done within Central Admin.
All now works correctly.
Authentication Failure on Front End Server
If, like me you find that you are unable to authenticate to your SharePoint site locally on the server, then follow this KB article to fix http://support.microsoft.com/kb/956158/en-us
All to do with a "loop back" check apparently.
All to do with a "loop back" check apparently.
Subscribe to:
Posts (Atom)
