Tijekom proteklog tjedna, moj kolega and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" radna graditi (za razliku od naših prijenosnih računala). While doing that, mi ran u nekoliko pogrešaka slijedeći ove korake:

• Otvaraju MS Word dokument putem Windows Explorera (koji koristi WebDAV).
• Napravite promjene.
• Spremite.

Došli smo do zaključka da neki puta (obično prvi put) smo spremili dokument, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Nismo razumjeli pitanje root u ovom trenutku, but we figured that we should make sure that the latest MS Office service pack had been installed on that work station. The IT folks went and did that. We went through the test again and we discovered a new problem. When we saved it, Sada smo dobili ovu pogrešku:

Ovaj puta, činilo se kao da je svaka promjena, zapravo, spremiti, whether we answered Yes or No to the scripts question.

Na kraju smo imali pogled na stvarne verzije sustava Office, a ispada da je radna trčanje MS Office 2000 sa servisnim paketom 3 koji se prikazuje u pomoć -> About as "Office 2002".

Pouka priče: Ja uvijek koristite Office 2003 kao moje minimalne osnovni uredski verziju kada koristite WebDAV i Moss.

</kraj>

Pretplatite se na moj blog.

(Za tražilice svrhe, ovo pogreške u tekstu):

Linija: 11807

Char: 2

Pogreška: Objekt ne podržava ovo svojstvo ili metodu

Kod; 0

URL: http://sharepoint01/DocumentReview/_vti_bin/owssvr.dll?location=Documents/1210/testworddocument.doc&dialogview=SaveForm

Želite li nastaviti prikazivati ​​skripte na ovoj stranici?

U jednom ili moja Prvi blogu, Sam opisao cjelokupni proces smo zatim preseliti kupca iz SPS-a 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Iz tog migracijskog projekta, morali smo pronaći dobar način da se presele puno SPS-a 2003 documents over to MOSS. The initial load was easy enough. Create a new target document library in MOSS and use windows explorer to move the documents.

Ovo je nova biblioteka dokumenata:

Open up two windows explorers. Point the first at SPS 2003 and the second at the new document library in MOSS. The following screen shot shows this. Note that the top browser is actually pointing at my c:\temp pogon, ali mogu zamisliti što ukazuje na SPS 2003 biblioteka dokumenata:

Nakon toga povuci i ispusti rad, moja ciljana izgleda ovako:

Now it’s time to deal with the metadata. Assume we have just one column of metadata for these documents named "location." We can see from the above "all documents" view that the location is blank. It’s easy enough to use a data sheet view to enter the location, or even go into each document’s properties one by one to add a location. Let’s assume that there is no practical way to assign the location column a value automatically and that end users must do this by hand. Osim toga, pretpostavimo postoje stotine dokumenata (možda i tisuće) and that it will take many many days to update the metadata. As we all know, no one is going to sit down and work for four of five days straight updating meta data for documents. Umjesto toga, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" vidite kako je prikazano:

Sada, kad netko sjeda za provesti svoj dodijeljeni dnevni sat ili dva označiti doselili dokumente, they can use the "untagged documents" vidite da se usredotočite svoje napore:

Dok korisnici tag dokumenata, oni spadati ovaj popis.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Out of the box, there’s no way to prevent a user from uploading a document to MOSS and then not enter meta data. We can specify that a particular site column is mandatory and the user won’t be allowed to push the save button. Međutim, ako korisnik slike, a zatim zatvara preglednik (ili koristi Windows Explorer za upload dokumenta), ne možemo prisiliti korisnik unijeti meta podataka (opet, iz kutije).

This approach can be used to help with that situation. We can use a "poorly tagged data" view to easily identify these documents and correct them. Couple this with a KPI and you have good visibility to the data with drill-down to manage these exceptional circumstances.

</kraj>

Pretplatite se na moj blog.

Ovaj tjedan, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Imam veću zahvalnost za vrste problema ljudi prijaviti na MSDN forumima i drugdje.

Završni Farma konfiguracija:

• SQL / Index / Intranet WFE unutar vatrozida.
• WFE u DMZ.
• Neka vrsta firewall između DMZ i unutarnjeg poslužitelja.

Prije nego što smo započeli projekt, we let the client know which ports needed to be open. During the give and take, natrag i naprijed preko toga, mi nikada nije izričito rekao dvije važne stvari:

1. SSL znači da je potrebno uvjerenje.
2. The DMZ server must be part of a domain.

Prvi dan, we showed up to install MOSS and learned that the domain accounts for database and MOSS hadn’t been created. To move things along, we went ahead and installed everything with a local account on the intranet server.

U ovom trenutku, smo otkrili zabunu preko SSL certifikata i, nažalost, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. U međuvremenu, mi rješenje arhitekata nastavila s poslovnim stvarima.

Vikend prolazi, a klijent dobiva certifikat.

Naša infrastruktura tip pokazuje i otkriva da DMZ server nije pridružio na bilo domeni (bilo perimetra domena s ograničenom povjerenja ili intranet domene). We wasted nearly a 1/2 day on that. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Još jedan dan prolazi i razne sigurnosne odbori, zainteresiranim stranama i (nije tako) nevini promatrači svi se slažu da je u redu da se pridruže DMZ poslužitelj s intranet domeni (ovo POC, uostalom, Ne proizvodnja rješenje).

Infrastructure guy comes in to wrap things up. This time we successfully pass through the the modern-day gauntlet affectionately known as the "SharePoint Configuration Wizard." We have a peek in central administration and … Yee haw! … DMZ server is listed in the farm. We look a little closer and realize we broke open the Champaign a mite bit early. WSS services is stuck in a "starting" status.

Da ne duljimo, it turns out that we forgot to change the identity of the service account via central administration from the original local account to the new domain account. We did that, re-ran čarobnjaka i voila! We were in business.

</kraj>

Pretplatite se na moj blog.

Iako to nije doslovce točno, kao praktično, internet okrenuto web prednji kraj u DMZ mora biti u domeni (i.e. ne neki samostalni poslužitelj u svojoj maloj radnoj grupi). It doesn’t need to be in the same domain as the internal WFE(s) i drugim poslužiteljima (a vjerojatno ne treba), ali to mora biti domena.

My colleagues and I spent an inordinate amount of time on a proposal which included SharePoint pre-requisites. This included a comprehensive list of firewall configurations that would enable the DMZ server to join the farm and so forth. Nažalost, nismo uspjeli dodati rečenicu negdje da je rekao, na efekt, "Cijela krvava točka ove konfiguracije je kako bi se omogućilo svoj DMZ WFE server, u domeni, da se pridruže unutarnje farmu."

Savršena oluja događaja, gdje smo u osnovi izgledao je napustio kada bismo gledali pravu, urotili sakriti taj problem s nama do relativno kasno u procesu, tako me sprječava zazivajući moje "reći lošu vijest rano" vladati.

Uzdah.

Pretplatite se na moj blog.