<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>rtraction - London, Ontario - Web Design, Web Development and Strategic Consulting &#187; DCOM</title>
	<atom:link href="http://www.rtraction.com/blog/tag/dcom/feed" rel="self" type="application/rss+xml" />
	<link>http://www.rtraction.com/blog</link>
	<description>rtraction blog - Web Design, Web Development and Strategic Consulting</description>
	<lastBuildDate>Fri, 25 Nov 2011 15:08:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WSS 403 Forbidden &amp; DCOM Errors in Eventlog</title>
		<link>http://www.rtraction.com/blog/devit/wss-403-forbidden-dcom-errors-in-eventlog.html</link>
		<comments>http://www.rtraction.com/blog/devit/wss-403-forbidden-dcom-errors-in-eventlog.html#comments</comments>
		<pubDate>Wed, 24 Jun 2009 13:52:55 +0000</pubDate>
		<dc:creator>David Millar</dc:creator>
				<category><![CDATA[Devit!]]></category>
		<category><![CDATA[403]]></category>
		<category><![CDATA[DCOM]]></category>
		<category><![CDATA[WSS]]></category>

		<guid isPermaLink="false">http://www.rtraction.com/blog/?p=382</guid>
		<description><![CDATA[One thing that can be frustrating for any developer is when you run into a problem and despite millions of search results when searching for a resolution nothing seems to solve the issue.  I thought I would share some simple solutions to two very frustrating WSS issues we&#8217;ve run into this past year.
The first issue [...]]]></description>
			<content:encoded><![CDATA[<p>One thing that can be frustrating for any developer is when you run into a problem and despite millions of search results when searching for a resolution nothing seems to solve the issue.  I thought I would share some simple solutions to two very frustrating WSS issues we&#8217;ve run into this past year.</p>
<p>The first issue is intermittent 403 Forbidden errors on a WSS (Windows Sharepoint Services) site.  We were seeing  anonymous users in our test environment who couldn&#8217;t use the website at all until an admin logged in.  After someone had logged in then anyone could use the website with or without a login.  What ended up being the problem was a permissions issue on the bin folder for the website.  To fix this problem please follow the simple steps below.</p>
<ol>
<li>Ensure all sub folders that are virtual directories on the site are using the same application pool as the root site.  (This didn&#8217;t help me as everything was set properly, however I read countless posts of this causing problems for others)</li>
<li>Add read access on the bin folder for the account IUSR.  (You don&#8217;t need to add read access to the files, which is somewhat confusing but none the less that protects the files from being downloaded)</li>
<li>Success!</li>
</ol>
<p>If you have any other problems please post your questions/solutions below.</p>
<p>Continuing on, I also ran into a strange DCOM error popping up in Eventlog on most of our servers with WSS sites running.  The error looks like this&#8230;</p>
<blockquote><p><span style="color: #ff0000; font-size: x-small;">The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user &lt;serverName&gt;\networkservice SID (S-1-5-21-&lt;serviceSID&gt;). This security permission can be modified using the Component Services administrative tool.</span></p></blockquote>
<p>Needless to say, getting this error several hundred times a day in Eventlog is not ideal.  The resolution is rather simple but not overly easy to explain.  Please carefully follow the steps below.</p>
<ol>
<li>Copy the GUID (In my case it was {61738644-F196-11D0-9953-00C04FD919C1})</li>
<li>Open the registry editor by running regedit</li>
<li>Click on &#8216;My Computer&#8217; at the top then select Edit -&gt; Find and Paste the Guid (remove the {})</li>
<li>You should see an application name in the right pane when the Guid is found &#8211; in my case this was &#8220;IIS WAMREG admin service&#8221;</li>
<li>Close the registry editor and open Component Services from Control Panel -&gt; Administrative Tools</li>
<li>Expand Component Services, My Computer, DCOM Config and find the application name discovered above in step #4.</li>
<li>Right click on the the application name and select &#8220;Properties&#8221; then select the Security tab</li>
<li>The first block should be set to Customize &#8211; select edit on the right side.</li>
<li>Now add the service account (in my case this was network service) and add the appropriate access which in my case was &#8220;Local Activiation&#8221; (which you can see in the error above)</li>
<li> Success!</li>
</ol>
<p>Please share this information as both of these errors can be both frustrating and a waste of time.</p>
<p>Good luck and happy coding!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rtraction.com/blog/devit/wss-403-forbidden-dcom-errors-in-eventlog.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

