Orokorra:
Arazketa zaila denean, Windows SharePoint Services funtzionalitatea pertsonalizatuak garatzen 3.0 (WSS) edo 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.
Erabiltzen dut teknika hau arrakasta handiz Besterik misteriotsu akatsak konpontzeko.
Hurbilketa:
SharePoint informazio asko gordetzen du erregistro batean log diagnostiko bat 12 hive.
The "12 hive" is usually located at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12". (Ez nago ziur da ahalik bada 12 hive inon bizi nahi, Izan ere,).
Ideia da gaur egungo log fitxategi bat aurkitu, 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.
- Kopiatu eta itsatsi nicely MS Excel sartu.
My favourite metodoa:
- Ireki du seinalatuz Windows Explorer bat 12 hive erregistroak.
- Ordenatzeko ikuspegian data aldatu erakusten (berrienak lehen).
- Nabarmendu gehien uneko egunkari-fitxategia.
- Web arakatzailearen leiho batean, behartzeko errorea gertatuko.
- Quickly open the current log file and copy its contents to MS Excel.
- Jump to the end and analyze the relevant entries.
Other Notes:
Lehenespenez, the diagnostic log is located in the 12 hive\LOGS directory.
MS Best practices (as per Mike T. of 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, in which case you’d obviously need to find the log file there instead of the default 12 hive location).
This entry addresses issues such as:
- SharePoint workflow failed to start due to an internal error.
- (more to be added over time)
- This entry has been helpful diagnosing workflow errors (e.g. "The workflow failed to start due to an internal error").
Beraz,, daude aldiz joan nintzen 12 hive erregistroak eta ez da gutxi aurkituko ditu bertan deus, nahiz eta saioa amaitzeko mailak dira, besteak beste, ez dagoela datu beharra dago. Esate baterako, Hemen nago eserita Windows Explorer erregistroak karpeta ikuspegi begiratu eta ikusten dut, batez besteko, erregistroak dira 1-2 Kontzertu. Baina orduan, hainbat ordu horretan, erregistroak dira, 10k ikusten dut. Orain, galdera guneak SharePoint erabiltzen dira nahiko askoz 24 etan, egun bat. Beraz, zerbait da, hari / prozesu informazioa saihesteko horiek informazio saioa itxi batetik sortzen da gertatzen, Dute bere gain hartuko nuke. Beraz,, Nola irudikatu dut zer arazo hau sortzen ari da?
Hau guztia aurkitu dut nahi egunkariak joan eta saiatu arazteko arazo bat joan nintzen. Erabiltzaile bat gehitu web zati bat eta web-zatian kontatzen erregistroak egiaztatzeko, horiek. Baina, jakina,, ez dago erregistroan ezer.
lagundu dit errorearekin: LOG ID 5566