I have cleared one more exam as well
Sharepoint-Configuring (70-630)
Am able to complete my MCTS certification in Sharepoint-Application Developement (Exam 70-542).
Friday, 21 December 2007
Monday, 17 December 2007
Logging Errors in MOSS
Logging Errors in SharePoint 2007
The error will be logged into folder 12/logs/ write your custom message to easily identify the error
If you have this need, use something like the following line of code:
catch(Exception myException)
{
Microsoft.Office.Server.Diagnostics.PortalLog.LogString("Exception Occurred: {0} || {1}", myException.Message, myException.StackTrace);
}
One more Important thing
The most popular error message is "An unexpected error has occured. Please contact your Administrator".
Am fed up with this generic error message, which gives no clue of error.
In order to see the real error messages as well as the stack trace of where the error happened within SharePoint, you have to do two simple things - in fact, this is mainly standard ASP.NET business:
In the web.config file of your SharePoint web application, edit these two entries:
1. Switch custom errors off
<system.web>
...
<customErrors mode="On" />
...
</system.web>
Set the value "On" to "Off" in a development or staging environment, or to "RemoteOnly" if you have to troubleshoot an issue in a productive environment (of course, the error has to be reproduced locally in this case).
2. Enable CallStack
<SharePoint>
...
<SafeMode MaxControls="50" CallStack="false" />
...
</SharePoint>
To make the CallStack visible, set the value to "true".
Please note that changing the web.config will cause SharePoint to restart the whole web application immediately after saving.
Happy D' ing.
The error will be logged into folder 12/logs/
If you have this need, use something like the following line of code:
catch(Exception myException)
{
Microsoft.Office.Server.Diagnostics.PortalLog.LogString("Exception Occurred: {0} || {1}", myException.Message, myException.StackTrace);
}
One more Important thing
The most popular error message is "An unexpected error has occured. Please contact your Administrator".
Am fed up with this generic error message, which gives no clue of error.
In order to see the real error messages as well as the stack trace of where the error happened within SharePoint, you have to do two simple things - in fact, this is mainly standard ASP.NET business:
In the web.config file of your SharePoint web application, edit these two entries:
1. Switch custom errors off
<system.web>
...
<customErrors mode="On" />
...
</system.web>
Set the value "On" to "Off" in a development or staging environment, or to "RemoteOnly" if you have to troubleshoot an issue in a productive environment (of course, the error has to be reproduced locally in this case).
2. Enable CallStack
<SharePoint>
...
<SafeMode MaxControls="50" CallStack="false" />
...
</SharePoint>
To make the CallStack visible, set the value to "true".
Please note that changing the web.config will cause SharePoint to restart the whole web application immediately after saving.
Happy D' ing.
Friday, 14 December 2007
MOSS WorkFlows : Failed on Start
In case the workflows fails on start--Keep a eye on Application Pool of the application and see that account on which the app pool runs has full priveleges over database and over the site-preferably admin priveleges are required.
Wednesday, 5 December 2007
MOSS Hard Limitations
SharePoint 2007 Maximum Limitations
Following is a list of names and other parameters with the maximum allowable size on each. If during your course of using the product, you inadvertently cross these limits, then you would end up with errors. These are hard limits
For some more Limitations refer http://technet.microsoft.com/en-us/library/cc262787.aspx
Following is a list of names and other parameters with the maximum allowable size on each. If during your course of using the product, you inadvertently cross these limits, then you would end up with errors. These are hard limits
Site Name | 128 characters |
Site URL | 255 characters |
Display name | 128 characters |
Connection string | 384 characters |
Email address | 128 characters |
Version numbers | 064 characters |
Virtual Server Friendly Name | 064 characters |
SQL Database Name | 123 characters |
SQL Database Column | 128 characters |
SQL Database Table Name | 128 characters |
SQL Role Name | 128 characters |
Server Name | 128 characters |
Windows User Name | 300 characters |
Windows Password | 300 characters |
Dependencies per object | 032 objects |
Zone enumeration value | 004 zones |
Default SQL command timeout | 300 seconds |
Number of simultaneous workflows that can be run | * 015 |
For some more Limitations refer http://technet.microsoft.com/en-us/library/cc262787.aspx
Labels:
MOSS Hard Limitations,
MOSS Limits
Monday, 3 December 2007
Upload Multiple Documents from client to Sharepoint Library
Create a .aspx file in 12 hive-Layouts directory, and it can be opened through the URL http://Server_Name/_layouts/WebForm1.aspx.
Copy the code from the following location into the newly created WebForm1.aspx.
http://msdn2.microsoft.com/en-us/library/ms456628.aspx
Copy the code from the following location into the newly created WebForm1.aspx.
http://msdn2.microsoft.com/en-us/library/ms456628.aspx
Difference between View and Read in Permissions in Sharepoint
Users with Read only permissions can view the content using Client side application like Excel or Infopath.
Users with View only permissions cannot.Like they can view only Server side rendering items.
Users with View only permissions cannot.Like they can view only Server side rendering items.
Subscribe to:
Posts (Atom)