Jinsi troubleshoot makosa SharePoint siri.

Overview:

Debugging ni vigumu wakati kuendeleza utendaji desturi kwa Windows SharePoint Huduma 3.0 (WSS) au Microsoft Office SharePoint Server (Moss). The main culprit is that SharePoint normally surfaces very little diagnostic information on the web browser when an error occurs. This blog entry describes how to locate additional system-generated diagnostic information that can often provide that extra bit of detail that one needs in order to identify root causes. This can then lead to solving the problem.

Mimi na kutumika mbinu hii na mafanikio makubwa ya kutatua makosa vinginevyo siri.

Mbinu:

SharePoint anaokoa mpango mkubwa wa habari kwa logi uchunguzi katika faili logi katika 12 mzinga.

The "12 hive" is usually located at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12". (Mimi nina uhakika kama inawezekana kwa 12 mzinga wa kuishi mahali popote pengine, kwa kweli).

Wazo ni ya Machapisho sasa logi faili, force the error and then quickly open the log file. These log files are characterized by:

  • Copious amounts of information. SharePoint generates a very large amount of diagnostic information and writes it to that log file very quickly. You need to be quick with the fingers to capture it.
  • Multiplicity. SharePoint does not write to a single log file but rather generates multiple log files in sequence.
  • Nakala na kuweka nicely katika MS Excel.

Njia favorite:

  1. Kufungua Explorer madirisha akizungumzia 12 mzinga magogo.
  2. Aina mtazamo kuonyesha kwa tarehe tarehe (hivi karibuni ya kwanza).
  3. Kuonyesha wengi sasa logi faili.
  4. Katika dirisha kivinjari, nguvu ya makosa kutokea.
  5. Haraka kufungua sasa logi faili na nakala ya yaliyomo yake na MS Excel.
  6. Kuruka hadi mwisho na kuchambua entries husika.

Nyingine Notes:

By default, logi uchunguzi iko katika 12 mzinga magogo saraka.

MS Best mazoea (Ace na Mike T. ya Microsoft) state that the log files should be saved to a separate hard drive. One does this via central admin. Your system administrator may have done this, katika kesi ambayo utazungumzia haja ya kutafuta faili logi huko badala ya default 12 mzinga eneo).

Kuingia hii anwani ya masuala kama vile:

  • SharePoint workflow imeshindwa kuanza kutokana na hitilafu ya ndani.
  • (zaidi kuongezwa baada ya muda)
  • Kuingia hii imekuwa inasaidia kupima makosa workflow (e.g. "The workflow failed to start due to an internal error").

4 mawazo juu ya "Jinsi troubleshoot makosa SharePoint siri.

  1. Larry Virden

    Hivyo, kuna wakati mimi kwenda 12 mzinga magogo na kupata ni kidogo chochote ndani yake, hata ingawa viwango vya magogo ni vile kwamba kuna haja ya kuwa kuna data. Kwa mfano, Mimi nina ameketi hapa kuangalia mtazamo madirisha Explorer ya folda magogo na mimi kuona kwamba, katika wastani, magogo ni 1-2 GIG. Lakini basi mimi kuona masaa kadhaa ambayo ni magogo 10k. Sasa, maeneo ya SharePoint katika swali ni katika matumizi ya pretty much 24 hrs siku. Hivyo kitu kinachotokea kwa nyuzi / michakato ya kuzalisha habari kwamba kuwazuia magogo habari, Ningependa kwa kudhani. Hivyo, jinsi gani mimi kufikiri ni nini na kusababisha suala hili?

    Niligundua haya yote wakati nilikwenda kwenda magogo na kujaribu na Debug tatizo. mtumiaji aliongeza sehemu ya mtandao na sehemu ya mtandao anawaambia kuangalia magogo. Lakini bila shaka, kuna kitu katika logi.

    Kujibu
  2. Kelly Ford
    Kama mafaili hakuna logi hupatikana katika eneo 12HIVE default, unaweza kuangalia faili logi eneo yanaweza kupatikana katika Central Tawala->Shughuli->Magogo na Taarifa ya->Uchunguzi Logging.
    Kujibu
  3. Nafees aliandika:
    Shukrani mtu! hii ni kubwa. Mimi hatimaye kuweza kufuatilia makosa kutoka logi faili yanayotokana. na nini i hakuwa mara tu kusahau kubadili jina la jina katika mkutano workflow.xml wazi faili maalum katika feature.xml.
    Excellent.
    "RunWorkflow: System.IO.FileNotFoundException: Could not load file or assembly ‘NewWorkFlowewWorkFlow, Version = 1.0.0.0, Utamaduni = neutral, PublicKeyToken = ed96fa43c5396ebe’ au mmoja wa beroendet yake. The system cannot find the file specified. File name: ‘NewWorkFlowewWorkFlow, Version = 1.0.0.0, Utamaduni = neutral, PublicKeyToken = ed96fa43c5396ebe’ at System.Reflection.Assembly._nLoad(AssemblyName Filename, Kamba codebase, Ushahidi assemblySecurity, Bunge locationHint, StackCrawlMark& stack udongo, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName Filename, Kamba codebase, Ushahidi assemblySecurity, Bunge locationHint, StackCrawlMark& stack udongo, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembl…"
    Kujibu

Kuondoka Reply

Anwani yako si kuchapishwa. Mashamba required ni alama *