Tuesday, October 13, 2009
Thursday, October 8, 2009
Access Denied in Operations and Applications Management tabs
Today I have faced one problem in my SharePoint Server when I have opened my SharePoint Central Administration. I can able to see the Home page, but when try to navigate Operations or Application Management tab. It was throwing error called “Access Denied.”
So, I followed these steps to update the password for the account that is used by the Central Administration application pool. I followed these steps:
On EACH (missed this part earlier) servers in the server farm, open a command prompt, type the following line, and then press ENTER: cd %commonprogramfiles%\Microsoft Shared\Web server extensions\12\Bin
On the server that hosts the Central Administration Web site, type the following line at the command prompt, and then press ENTER: stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword
On all other servers in the server farm, type the following line at the command prompt, and then press ENTER: Stsadm –o updateaccountpassword –userlogin-password [-noadmin]
· Then do an iisreset /noforce
That granted restored my permissions to the Application Management and Operations sites.
Then its works fine!!!!
So, I followed these steps to update the password for the account that is used by the Central Administration application pool. I followed these steps:
On EACH (missed this part earlier) servers in the server farm, open a command prompt, type the following line, and then press ENTER: cd %commonprogramfiles%\Microsoft Shared\Web server extensions\12\Bin
On the server that hosts the Central Administration Web site, type the following line at the command prompt, and then press ENTER: stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword
On all other servers in the server farm, type the following line at the command prompt, and then press ENTER: Stsadm –o updateaccountpassword –userlogin
· Then do an iisreset /noforce
That granted restored my permissions to the Application Management and Operations sites.
Then its works fine!!!!
Saturday, September 12, 2009
How to create your own custom 404 error page and handle redirect in SharePoint 2007 (MOSS)?
how to use our own 404 file not found error page in MOSS environment. The following example catches the 404 error and sends users to a redirect page.
Here's the steps:
1. In your MOSS server, make a copy of
%systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033\sps404.html
and call it my404.html
2. Create a Virtual Directory in IIS under your MOSS root web application. For example /errors
3. Create your own redirect aspx page, for example /errors/my404redirect.aspx and code your redirect logic in there. This is a normal asp.net page.
4. In my404.html, make the following change:
STSNavigate("/errors/my404redirect.aspx?oldUrl=" + requestedUrl);
5. Create a Console Application and insert the following code and run it in MOSS server
System.Uri webApplicationUri = new Uri(http://MOSSServer/);
SPWebApplication webApplication = SPWebApplication.Lookup(webApplicationUri);
webApplication.FileNotFoundPage = "my404.html"; //*note
webApplication.Update();
*Note: By default this is set to null. FileNotFoundPage needs to point to a html file that lives in %systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033. The file needs to be html only.
6. Now when you browse to a page that doesn't exist, you should expect to be brought to the redirected page.
*Another note:
In IE there's a "Show friendly HTTP error messages" setting which is ON by default in Internet Options->Advanced. With this setting on, sometimes your custom error page is not displayed. In order to override this setting, both my404.html and /errors/my404redirect.aspx from the above steps need to be larger than 512 bytes in size. Refer to the following KB about this setting: http://support.microsoft.com/kb/218155
* This seems to be working within a site collection context only, i.e. http://MOSSServer/sites/siteA if sites is a wildcard inclusion managed path and siteA doesn't exist in MOSS then this URL will NOT trigger the custom 404 error page set to SPWebApplication.FileNotFoundPage property.
Here's the steps:
1. In your MOSS server, make a copy of
%systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033\sps404.html
and call it my404.html
2. Create a Virtual Directory in IIS under your MOSS root web application. For example /errors
3. Create your own redirect aspx page, for example /errors/my404redirect.aspx and code your redirect logic in there. This is a normal asp.net page.
4. In my404.html, make the following change:
STSNavigate("/errors/my404redirect.aspx?oldUrl=" + requestedUrl);
5. Create a Console Application and insert the following code and run it in MOSS server
System.Uri webApplicationUri = new Uri(http://MOSSServer/);
SPWebApplication webApplication = SPWebApplication.Lookup(webApplicationUri);
webApplication.FileNotFoundPage = "my404.html"; //*note
webApplication.Update();
*Note: By default this is set to null. FileNotFoundPage needs to point to a html file that lives in %systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033. The file needs to be html only.
6. Now when you browse to a page that doesn't exist, you should expect to be brought to the redirected page.
*Another note:
In IE there's a "Show friendly HTTP error messages" setting which is ON by default in Internet Options->Advanced. With this setting on, sometimes your custom error page is not displayed. In order to override this setting, both my404.html and /errors/my404redirect.aspx from the above steps need to be larger than 512 bytes in size. Refer to the following KB about this setting: http://support.microsoft.com/kb/218155
* This seems to be working within a site collection context only, i.e. http://MOSSServer/sites/siteA if sites is a wildcard inclusion managed path and siteA doesn't exist in MOSS then this URL will NOT trigger the custom 404 error page set to SPWebApplication.FileNotFoundPage property.
Saturday, August 29, 2009
Subscribe to:
Posts (Atom)