<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Murthy GS's Blogging Spot</title><subtitle type="html" /><id>http://blogs.msdn.com/murthygs/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/murthygs/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/murthygs/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2009-04-20T05:08:00Z</updated><entry><title>401 - You are nto authorized to view this page - Refresh or f5 will help.</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/murthygs/archive/2009/09/30/401-you-are-nto-authorized-to-view-this-page-refresh-or-f5-will-help.aspx" /><id>http://blogs.msdn.com/murthygs/archive/2009/09/30/401-you-are-nto-authorized-to-view-this-page-refresh-or-f5-will-help.aspx</id><published>2009-09-30T05:40:00Z</published><updated>2009-09-30T05:40:00Z</updated><content type="html">&lt;P&gt;&lt;STRONG&gt;ENVIRONMENT -&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;MOSS 2007 - Upgraded to Sp1 - 12.0.0.6219&lt;/P&gt;
&lt;P&gt;OS - Windows Server 2003 ENT SP2 x64&lt;/P&gt;
&lt;P&gt;SQL - SQL server 2005&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;PROBLEM DESCRIPTION -&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;This problem occured after applying Sp1 - When we browse to a SharePoint site for the frist time after IIS RESET and also browse to the links with in this site for the first time- we are prompted for user authentication and when the users gives the credentials the site come up. But the point is that this web application is configured for anaonymous access. So the question is why is the site asking for credentials when it is for anonymous access. &lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;CAUSE -&lt;/STRONG&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the web.config file &lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;STRONG&gt;&lt;EM&gt;&amp;lt;compilation batch="true" debug="true"&amp;gt;&lt;/EM&gt;&lt;/STRONG&gt;&amp;nbsp; was the culprit. By default this tag should be &lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;STRONG&gt;&lt;EM&gt;&amp;lt;compilation batch="false" debug="false"&amp;gt;.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;Ideally in production environments the debug value should be false, if it is "true" then the web.config file will go into debug mode and look for permissions. It specifies whether to compile debug binaries rather than retail binaries.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;STRONG&gt;RESOLUTION -&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;Change the debug value from "true" to "False".&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;What is Batch compilation?&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt" mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;In short, when debug=true, we don’t batch compile, when debug=false we do…&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt" mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;When an aspx, asax, or ascx page is first requested it gets compiled into an assembly. This assembly has a name like 3ks0rnwz.dll or similar (8 characters) and stores the class for the actual ascx, asax, or aspx page (not the code behind). The assembly goes into a folder in the C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files with the same name as the application.&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt" mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;Related Link - &lt;A href="http://msdn.microsoft.com/en-us/library/s10awwz0.aspx"&gt;http://msdn.microsoft.com/en-us/library/s10awwz0.aspx&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR&gt;&amp;nbsp;&lt;/P&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;STRONG&gt;&lt;EM&gt;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9901139" width="1" height="1"&gt;</content><author><name>murthygs</name><uri>http://blogs.msdn.com/members/murthygs.aspx</uri></author></entry><entry><title>MOSS 2007 - ERROR - Trial period for this product has expired.</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/murthygs/archive/2009/04/20/moss-2007-error-trial-period-for-this-product-has-expired.aspx" /><id>http://blogs.msdn.com/murthygs/archive/2009/04/20/moss-2007-error-trial-period-for-this-product-has-expired.aspx</id><published>2009-04-20T07:08:00Z</published><updated>2009-04-20T07:08:00Z</updated><content type="html">&lt;FONT size=1&gt;
&lt;P&gt;BEHAVIOR:&lt;/P&gt;
&lt;P&gt;====================&lt;/P&gt;
&lt;P&gt;When we perform certain tasks in SharePoint portal 2007 site, like, create a publishing or collaboration site or check out web parts or a custom VS2005-build &lt;/P&gt;
&lt;P&gt;Workflow with a document library or while creating pages, you get an error message.&lt;/P&gt;
&lt;P&gt;ERROR MESSAGE:&lt;/P&gt;
&lt;P&gt;====================&lt;/P&gt;
&lt;P&gt;The Trial period of this product has expired&lt;/P&gt;
&lt;P&gt;ENVIRONMENT:&lt;/P&gt;
&lt;P&gt;====================&lt;/P&gt;
&lt;P&gt;Product - Office SharePoint server 2007 -12.0.4518.1016&lt;/P&gt;
&lt;P&gt;OS - Windows server 2003 standard edition Sp2&lt;/P&gt;&lt;FONT size=1&gt;
&lt;P&gt;CAUSE:&lt;/P&gt;
&lt;P&gt;====================&lt;/P&gt;
&lt;P&gt;This error still happens on the RTM release, not just the B2TR release as mentioned &lt;/P&gt;
&lt;P&gt;in the forum post. Also caused by a server in a farm scenario (even a single-server &lt;/P&gt;
&lt;P&gt;farm) whose application pools are using non-admin accounts.&lt;/P&gt;
&lt;P&gt;RESOLUTION:&lt;/P&gt;
&lt;P&gt;====================&lt;/P&gt;
&lt;P&gt;- Customer as soon as getting this error message will try to check if he had the &lt;/P&gt;
&lt;P&gt;trial version or the full version and tries to convert the license by "convert &lt;/P&gt;
&lt;P&gt;license type" link in the central administration operations page.&lt;/P&gt;
&lt;P&gt;-This step might fail with the following error -"your license conversion operation &lt;/P&gt;
&lt;P&gt;failed. Check the error logs for details" this is an expected behavior as the &lt;/P&gt;
&lt;P&gt;SharePoint license is already converted to a full version from a trial version.&lt;/P&gt;
&lt;P&gt;-The actual problem will not be solved by the above 2 steps.&lt;/P&gt;
&lt;P&gt;-We changed the application pool log on from network service account to a &lt;/P&gt;
&lt;P&gt;SharePoint administration service account.&lt;/P&gt;
&lt;P&gt;- Made this account the local administrator, by adding into the local administrator &lt;/P&gt;
&lt;P&gt;group.&lt;/P&gt;
&lt;P&gt;- Added the SharePoint administrator service account to the IIS_WPG and WSS_WPG &lt;/P&gt;
&lt;P&gt;groups. Did an IIS reset.&lt;/P&gt;
&lt;P&gt;- Logged into the system with the SharePoint administrator service account.&lt;/P&gt;
&lt;P&gt;- These steps did not bring the trial expired error message.&lt;/P&gt;
&lt;P&gt;- And the issue got resolved.&lt;/P&gt;
&lt;P&gt;KEYWORDS:&lt;/P&gt;
&lt;P&gt;====================&lt;/P&gt;
&lt;P&gt;SharePoint MOSS 2007 license expired trial period&lt;/P&gt;
&lt;P&gt;MORE INFORMATION:&lt;/P&gt;
&lt;P&gt;====================&lt;/P&gt;
&lt;P&gt;NOTE - This is a Non MS Link.&lt;/P&gt;
&lt;P&gt;&amp;lt;&lt;A class="" href="http://weblogs.asp.net/avnerk/archive/2007/02/20/trial-expired-errors-in-unexpected-places.aspx" target=_blank mce_href="http://weblogs.asp.net/avnerk/archive/2007/02/20/trial-expired-errors-in-unexpected-places.aspx"&gt;http://weblogs.asp.net/avnerk/archive/2007/02/20/trial-expired-errors-in-unexpected-places.aspx&lt;/A&gt;&amp;gt;&lt;/P&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9556193" width="1" height="1"&gt;</content><author><name>murthygs</name><uri>http://blogs.msdn.com/members/murthygs.aspx</uri></author><category term="Setup" scheme="http://blogs.msdn.com/murthygs/archive/tags/Setup/default.aspx" /></entry></feed>