Automatic page refreshes were a big pain point in SharePoint 2007. If you had a page or list that you wished to refresh at regular intervals, so it the event that another user entered items, the screen would update, there was no easy/direct way of doing this. You could of could add using the Content Editor Web Part but this refreshes entire the entire page.
To overcome this, SharePoint 2010 introduces a new Ajax option has been added to many webparts to enable auto refresh of webpart without refreshing the entire web page. This feature is available out of the box in SharePoint 2010 and no additional development is required.
How to use Auto Refresh Web parts in SharePoint 2010:
In SharePoint 2010, web parts have a new section in their tool panes - Ajax Options:
The key option is the Enable Asynchronous Automatic Refresh. Checking this will enable the Auto Refresh feature on the webpart. The Auto Refreshing Interval is the time interval in which webpart will get refreshed automatically.
Implementation:
To demonstrate the implementation I created a custom list and added several items. Next, I added the list to a page as a web part. Editing the web part, I selected the checkbox to enable the automatic refresh and left the interval at the default 60 seconds (as shown above). I clicked Ok to save the settings and then saved the page (using the Stop Editing button) and thus generated a page with an auto-refreshing web part showing the contents of the custom list:
As many of you know, event receivers are a great way to hook into various SharePoint events. These can apply to Feature events such as FeatureActivated, List events such as FieldAdded, and many others. The most common set of receivers used, however, are part of SPItemEventReceiver which let you wire your code up to a number of events that can occur to items on a list or library.
When working with events, you’ll quickly find that before (synchronous) and after (asynchronous) events exist, and the method suffix such as “ing” (e.g. ItemAdding) and “ed” (e.g. ItemAdded) will tell you whether it gets invoked before or after the actual change is made. Basic stuff.
And, as you get deeper, you’ll even find that you can extract the before and after state of the change. For example, you can hook into the ItemUpdating event for a document library and prevent a user from changing a certain column. The code might look like this:
public override void ItemUpdating(SPItemEventProperties properties) { if (properties.BeforeProperties["column"] != properties.AfterProperties["column"]) { properties.Cancel = true; properties.ErrorMessage = "This column cannot be changed"; } }
For a document library, this works just fine. However, you should know that the BeforeProperties hash table is not populated for items on a list. As is worded in the SDK: “For documents, Before and After properties are guaranteed for post events, such as ItemUpdated, but Before properties are not available for post events on list items”
When they say “not available for post events on list items”, do they mean after events (like ItemUpdated, ItemDeleted, etc)? The wording is curious here, so I thought I’d take some time to test each combination of common events such as Add, Update and Delete. These were done across a custom list and then a document library. Each test involved adding a new item, editing the item and then deleting the item. Here are the results for a list:
| List | BeforeProperties | AfterProperties | properties.ListItem |
| ItemAdding | No value | New value | Null |
| ItemAdded | No value | New value | New value |
| ItemUpdating | No value | Changed value | Original value |
| ItemUpdated | No value | Changed value | Changed value |
| ItemDeleting | No value | No value | Original value |
| ItemDeleted | No value | No value | Null |
No value means that column value in the hash table was not available.
New value means that the correct value for the column was available.
Changed value means that the correct updated value was available.
Original value means that the correct original value was available.
Here is the same test against a document library:
| Library | BeforeProperties | AfterProperties | properties.ListItem |
| ItemAdding | No value | No value | Null |
| ItemAdded | No value | No value | New value |
| ItemUpdating | Original value | Changed value | Original value |
| ItemUpdated | Original value | Changed value | Changed value |
| ItemDeleting | No value | No value | Original value |
| ItemDeleted | No value | No value | Null |
Properties.ListItem refers the the current value for the list item at that point in the event. Null means that the item is not available. My analysis yields the following results:
So, if we go back to our original problem listed above. How can we prevent a user from changing a certain column for an item in a list event? From the list table, you can see if we hook into the ItemUpdating event, we can compare the current item’s value (properties.ListItem) to the AfterProperties value. The code would look like this:
if (properties.ListItem["column"] != properties.AfterProperties["column"]) { properties.Cancel = true; properties.ErrorMessage = "This column cannot be changed"; }
I hope this post gives you a better idea of how before and after events work for both lists and libraries. Your comments and feedback are always welcomed.
Renaming the server simply will screw up all the settings inside the sharepoint as many places there are hardcoded references to the previous server which has to be remapped in order to run the MOSS server with the new server name.
Here in this article i will explain you the step by step process for renaming the MOSS server.There are few resources available on the net which helps you in achieving the same but it was hard for me to find a good resource, so i thought to pen it down so that it can help everyone using Sharepoint.
Steps:-
1.Change Alternate Access Mappings
This is the first and foremost step to rename the Sharepoint server.Alternate access mappings can be found at Central Administration>Operations>Alternate Access Mappings
Click on the web application url and edit the url to have the new server name.This you have to do manually for every website.
2.Run stsadm for renaming the server.
You have to rename the server using stsadm before actually or physically renaming the sharepoint server.
The command to rename the server is
“stsadm –o renameserver –newservername “[yournewservername]” -oldservername “[youroldservername]“ ”and this is also shown in the figure below:-
stsadm can be found in “C:\ProgramFiles\Common Files\Microsoft Shared\web server extensions\12\bin\
Developers can set the path to be globally accessible for ease of using stsadm instead of navigating to the whole path.How to configure environment variables in order to get the stsadm available globally can be found here :-http://smallworkarounds.blogspot.com/2009/07/sharepoint-quick-tip-add-stsadmexe-to.html
3.Rename the server physically in the windows explorer
For this step just right click on the My Computer icon in the start menu and click on properties then on the Computer Name tab just click Change button and rename it to whatever new name you want to give to your sharepoint server installation.
4.Reboot the server
After following all the 3 steps mentioned above just reboot your sharepoint server.
5.Update Login Credentials
Updating credentials is must as sharepoint server is still mapped to the old username inside the domain and will thus cause problems.To update credentials we will again use stsadm.exe
“stsadm –o updatefarmcredentials –userlogin “newservername\username” –password “yourpassword”
6.Restart IIS
IIS needs to be restarted in order to reflect the changes which we have just made in the above steps.
Remember to restart the IIS using iisreset/noforce from the command prompt.
7.Changing Identity references in IIS
After doing all these changes still sharepoint website’s application pools are mapped to the old username and servername which were used to install the Sharepoint inside the farm.So in order to get rid of this old server name we have to manually change the Identity references in the IIS.
Remember if the identity says “Predefined” and the value is set to Network Service then there is no need to play and touch those settings, let them be like that only.
But if the Identity is configurable then you have to replace the old servername with the new servername in the username section and if you want to change the password then you have to type the password and retype it to confirm and press ok
After this step almost everything is done you just have to configure search index to function properly.
8.Reconfigure Search Index
After renaming the sharepoint server the search index have to be reconfigured the best possible solution is to drop the search index and rebuild it.
After doing all these changes you may still find at some places where few links are referencing your old server name and clicking those links does nothing more then giving a blank page to user saying nothing exists on the server like that which he is asking for.
In such scenarios you have to use your hit and trial method and have to find the root element which is causing this trouble and definitely that would be configurable just you have to figure out which is the right spot to configure this.
After doing this you might face problems with MySite which can be fixed once editing the People & Groups section of the MySite administration.
At last you can navigate through various pages to check that whether your MOSS 2007 server is working or not.
Disclaimer :- This article is based on my testing under my virtual environment things may vary and i advice not to test and play with your production farm sharepoint installations as this might damage your sharepoint server.
Happy Programming !!!!!!!!!!!!!!!!!!
Sys.WebForms.PageRequestManagerServerErrorException 오류
이 오류가 뭔가여?? 아~~
<%@Page ValidateRequest ValidateRequest="false"
ValidateRequest 를 설정하지 않으면 잠재적 위험요소 오류 발생
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="aa.aspx.cs" Inherits="aa" ValidateRequest="false"%>
ValidateRequest 아~~ 이거때문에 삽질했네...
기본을 까먹지 말자...캬캬캬
--데이터베이스 생성
CREATE DATABASE TestDB
ON (name='data1', filename='d:\data1.mdf')
LOG ON (name='log', filename='d:\log.ldf')
GO
--백업 수행(D:\Test1.bak, D:\Test2.bak에 나누어서 백업)
BACKUP DATABASE TestDB TO DISK='d:\TestDB1.bak' , DISK='d:\TestDB2.bak' WITH INIT
GO
--기존 데이터베이스 삭제
DROP DATABASE TestDB
GO
|
처음전체백업을 받아서 덮어쓰기 옵션으로 다른서버에서 복구를 성공시켰는데
이후 다시 이전서버백업으로 신규서버로 복원을 하려고 하니
아래와 같은 에러가 발생합니다
-----------------------------------------------------
System.Data.SqlClient.SqlError: 미디어 세트에 2개의 미디어 패밀리가 있지만 1개만 제공하고 있습니다.
모든 멤버를 제공해야 합니다. (Microsoft.SqlServer.Smo)
-----------------------------------------------------
어떻게 해야할까요..? |