何小碩's profileGet More... ExperiencePhotosBlogListsMore Tools Help

Blog


    June 13

    Template ID

    ID - FOLDER (extra info)  -  Configurations

        0 - GLOBAL (SetupPath=global) - "Global template"
        1 - STS - "windows SharePoint Services Site", "Team Site", "Blank Site", "Document Workspace"
        2 - MPS - "Basic Meeting Workspace", "Blank Meeting Workspace", "Decision Meeting Workspace", "Social Meeting Workspace", "Multipage Meeting Workspace"
        3 - CENTRALADMIN - "Central Admin Site"
        4 - WIKI - "Wiki Site"
        7 - BDR - "Document Center"
        9 - BLOG - "Blog"
       20 - SPS (OBSOLETE) - "SharePoint Portal Server Site"
       21 - SPSPERS - "SharePoint Portal Server Personal Space"
       22 - SPSMSITE - "Personalization Site"
       30 - SPSTOC (OBSOLETE) - "Contents area Template"
       31 - SPSTOPIC (OBSOLETE) - "Topic area template"
       32 - SPSNEWS (OBSOLETE) - "News area template"
       33 - SPSNHOME (SubWebOnly) - "News Home template"
       34 - SPSSITES - "Site Directory area template"
       36 - SPSCOMMU (OBSOLETE) - "Community area template"
       38 - SPSREPORTCENTER - "Report Center Site"
       39 - CMSPUBLISHING (SetupPath=SiteTemplates\PUBLISHING) - "Publishing and Team Collaboration Site"
       40 - OSRV (SetupPath=SiteTemplates\OSRV) - "Shared Services Administration Site"
       47 - SPSPORTAL - "Corporate Intranet Site"
       50 - SRCHCEN - "Search Center"
       51 - PROFILES - "Profiles"
       52 - BLANKINTERNETCONTAINER - "Internet Presence Web Site"
       53 - BLANKINTERNET - "Publishing Site", "Press Releases Site", "Publishing Site"
       54 - SPSMSITEHOST - "My Site Host"
       90 - SRCHCENTERLITE (SetupPath=SiteTemplates\SRCHCENTERLITE) - "Search Center Lite"
    6221 - PWA (SetupPath=SiteTemplates\PWA) - "Project Web Access Site"
    6215 - PWS (SetupPath=SiteTemplates\PWS) - "Project Workspace"
    14483 - OFFILE - "Records Repository", "Records Repository"

    June 12

    Error ID 5617

    事件類型: 錯誤
    事件來源: Windows SharePoint Services 3
    事件類別目錄: 拓撲
    事件識別碼: 5617
    日期:  2008/6/12
    時間:  下午 09:46:19
    使用者:  N/A
    電腦: xxxx
    描述:
    在 xxxx\OfficeServers 之資料庫 WSS_Content 的結構描述版本 (3.0.149.0) 與在 xxx之預期的資料庫結構描述版本 (3.1.4.0) 不一致。已經阻擋從此伺服器至此資料庫的連線,以避免資料遺失。升級 Web 前端服務或內容資料庫以確保這些版本相符。

    請在 http://go.microsoft.com/fwlink/events.asp 查看說明及支援中心,以取得其他資訊。

    下指令解決: stsadm -o upgrade -inplace -url http://{central_admin_url}"

    June 06

    當你發生如下內容時...???

    今天在客戶端發生了這樣的問題... 完整解答

    SYMPTOMS

    You perform a system recovery in Microsoft Windows SharePoint Services 3.0 in which the configuration database is restored. Then, you try to modify or to delete an alternate access mapping.
    When you do this, you receive an error message that resembles the following error message:

    An update conflict has occurred, and you must re-try this action. The object SPAlternateUrlCollection Name=WEBAPPLICATION Parent=SPFarm Name=SharePoint_Config is being updated by DomainName\UserName1, in the w3wp process, on machine ServerName. View the tracing log for more information about the conflict.

    When you view the Unified Logging Service (ULS) log files, you see an entry that resembles the following entry:

    Date Time w3wp.exe (0x1620) 0x1988 Windows SharePoint Services Topology 8xqz Medium Updating SPPersistedObject SPAlternateUrlCollection Name=WEBAPPLICATION Parent=SPFarm Name=SharePoint_Config. Version: 16449 Ensure: 0, HashCode: 30474330, Id: 609b3309-241a-4193-8289-1bba6a70be50, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPAlternateUrlCollection.Update() at Microsoft.SharePoint.ApplicationPages.IncomingUrlPage.BtnSave_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP._admin_editincomingurl_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.ResumeSteps(Exception error) at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr) at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType) 06/06/2007 14:36:31.51 w3wp.exe (0x1620) 0x1988 Windows SharePoint Services Topology 75bd High UpdatedConcurrencyException: The object SPAlternateUrlCollection Name=WEBAPPLICATION Parent=SPFarm Name=SharePoint_Config was updated by another user. Determine if these changes will conflict, resolve any differences, and reapply the second change. This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread. Previous update information: User: DomainName\UserName1 Process:w3wp Machine:ServerName Time:Date Time Current update information: User: DomainName\UserName2 Process:w3wp Machine:ServerNameDate Time w3wp.exe (0x1620) 0x1988 Windows SharePoint Services Topology 8xqy High ConcurrencyException: Old Version : 16449 New Version : 0

    Back to the top

    最後在 MSDN 中找到這樣的解答~~

     

    CAUSE

    This issue occurs if the contents of the file system cache on the front-end servers are newer than the contents of the configuration database. After you perform a system recovery, you may have to manually clear the file system cache on the local server.

    Back to the top

    RESOLUTION

    To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

    1.Stop the Timer service. To do this, follow these steps:

       a.Click Start, point to Administrative Tools, and then click Services.

       b.Right-click Windows SharePoint Services Timer, and then click Stop.

       c.Close the Services console.

    2.On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.

    3.In Windows Explorer, locate and then double-click the following folder:

    Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID

    Notes

    •The Drive placeholder specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.

    •The GUID placeholder specifies the GUID folder.

    •The Application Data folder may be hidden. To view the hidden folder, follow these steps:

    1.On the Tools menu, click Folder Options.

    2.Click the View tab.

    3.In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.

    •In Windows Server 2008, the configuration cache is in the following location:

    Drive:\ProgramData\Microsoft\SharePoint\Config\GUID

    4.Back up the Cache.ini file.

    5.Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.

    Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.

    6.Double-click the Cache.ini file.

    7.On the Edit menu, click Select All.

    8.On the Edit menu, click Delete.

    9.Type 1, and then click Save on the File menu.

    10.On the File menu, click Exit.

    11.Start the Timer service. To do this, follow these steps:

       a.Click Start, point to Administrative Tools, and then click Services.

       b.Right-click Windows SharePoint Services Timer, and then click Start.

       c.Close the Services console.

    Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

    12.Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

    13.Click Start, point to Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.

    14.Click the Operations tab, and then click Timer job status under Global Configuration.

    15.In the list of timer jobs, verify that the status of the Config Refresh entry is Succeeded.

    16.On the File menu, click Close.

    June 05

    移除預設網站範本

    stsadm –o gl-removeavailablesitetemplate –url "http://intranet/" -template "WIKI#0" -lcid 1033 -resetallsubsites

    範本代碼

    WIKI#0 = Wiki Site (All)

    BLANKINTERNET#2 = Publishing Site with Workflow (All)

    SPSREPORTCENTER#0 = Report Center (All)

    SPSNHOME#0 = News Site (All)

    CMSPUBLISHING#0 = Publishing Site (All)

    BDR#0 = Document Center (All)

    SPSSITES#0 = Site Directory (All)

    STS#1 = Blank Site (All)

    STS#0 = Team Site (All)

    SRCHCEN#0 = Search Center with Tabs (All)

    WIKI#0 = Wiki Site (1033)

    BLANKINTERNET#2 = Publishing Site with Workflow (1033)

    SPSREPORTCENTER#0 = Report Center (1033)

    SPSNHOME#0 = News Site (1033)

    CMSPUBLISHING#0 = Publishing Site (1033)

    BDR#0 = Document Center (1033)

    SPSSITES#0 = Site Directory (1033)

    STS#1 = Blank Site (1033)

    STS#0 = Team Site (1033)

    SRCHCEN#0 = Search Center with Tabs (1033)

    June 01

    當你客製化 MasterPage 出現 "An unexpected error has occurred" 怎樣追蹤問題呢?

    Setting <customErrors mode="Off" /> in web.config and the CallStack="true" property in the <SharePoint><SafeMode> tag in web.config