the issues i have faced after deploy MOSS SP2

After deploy MOSS SP2 to QA environment i have faced 3 issues :

1. Telerik Radeditor not working as normal at Mac client with Safari.
2. Foxit PDF i0Filter is not working
   
3. Some changer on the layout folder, so our layout customization lost some imagine.

Solution:

1. no solution yet, still checking at telerik forum.
2. Reinstall the PDF i-filter and start full crawl
3. Developer help to move the image to right folder
   

How to check the document have index to index server.

Let say you want to check the file you have uploaded is index to index server or not, you can go to Shared Services Administration --> Search administration --> Crawl Log --> Select the Host name you want to check --> Type the path you want to check to Find URLs that begin with the following hostname/path: ( exp : abc.com/sites/test/share document)

At last click on the Filter then go to search your file at the log.

if you not see the your file not propagate, you can go to run incremental Crawl.

then chek you log file again. Done

Index and search at MOSS

oh no!! get crazy with my lab server for the index and search problem!! after few day on testing and google , i able to understand some concept. Just want to keep the record here for future reference.

what is search server ? as i understand is copy the index file from index server and keep and search server, when user do the search query.

How to reset the search server propagation file ? is simple step , stop the office at central admin -> operation -> services on server -> office SharePoint Server Search ( on top select the server you want to reset)--> click on the Action Stop --> go to the index file delete the folder --> click the action start the search service. At this moment the search server will pull the propagation from the index server.

what is index server ? Index server is the server to do pull the indexing data from SQL and keep it at index server then propagation to all search server.

how to reset the index ? go to SSP --> Search administration --> Reset all crawled content --> click Reset Now. After reset all the index will become Zero (nothing) , so you need to start the Crawl. Go to Content sources ->click on the Start full Crawl under the Local Office SharePoint Server sites. then waiting the crawl, if you have alot content will take up few day to complete it.

yeah..this is what i want to share about the index and search .. :) . if you want to find specify file have crawl or not you can check onw the Crawl log.

ULS logs

ULS logs what is that? hi hi.. just get to learn new log related with MOSS operation. I have not much trouble shooting for MOSS at server , normally all the time look at event viewer log then will resolved the problem. This ULS logs can track the communication between moss with SQL so you can know what is going on the query.

You can use your server's Unified Logging Service (ULS) logs to troubleshoot queue issues in Microsoft Office Project Server 2007. The queue entry information in ULS logs is especially useful in conjunction with the information in the Manage Queue page in Project Web Access, or with Windows Server Event Viewer.

you can get more detail here:

This article describes:

• How to configure ULS log-file settings

• How to configure Microsoft Office Excel 2007 to view ULS log files

• How to search for specific queue jobs in the ULS logs

• Types of queue job entries in the ULS logs

• Queue entry parameters

• Best practices for troubleshooting queue issues