Gjatë javës së kaluar, tim koleg and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" workstation build (në krahasim me laptopë tonë). While doing that, ne u përplas me disa gabime duke ndjekur këto hapa:

• Hapni një dokument MS Word përmes Windows explorer (e cila përdor WebDAV).
• Bëni një ndryshim.
• Ruaje atë.

Ne kemi ardhur për të kuptojnë se disa herë (zakonisht hera e parë) ne shpëtuam dokumentin, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Ne nuk e ka kuptuar çështjen rrënjë në këtë pikë, 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, ne tani mori këtë gabim:

Këtë herë, ajo dukej si çdo ndryshim ishte, në të vërtetë, ruajtur, whether we answered Yes or No to the scripts question.

Ne fund kishte një vështrim në versionin aktual të Zyrës dhe kjo rezulton se workstation është running MS Office 2000 me pako të shërbimit 3 e cila tregon deri nën ndihmë -> About as "Office 2002".

Morale të tregimit: Unë gjithmonë do të përdorim zyre 2003 si minimum time zyre version bazë kur duke përdorur WebDAV dhe myshk.

</fund>

Abonohen në blogun tim.

(Për qëllime search engine, kjo është teksti gabimi së):

Linjë: 11807

Shkrumb: 2

Gabim: Object nuk e mbështet këtë pronë apo metodë

Kod; 0

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

A doni që të vazhdojë drejtimin Scripts në këtë faqe?

In one or my very first blog posts, I described the overall process we followed to migrate a customer from SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.

For that migration project, we had to find a good way to move a lot of SPS 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.

This is the new document library:

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 drive, but you can imagine it pointing to an SPS 2003 document library:

After that drag and drop operation, my target looks like this:

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. Veç kësaj, let’s assume there are hundreds of documents (maybe thousands) 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. Në vend të kësaj, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" view as shown:

Tani, when someone sits down to spend their allocated daily hour or two to tag migrated documents, they can use the "untagged documents" view to focus their effort:

As users tag documents, they drop off this list.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Nga kutia, 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. Megjithatë, në qoftë se përdoruesi Ngarkimet më të dhe pastaj mbyllet shfletuesin (ose përdor Windows Explorer për të ngarkoni dokumentin), ne nuk mund të detyrojnë përdoruesin për të hyrë në të dhënat meta (përsëri, nga kutia).

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.

</fund>

Abonohen në blogun tim.

Këtë javë, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, I have a greater appreciation for the kinds of problems people report on the MSDN forums and elsewhere.

The final farm configuration:

• SQL/Index/Intranet WFE inside the firewall.
• WFE in the DMZ.
• Some kind of firewall between the DMZ and the internal server.

Before we started the project, we let the client know which ports needed to be open. During the give and take, back and forth over that, we never explicitly said two important things:

1. SSL means you need a certificate.
2. The DMZ server must be part of a domain.

Day one, 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.

Në këtë pikë, Ne kemi zbuluar konfuzionin mbi certifikatë SSL dhe, trishtim, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Në kohë të thotë, ne arkitektë zgjidhje lëvizur përpara me sende të biznesit.

Një fundjavë shkon nga dhe klienti merr certifikatën.

Djalë ynë infrastruktura tregon dhe zbulon se serveri DMZ nuk është i bashkuar për çdo domain (ose një domain rrethues me besim të kufizuar ose domain intranet). We wasted nearly a 1/2 ditë në të cilat. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Another day passes and the various security committees, interested parties and (not so) innocent bystanders all agree that it’s OK to join the DMZ server with the intranet domain (this is a POC, në fund të fundit, not a production solution).

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.

Long histori e shkurtër, 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 the configuration wizard and voila! We were in business.

</fund>

Abonohen në blogun tim.

Edhe pse nuk është fjalë për fjalë e vërtetë, si një çështje praktike, një internet-ballafaqohet web front end në një DMZ duhet të jetë në një sferë (i.e. jo disa server standalone në workgroup vet pak). It doesn’t need to be in the same domain as the internal WFE(s) dhe serverat e tjera (dhe ndoshta nuk duhet të), por ajo duhet të jetë një domain.

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. Mjerisht, ne nuk mundëm të shtoni një fjali që thoshte se diku, për efekt, "the whole bloody point of this configuration is to allow your DMZ WFE server, në domenin, për t'u bashkuar me fermë të brendshëm."

Një stuhi e përsosur e ngjarjeve, ku ne thelb dukej i lënë, kur ne mund të ketë shikuar të drejtë, kurdisi një komplot për të fshehur këtë problem nga ne deri mjaft vonë në procesin e, duke parandaluar mua nga herë e betimit mia "them një lajm i keq në fillim" sundojnë.

Psherëtimë.

Abonohen në blogun tim.