Durante a semana pasada, meu compañeiro and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" estación de traballo de construción (por oposición aos nosos ordenadores portátiles). While doing that, que funcionou nalgúns erros, seguindo estes pasos:

• Abra un documento de MS Word a través de Windows Explorer (que utiliza WebDAV).
• Fai un cambio.
• Salvalo.

Nós vimos a entender que algunhas veces (xeralmente a primeira vez) que salvo o documento, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Non entender a raíz do problema neste momento, 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, agora teño ese erro:

Este tempo, parecía que cada cambio foi, de feito, salvo, whether we answered Yes or No to the scripts question.

Finalmente tivemos un ollo á versión actual do Office e verifícase que a estación estaba correndo MS Office 2000 con service pack 3 que aparece en Help -> About as "Office 2002".

A moral da historia: Sempre vou usar o Office 2003 como a miña versión mínima oficina de base ao usar WebDAV e Moss.

</final>

Rexístrate para o meu blog.

(Para fins de investigación, este é o texto do erro):

Liña: 11807

Carbonizar: 2

Erro: Obxecto non soporta esta propiedade ou método

Código; 0

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

Desexa continuar a executar scripts nesta páxina?

Nunha ou miña primeiros artigos, I describiu o proceso no seu conxunto, seguimos para migrar un cliente do SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Para que o proxecto de migración, tivemos de atopar unha boa forma de mover unha gran cantidade de 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.

Esta é unha nova biblioteca de documentos:

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. Ademais, imos supor que hai centos de documentos (quizais milleiros) 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. Pola, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" ver como se mostra:

Agora, cando alguén se senta para pasar a súa hora diaria alocados ou dous para marcar documentos migraron, 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. Fóra da caixa, 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. Con todo, if the user uploads and then closes the browser (or uses windows explorer to upload the document), we can’t force the user to enter meta data (novo, para fóra da caixa).

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.

</final>

Rexístrate para o meu blog.

Esta semana, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Teño unha maior valoración para os tipos de problemas que as persoas relatan foros MSDN e noutros lugares.

A configuración final granxa:

• SQL / Index / Intranet WFE dentro do firewall.
• WFE na DMZ.
• Algún tipo de devasa entre o servidor interno e DMZ.

Antes de comezar o proxecto, we let the client know which ports needed to be open. During the give and take, adiante e cara atrás ao longo dese, nunca dixo explícitamente dúas cousas importantes:

1. SSL significa que precisa dun certificado.
2. The DMZ server must be part of a domain.

O primeiro día, 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.

Neste punto, descubrimos a confusión sobre o certificado e SSL, tristemente, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Nese medio tempo, nós, arquitectos de solucións avanzou co material de negocios.

Un fin de semana pasa e que o cliente obtén o certificado.

Nosa infraestrutura cara aparece e descobre que o servidor DMZ non está asociado a calquera dominio (ou un dominio de perímetro con confianza limitada ou o dominio intranet). We wasted nearly a 1/2 día en que. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Outro día pasa e as distintas comisións de seguridade, partes interesadas e (non tan) inocentes todos coinciden en que non hai problema en unirse ao servidor DMZ co dominio intranet (este é un POC, ao final, non é unha solución de produción).

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" Estado.

Longa historia curta, 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-foi o asistente de configuración e listo! We were in business.

</final>

Rexístrate para o meu blog.

Aínda que non é literalmente certo, Como unha cuestión práctica, unha Internet dedicado a web front-end nunha DMZ debe estar nun dominio (i.e. non un servidor independente no seu propio pequeno grupo de traballo). It doesn’t need to be in the same domain as the internal WFE(s) e outros servidores (e probablemente non debería), but it needs to be a 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. Desafortunadamente, we failed to add a sentence somewhere that said, to the effect, "the whole bloody point of this configuration is to allow your DMZ WFE server, in a domain, to join the internal farm."

A perfect storm of events, where we basically looked left when we might have looked right, conspired to hide this problem from us until fairly late in the process, thus preventing me from invoking my "tell bad news early" rule.

Sigh.

Rexístrate para o meu blog.