Tag: sharepoint 2007
The first of all is, when you go to a customer for a simple upgrade to SharePoint 2010 isn't going to be easy. Why, well Rick Taylor is one of the masters of upgrading to SharePoint 2010, and now I know why he is preaching about all the mess you going to have with upgrading to SharePoint 2010.
A simple thought about upgrading isn't going to be, why? Every customer has custom solutions, changed css's or anything of that stuff, but it's going to be worse. When you have Site Definitions, what is not the best practice of course it is going to be alot worse. All kinds of developers are writing and developing nice Site Definitions but when you are at the stage you want to upgrade these developers kan start all over again. Yes, because they put everything in a solution. Every complete customized lists, document libraries and blogs.
Wow, well if you are an architect or a business manager and you hear about Site Definitions and you're upgrading to SharePoint 2010. You can think twice, and even need to save some money to hire a developer that can write all the site definitions again which are not best practice off course. Yes, why I am writing this blog, because I just started to upgrade some solution that is written if all the above mess. Customized blog pages, document libraries, lists, etc. Yes we make features and we make site definitions and we put them all in one bucket called a WSP and hopefully it will work under SharePoint 2010, because you'll never know.
Allright let's get started. Because a normal SharePoint farm will not allow you to request pages with logged in on your website. This is because MOSS will intercept every page you will ask even when you are using an Web Application. In WSS 2.0 and SPS 2003 you had to the possibility to exclude certain paths from being captured by SPS or WSS.
Well in SharePoint 2007 you can't make an exclusion in Central Administration, but you can do it by manual. How to do this is easy or not, but it's possible. You can't access pages directly in a Web Application, but you can create a Virtual Directory. Still when you access this virtual directory, SharePoint won't allow you to access this virtual directory.
Now we have to do it another way. Let's modify the web.config of your Web Application.
this is probably how your
<httpHandlers> <remove verb="GET,HEAD,POST" path="*" /> <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=126.96.36.199, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=188.8.131.52, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </httpHandlers>
modify it to this:
<httpHandlers> <!-- <remove verb="GET,HEAD,POST" path="*" /> --> <add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> <add path="trace.axd" verb="*" type="System.Web.Handlers.TraceHandler" validate="True" /> <add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" /> <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=220.127.116.11, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=18.104.22.168, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </httpHandlers>
Change the trust level:
<trust level="Full" originUrl="" />
Ensure that your virtual directory has it's own web.config. Without an own web.config it will inherit from your web.config in your website (of course your web.config of your web application).
The situation is following.
I have a page located in the /_Layouts/ dir. This page is the CustomLogin page and validates two ways. The first way is by a post to a security validation with a token.
<form name="LoginForm" action="<% =requestURL %>" method="post" enctype="application/x-www-form-urlencoded" id="LoginForm">
When we hit the submit button it should post data to this validation server and returns data formatted in the header.
The problem is that the posted data is not submitted, because for someone reason MOSS blocks it.
This validation server has it's own SSL certificate and the MOSS site has it's own SSL certificate.
For a company I work for we have an different kind of situation regards the SharePoint site. We have a DMZ with all the webservers we need. We also got a small MOSS 2007 farm where the company hosts his two SharePoint sites. Both sites are on the same farm and on the intranet it works perfectly.
On of these sites is hosted normally on the http port, and the other on is hosted as an extranet application on the https port. The site hosted on the public http port is good, and doesn’t show any problems.
The certificate for the private site is at the reverse proxy server, although it is also a kind of firewall. We used the technet documentation for implementation (link). We did use the Alternative Access Mappings and we did redirect our https port(proxy) to the http port(Site farm).
Everything works perfectly, except for the Document Library. Normal documents can be opened without any problems, but when you want to access a folder in the document library we got a permission denied error from the proxy server. Why you may ask? Well the document library has folders and show all http:// instead of https://. So it redirects from an secure site into a insecure site were the port is blocked on the DNS.
So we maybe thought that this was related to the firewall instead of SharePoint, well forget that. The problem resists in the Document Library and nothing else. Now we contact Microsoft for this issue, but the problem is that Microsoft has only helpdesk people with knowledge of SharePoint or ISA Server. Microsoft helpdesk wants to relate the problem to the firewall instead of their own product, and I can’t blame them, because it’s their product. Well I’m not happy at all with this, because we won’t change anything in the firewall. We tried everything there is needed to work.
The company were I work for doesn’t have this problem to Exchange Server 2003, and this is the same kind of product, and they have the exact same rules and same implementation… Probably this a bug (or feature) and they can’t solve it… maybe later on…
Well I will keep you informed… when I have a solution my blog will keep you informed about it…
I discovered a problem with the My SharePoint-Sites. Someone at the company I work for discovered that he had alot of sites in his SharePoint-Sites webpart at his My Site. So that shouldn’t be a problem I thought. Well it was…
I deleted a subsite of our company intranet, because we decided that the site needed his own dns and database, because it was growing to large. After two weeks we found out that the SharePoint-Sites didn’t update and when we hitted on of these sites we got an error. So, I thought it was maybe a My Site related issue. I deleted his My Site, because it didn’t have alot of information on and added his My Site to new.
Still the same problems came forward, so I decided to hit google.com for it. Well maybe I didn’t seek good enough, but maybe it was related to the search engine. So I decided to reset all the crawled content. After an hour I checked back on the My Site, but still the same problem exists.
Allright, so I decided to look in the help of the stsadm utility. Things that could help I sought on google.com. Well after a couple of searches I found out the following command:
stsadm -o sync -deleteolddatabases 0
In the ssp database you have the table ’sitesynch’ and holds the information for all synchronized information over your SharePoint sites and My Sites. This article mentioned also that sometimes the synchronization table isn’t sychronized. Well after an hour I checked back at the My Site and saw that the SharePoint-Sites didn’t appear anymore.
The job related to this is the â œProfile Synchronizationâ timer job