Azken astean zehar, nire lankide and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" travail eraikitze (gure ordenagailu eramangarriak aurka). While doing that, ran gutxi akatsak dugu urrats hauek jarraituz:

• MS word dokumentua ireki Windows Explorer bidez (erabiltzen duten WebDAV).
• Egin aldaketa bat.
• Gorde.

Konturatu ginen batzuetan (lehen aldia izan ohi) Dokumentua gorde dugu, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Ez dugu ulertu root arazoa puntu honetan, 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, errore hau lortu dugu:

Oraingo honetan, aldaketa guztietan bezala zirudien, Izan ere,, gorde, whether we answered Yes or No to the scripts question.

Izan dugu azkenik Office benetako bertsio begirada bat eta bihurtzen da travail zela MS Office 2000 zerbitzua pack 3 Laguntza erakusten ditu pean> About as "Office 2002".

Istorioaren morala: Erabili egingo dut beti. Office 2003 nire oinarrizko gutxieneko bulegoan bertsioa WebDAV eta MOSS erabiliz.

</amaiera>

Nire blog Harpidetu.

(Bilatzailea helburuetarako, error testuaren):

Line: 11807

Char: 2

Errorea: Objektu ez jabetza edo metodo hau onartzen

Code; 0

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

Scriptak exekutatzen orri honetan jarraitu nahi duzu?

Bat edo nire Oso lehenengo blog-mezu, SPS bezero migratzeko jarraitu genuen prozesu orokorra deskribatu dut 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Migrazio-proiektu, SPS asko mugitzeko modu ona aurkitu behar izan dugu 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.

Dokumentu berri honek liburutegia da:

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:\aldi baterako unitatean, baina SPS bat seinalatuz imajinatu dezakezu 2003 Dokumentu liburutegia:

Arrastatu eta jaregin eragiketa, eta ondoren, nire Helburu itxura:

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. Gainera, Demagun ez dira ehunka dokumentuen (agian milaka) 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. Horren ordez, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" ikusteko gisa agertzen dira:

Orain, norbaitek eseri behera bere esleitu eguneroko ordu bat edo bi pasatzeko migratu dokumentuak etiketatu, they can use the "untagged documents" ikusteko beren ahalegina bideratzen:

Erabiltzaile tag dokumentuak, utzi dute zerrenda honetan.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Kutxa Out, 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. Hala eta guztiz ere, erabiltzailearen fitxategiak eta, ondoren, nabigatzailea ixten bada (edo Windows Explorer erabiltzen dokumentua igo), ezin dugu behartu erabiltzaileari meta datuak sartu (berriro, koadroan out).

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.

</amaiera>

Nire blog Harpidetu.

Aste honetan, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Arazo mota estimua handiagoa txostena MSDN foroak eta beste nonbait daukat.

Azken baserriko konfigurazio:

• SQL / Index / Intranet WFE firewall barruan.
• DMZ, WFE.
• Mota batzuk suebaki DMZ eta barne-zerbitzariaren arteko.

Proiektuaren aurretik hasi ginen, we let the client know which ports needed to be open. During the give and take, atzera eta aurrera baino gehiago, esplizituki inoiz ez dugu esan bi gauza garrantzitsu:

1. SSL esan nahi du ziurtagiri bat behar duzu..
2. The DMZ server must be part of a domain.

Egun bat, 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.

Puntu honetan, nahasmena aurkitu dugu ziurtagiria SSL eta gehiagoko, zoritxarrez, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Batez besteko denbora, dugu konponbidea arkitektoek mugitu aurretik enpresa stuff.

Asteburuan A doa eta bezeroaren ziurtagiria lortzen.

Gure azpiegitura lasaia erakusten du eta deskubritzen DMZ zerbitzaria ez da edozein domeinu sartu (bai konfiantza mugatua edo intranet domeinu domeinu perimetroa). We wasted nearly a 1/2 duten egunean. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Beste egun batean pasatzen du, eta segurtasun-batzordeak hainbat, interesatuek eta (beraz, ez) errugabeen bystanders guztiak bat datoz dela OK intranet domeinu zerbitzaria DMZ sartu (hau da poc, azken finean, ez da ekoizpen irtenbide bat).

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

Long Narrazio laburren, 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 konfigurazio morroia eta voila! We were in business.

</amaiera>

Nire blog Harpidetu.

Ez da egia, nahiz eta literalki, praktiko gisa materia, Interneteko web-begira aurrean DMZ batean bukaera behar domeinu bat izango da (I.E. ez da gutxi egin lantalde zerbitzari standalone batzuk). It doesn’t need to be in the same domain as the internal WFE(s) eta beste zerbitzariak (eta, seguruenik, behar ez), baina domeinu bat izan behar du.

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. Tamalez, Esaldi bat nonbait esan gehitzeko huts egin dugu, to efektua, "the whole bloody point of this configuration is to allow your DMZ WFE server, domeinu bat, barne baserria batzeko."

Ekitaldi ekaitz perfektua A, non dugu, funtsean, aurpegia geratzen denean begiratu izan dugu agian eskubidea, konspiratu arazo hau ezkutatzeko, gugandik nahiko prozesuan berandu arte, beraz, niri saihesten dei batetik nire "esango albiste txarra goiz" araua.

Sigh.

Nire blog Harpidetu.