posted by ekfn 2011. 3. 3. 11:37
참고 Url : http://hyderabadtechies.info/index.php/sms-alerts/index.php?option=com_content&view=article&id=789:hyderabad-techies-article

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:
Auto Refresh Web Part

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:

Auto Refresh Web Part

posted by ekfn 2011. 2. 16. 11:05
참고 Url : http://www.smallworkarounds.net/2009/07/renaming-moss-2007-or-sharepoint-server.html

Renaming MOSS 2007 or Sharepoint Server

Many times there are situations when you have to rename a MOSS installation either in your virtual PC environment and also sometimes in production, although the production one is little uncommon but the point is a sharepoint developer at one point or other want’s to rename his sharepoint server.

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
  2. Run stsadm for renaming the server.
  3. Rename the server physically on windows explorer.
  4. Reboot the server
  5. Update login credentials 
  6. Restart IIS
  7. Change identity references in IIS
  8. Reconfigure search index

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 !!!!!!!!!!!!!!!!!!

posted by 준치 2010. 3. 9. 19:08
vs2005를 실행해서 새로 만들기 했는데 sharepoint 관련 솔루션 또는 새항목이

안나와서 짱나 죽는 줄알았다..근데 BH 님께서 도와주심..쌩유..

우선 다른 블러그에서 다운로드해서 설치하라는데 그거때문에 그런건지는

확실하지 않다..그거는 vs2008 용이기 때문이다. 그래도 url은 적어야 함..ㅎ

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fb9d4b85-da2a-432e-91fb-d505199c49f6

첫번째

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ProjectTemplates\CSharp\SharePoint\1033 에 있는파일을
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ProjectTemplates\CSharp\SharePoint\1042
폴더 만들어서 복사해 넣는다.

두번째

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplates\CSharp\SharePoint\1033 에 있는파일을
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplates\CSharp\SharePoint\1042
폴더를 만들어서 복사해 넣는다.

시작 - 실행 - cmd 를 해서

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE 이경로로 간다.

그후에 devenv /installvstemplates 를 실행.. 잠시 아무동작 않고 있다가

빠져 나간다..

이렇게 하고 Visual Studio 2005 를 다시 실행하면 된다.

이상입니당...


posted by 준치 2009. 5. 20. 09:41

SharePoint 2007 SP1 failed: Cannot start service SPTimerV3

My lab VM with Win2003 x64, BizTalk 2006 R2, SharePoint 2007 and SQL Server 2005 SP-2 runs very nice, but I forgot to upgrade SharePoint to the new SP-1 version. I would like to mention that this VM was installed with all the default and typical settings selected for all installed products.

The SP-1 for SharePoint 2007 requires WSS 3.0 to be upgraded to SP-1 first. But, this installation failed. The error was:

One or more configurations failed. Completed configuration settings will not be rolled back. Resolve the problem and run this configuration wizard again. System.InvalidOperationException. Cannot start service SPTimerV3.

The upgrade itself was successful, but the wizard failed to start the 'Windows SharePoint Services Timer' NT service. I opened up services.msc and tried to start it manually, but it also fails. The error in the Event Viewer is: The service did not start due to a logon failure.

Maybe this can be caused by the dcpromo-process this lab VM undergone. The server is now a Primary Domain Controller (and wasn't while SharePoint was initially installed).

Changing the 'Log on as' on the 'Log on' tab of the service to a valid account (and password) solved this problem. I started the service manually and pressed the Finish button of the configuration wizard.

Now the SharePoint SP-1 itself...

출처 : http://www.leonmeijer.nl/archive/2008/03/08/81.aspx

2003 서버에 모스를 설치하고 아무 이상이 없다가....언제부터인가 부팅을 하면 서비스나 드라이버에 이상이 있다는 경고 창이 떠서 찾아보니 이 문제 였었다...참....
삽질하고 다시 설치 할뻔했네..ㅎㅎㅎㅎ
해석이 안되서 번역기로...ㅋㅋㅋㅋ 서비스에가서 로그온에서 계정이 맞는지 확인해보니 패스워드가 이상하게 설정되어있었다...그래서 실행이 되지 않았던것이였다....변경....콜..바로 시작...ㅋㅋㅋ

posted by 준치 2009. 4. 6. 15:18

Comparison Operators

General Meaning

Eq

=

Gt

> 

Lt

< 

Geq

>=

Leq

<=

Neq

<> 

Contains

Like

IsNull

Null

IsNotNull

NotNull

BeginsWith

Beginning with word

DateRangesOverlap

compare the dates in a recurring event with a specified DateTime value, to determine whether they overlap


posted by 준치 2009. 2. 10. 10:55
배포할때 Gac에다가 바로 넣지않고 WebApplication 에 배포시에 에러가 나는데 이렇게 하면 배포가 된다...겁바 삽질..

wsp manifest 수정

<?xml version="1.0" encoding="utf-8"?>
<Solution SolutionId="0af73a48-2f56-4da2-b5ed-7414a36b96a9" xmlns="http://schemas.microsoft.com/sharepoint/">
  <Assemblies>
    <Assembly Location="dll 이름이 자동 적용" DeploymentTarget="WebApplication">
      <SafeControls>
        <SafeControl Assembly="적용된 dll 네임, Version=1.0.0.0, Culture=neutral, PublicKeyToken=토큰키" Namespace="PNU.SharePoint.Board.Common" Safe="True" TypeName="*" />
      </SafeControls>

    </Assembly>
  </Assemblies>
</Solution>
posted by 준치 2008. 10. 29. 11:09

구분
<?xml:namespace prefix = o /><?xml:namespace prefix = o />
설명 
SharePoint에 인증받기 위한 방법
Windows 인증
Active Directory, IIS 를 이용한 윈도우 기본 인증

지원형태
Anonymous, Basic,Digest,
Certificates,Kerberos,NTLM

설명
ASP.NET 폼 기반 인증
Active Directory 및 표준 LDAP, SQL, 여타의 데이터베이스, 여타의 ASP.NET 기반 폼 인증 솔루션
-------------------------------------------------------------
지원형태
표준LDAP, SQL, 기타 데이터베이스,
기타 ASP.NET 폼 인증 솔루션  
 
설명
Web SSO
폼 기반으로써 ADFS 나 여타의 ID 관리 시스템과 연계한 웹SSO
-----------------------------------------------------------
지원형태
ADFS(Active Directory Federation Service) ,
여타의 페더레이션 형태의
아이덴티티 관리 시스템  

설명 
SharePoint에서 다른시스템으로 인증 받기 위한 방법
Portal  SSO
데이터베이스의 암호화 된 credential을 이용, SharePoint와 back-end 시스템과의 인증 연동을 위한 것임
--------------------------------------------------------
지원형태
SharePoint SSO  


 

posted by 준치 2008. 10. 29. 11:00
인증 방식에 따라 클라이언트 연동 기능은 반복적인 인증 요구 문제를 일으킬 수 있음

 

인증방식 <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

현상

Basic (기본 인증)

문서에 엑세스 할 때마다 인증 정보를 물어 보게 됨.

WSS의 다른 영역들도 계속적인 인증 요청을 할 가능성이 있음

ASP.NET 폼 인증 /

Web Single Sign-On

자동으로 로그인(Sign me in automatically)” 옵션을 선택하였을 경우
persistent cookie
클라이언트에 생성됨.
이 쿠키는 모든 어플리케이션에 의하여 사용되므로
사용자는 클라이언트
어플리케이션으로 문서를 열 수 있음

자동으로 로그인(Sign me in automatically)” 옵션을
선택 하지 않았을 경우 세션 쿠키가 사용됨.

이 쿠키는 브라우저만이 접근 가능하므로 사용자는 문서 등을
클라이언트 어플리케이션으로

바로 열수 없음

Anonymous (익명 인증)

문서를 열고자 할때 계속적으로 인증 요구를 받게 됨. “취소버튼을 10번 정도 누르면

 문서를 열 수도 있으나, 이것은 사용성이 매우 나쁘기 때문에,
 
익명 엑세스를 할 경우는
 “Client interaction” 옵션을 disable
시키는 것이 좋음 

























 

posted by 준치 2008. 10. 22. 04:00

The SharePoint Web Services

Windows SharePoint Services was being designed and developed during the time when Microsoft was beginning to heavily push Web services. It should be no surprise, then, to find out that you can get at the data in SharePoint through Web services. In fact, there's not just one Web service involved; there are 16. Here's a brief rundown of the Web services that a SharePoint server makes available out of the box:

  • http://server:5966/_vti_adm/Admin.asmx - Administrative methods such as creating and deleting sites
  • http://server/_vti_bin/Alerts.asmx - Methods for working with alerts
  • http://server/_vti_bin/DspSts.asmx - Methods for retrieving schemas and data
  • http://server/_vti_bin/DWS.asmx - Methods for working with Document Workspaces
  • http://server/_vti_bin/Forms.asmx - Methods for working with user interface forms
  • http://server/_vti_bin/Imaging.asmx - Methods for working with picture libraries
  • http://server/_vti_bin/Lists.asmx - Methods for working with lists
  • http://server/_vti_bin/Meetings.asmx - Methods for working with Meeting Workspaces
  • http://server/_vti_bin/Permissions.asmx - Methods for working with SharePoint Services security
  • http://server/_vti_bin/SiteData.asmx - Methods used by Windows SharePoint Portal Server
  • http://server/_vti_bin/Sites.asmx - Contains a single method to retrieve site templates
  • http://server/_vti_bin/UserGroup.asmx - Methods for working with users and groups
  • http://server/_vti_bin/versions.asmx - Methods for working with file versions
  • http://server/_vti_bin/Views.asmx - Methods for working with views of lists
  • http://server/_vti_bin/WebPartPages.asmx - Methods for working with Web Parts
  • http://server/_vti_bin/Webs.asmx - Methods for working with sites and subsites
posted by 준치 2008. 9. 26. 23:13


Calling SharePoint Web Services from Javascript

I’m on a mission. And that mission is to build SharePoint apps without dropping code on the server. Why would anyone want to do this? Well, in many enterprise or hosted environments you don’t have the ability to drop DLLs into a shared SharePoint environment. This has often limited the types of applications we can build to out of the box features or SharePoint designer. But with some Javascript and the WSS web services, we can build a more complex app all with AJAXy goodness.

This code sample uses the Prototype Javascript library. When you see Ajax.Request, that’s using prototype’s Ajax framework. The great thing about prototype is that everything is cross-browser compatible.

First we need some code that formats a simple SOAP envelope. SOAP is the required protocol for communicating with the SharePoint web service.


var Soap = {
  createEnvelope: function(action, ns, parameters)
  {
    var soap = '<?xml version="1.0" encoding="utf-8"?>
        <soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
        <soap12:Body>';
    soap += '<' + action + ' xmlns="' + ns + '">';
    soap += Soap.__parseParameters(parameters);
    soap += '</' + action + '></soap12:Body></soap12:Envelope>';
    return soap;
  },

  __parseParameters: function(parameters)
  {
    var params = "";
    if (typeof parameters == 'object')
    {
      // check if we were provided an array or an object
      if (typeof parameters.push == 'function')
      {
        for (var i = 0, length = parameters.length; i < length; i += 2)
        {
          params += "<" + parameters[i] + “>” + parameters[i+1] +
              “</” + parameters[i] + “>”;
        }
      }
      else
      {
        $H(parameters).each(
          function(pair)
          {
            params += “<” + pair.key + “>” + pair.value + “</” + pair.key + “>”;
          });
      }
    }
    return params;
  }
}
Okay, so now we can make a SOAP envelope as simple as this:

var mySoap = Soap.createEnvelope(
  "MyAction",
  "http://schemas.microsoft.com/sharepoint/soap/",
  { param1: "value", param2: "value" });
Simple enough. Now let’s call a SharePoint web service. We’ll use the Lists web service and create a new list item. The UpdateListItems method allows us to pass in some XML defining the items to create. So first I’m going to build that XML.

var batch = '
  <Batch OnError="Continue">
    <Method ID="1" Cmd="New">
      <Field Name="ID">New</Field>
      <Field Name="Title">Hello World</Field>
    </Method>
  </Batch>';
Next we’ll call the web service using the Ajax.Request object:

// build parameter object
var parameters =
{
  listName: "My List",
  updates: batch       // xml created earlier
}

// create soap envelope
var soap = Soap.createEnvelope(
  "UpdateListItems",
  "http://schemas.microsoft.com/sharepoint/soap/",
  parameters);

// call web service
new Ajax.Request(
  "http://myserver/mysite/_vti_bin/lists.asmx",
  {
    method: "post",
    contentType: "application/soap+xml",
    postBody: soap,
    onSuccess: function(transoprt) { alert("Success: " + transport.responseText); },
    onFailure: function(transport) { alert("Error: " + transport.responseText); }
  });
If all goes according to plan, I should have a new list item with the title of “Hello World” in the list called “My List”.

A couple of points about the javascript above:

It’s certainly not the greatest Javascript in the world. I plan to clean it up and hopefully release a Javascript library for working with all of SharePoint’s web services.
The user’s browser must already be authenticated for this to work. Prototype doesn’t have a way to pass credentials to the web service so make sure you run this from a machine joined to the same domain as the sharepoint site. Ideally this is running within a sharepoint site so that should take care of the authentication problem.
FireFox has an issue because it doesn’t pass domain credentials automatically. This makes debugging hard from your workstation, but if it’s running on a SharePoint site where the user has already authenticated, it works fine.
I cheat in the example above and break strings onto multiple lines. That’s for the purpose of formatting only. If you copy and paste this code directly it won’t work.