André Krijnen

Well it was the first time I did a deployment of WSS 3.0 on Windows Server 2008 R2 at a customer… the installation went very well I could say but yet I found out that I had a strange DCOM error. Not the DCOM error I would suspect…

Type: Error
Source: DCOM
Category: None
Event ID: 10016
Description:
The application-specific permissions settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user DomainName\UserName SID {61738644-F196-11D0-9953-00C04FD919C1}. This security permission can be modified using the Component Services administration tool.

So after searching on BING.com I found out that this has the do with the DCOM IIS WAMReg admin service. Normally you would say that this has to do with the location activation of the DCOM service. But when I found out that the DCOM service couldn’t be changed I had to figure out that I had to change some settings. I knew that you can activitate the DCOM service, but Microsoft had to change this DCOM service with the new release of Windows Server 2008 R2. On BING I found out that someone had this error.

So check the blog of Wictor Wilen It saves you a lot of time to figure it out.

Warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in E:\Vhosts\mysticslayer.com\httpdocs\wp-content\plugins\highlight-source-pro\highlight_source_pro.php on line 128

Warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in E:\Vhosts\mysticslayer.com\httpdocs\wp-content\plugins\highlight-source-pro\highlight_source_pro.php on line 128

SharePoint sites using hostnames (HOSTS) with Internet Explorer 8 (IE8) have logon failures

I like to use beta programs. You can see what new functionality will be available before the product is released. But using betas of Internet Explorer is something i have a lot of bad experiences with. Currently we got a report on one of our websites that it had some problems running under Internet Explorer 8. Ofcourse i checked this in my virtual machine by installing the released version of Internet Explorer 6/7/8.

For some reason i was not able to access my SharePoint websites anymore. It kept me asking for my login over and over again. Doing some googling i found out that this issue was also under the beta release and that there is a solution. Keep in mind that this issue is still present in the released version.

It seems that Internet Explorer 8 does a loopback check. This causes SharePoint sites using hostnames (in your HOSTS file) with a logon to have logon failures.I like to use the HOSTS file, because you do not have to use specific port numbers for running your websites. Als for doing demos on events and at customers it looks better.

There are two solutions for the problem. This one i think is the best and less work:

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit Registry Editor, and then restart your computer. (it seems that this was not needed on my virtual machine).

For more information: http://support.microsoft.com/default.aspx/kb/896861

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