Extra Site Usage Reports

For those that are interested, there are these two pages that might be useful aswell, even if the usual MOSS site statistics are not working:

http:///_layouts/usage.aspx

http:///_layouts/usageDetails.aspx

I believe these pages are provided as part of WSS, however if you install MOSS they do not appear to be linked from anywhere, as instead you get the SpUsageSite.aspx/SpUsageWeb.aspx pages with the graphs etc…

The http:///_layouts/usageDetails.aspx even shows you the total hits for the documents which are very useful information

See the following for more info:

http://sharepointknowledgebase.blogspot.com/2009/03/configure-usage-reporting.html

http://blogs.msdn.com/ketaanhs/archive/2008/10/08/usagedetails-aspx-and-spusageweb-aspx-why-some-sites-show-usagedetails-aspx-and-not-spusageweb-aspx.aspx

Are you ready for SharePoint 2010?

The PreUpgradeCheck utility in SP2 is a simple to use tool that is run from the command line

stsadm –o preupgradecheck

This tool goes one step deeper and after the completion of this tool a nice output page is displayed that further dives into your FARM and outputs some decent information. If there are failures or issues it will be deeply highlighted in this output.

And the most important, it is read-only, so there is no hard to run on your server

Error “An error has occurred while accessing SQL database or system resources. If this is the first time you have seen this message, please try again later. If this problem persists, please contact your administrator. ” on Configure configure profile import: An error has occurred while accessing SQL database or system resources. If this is the first time you have seen this message, please try again later. If this problem persists, please contact your administrator.” An error has occurred while accessing SQL database or system resources. If this is the first time you have seen this message, please try again later. If this problem persists, please contact your administrator. on user Profile and Properties

I have seen this error a few times, firat check your Servcie Proider (SharedServices1) to make sure there is a index server seleted.

Otherwise, go to your 12 log and try to seach key word “fail”

Logging levels in Sharepoint and STSADM

I just found on our Front End Servers where there are no trace logs under 12\LOGS. The log files are there but without any message inside.

‘This gives you the current settings
stsadm.exe -o listlogginglevels

Run this before doing any changes on a machine. It’s always good to know the original settings before making changes.

‘This set the logging to Verbose / Error.
stsadm -o setlogginglevel -tracelevel Verbose -windowslogginglevel Error

//full path
“C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\stsadm” -o setlogginglevel -tracelevel Verbose -windowslogginglevel Error

Readonly textbox value lost on postback

I am sure I have came across this before. In Asp .net 2.0, a readonly textbox value will not be passed if it is set by Javascript. To get the value you will just manually read the value from the request headers (this.TextBox1.Text = Request[this.TextBox1.UniqueID];), which poses a security risk and introduces the problem that 2.0 addresses.

With 2.0, the TextBox control’s ReadOnly property’s behavior has changed slightly. From the technical docs:

The Text value of a TextBox control with the ReadOnly property set to true is sent to the server when a postback occurs, but the server does no processing for a read-only text box. This prevents a malicious user from changing a Text value that is read-only. The value of the Text property is preserved in the view state between postbacks unless modified by server-side code.