Uimh anraith ar do shon! Is Cisco an Nazi Anraith de tháirgí NLB?

Sa lá atá inniu, I tried to access a document library via windows explorer. This doc lib is living inside a system that consists of two WFE’s load balanced by some kind of Cisco NLB solution. (Má / nuair a wizards líonra insint dom cad é, Feicfidh mé an post seo cothrom le dáta).

Windows explorer couldn’t connect. I did some research and eventually, an wizards líonra dúirt go WebDAV faoi ​​mhíchumas ag / Ní thacaíonn / beneath the dignity of the NLB.

Mar sin,, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", Caithfidh mé a Wonder — dhéanann NLB, ag nádúr, dhíchumasú WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Anraith Nazi?

Bainistíochta CAONAIGH / Timpeallachtaí SSU — coinneáil suas le bonn eolais Microsoft

Microsoft creates knowledge base articles day in and day out and some of those are darned important to know about if you live in the SharePoint world.

Mé a choinneáil suas chun dlús a chur leo trí sheirbhís a chur ar fáil ag an folks go maith ag www.kbalertz.com. KBAlertz enables you to sign up for your favorite MS technology and they send you digest versions of Microsoft KB articles via email.

Polasaí Iarratais Gréasáin, Láithreáin Slándáil agus Slándáil Bearradh — Know do chumraíocht

(Updated 11/29 a mhíniú conas rochtain a suímh ghréasáin polasaí i bhfeidhm tríd an Chomhéadain)

I had one of those "why is MOSS doing this to me????" moments today. Sa deireadh, tá sé go léir mo locht.

We have an enterprise MOSS project going on and we want to secure "place holder" sites so that no user may access it or see it. That’s easy:

  1. Téigh go dtí an láithreán.
  2. Briseadh an oidhreacht slándála.
  3. Bain gach úsáideora / grúpa ó ceadanna láithreán.

Ba chóir an thuas fhágáil ach an riarthóir bailiúcháin suíomh le cead a fheiceáil ar an suíomh.

Má logs duine ar bith eile i, ba chóir dóibh a thuilleadh a fheiceáil ar an suíomh seo agus ba chóir é a bheith slándála-bearrtha ó na háiteanna is gnách.

Ach … Ní raibh sé. Ag an am céanna, I suddenly realize that my "Joe User" standard user test account with no priv’s other than restricted read access has a "Site Actions" choice everywhere he goes. I double check one thing and double check something else. I pick up the phone to call a colleague, but put it down and check something else. I go for a walk and try everything all over again. I call a colleague and leave a message. And then, ar deireadh, I find that at Ethan’s blog, his opening graph makes it quite simple:

CAONAIGH 2007 has a new feature called Web Application Policies. Tá na ceadanna slándála go bhfuil ceangailte le Iarratais Gréasáin. Tá na socruithe slándála gcealófaí leis aon socrú slándála atá leagtha ag an mBailiúchán Suíomh nó an tSuímh (Gréasáin) leibhéal don úsáideoir.

A quick visit to web application policies shows that "NT Authority\authenticated users" had been granted Full Read. I removed them from the list and everything finally started working as expected. I believe they were added in the first place by someone with the mistaken impression that that is best method to grant read access to everyone in the enterprise. It does, ach, le brú a ceanglófar, "It does not mean what you think it means."

Access web application policies this way:

  1. Téigh go dtí Riarachán Lárnach
  2. Roghnaigh Bainistíochta Iarratais
  3. Select "Policy for Web Application"
  4. On that screen, make sure you pick the correct web application. Maidir liom féin, it defaults to the web application of central admin which may not be the one you want.

Nuair a bhí mé an fhadhb seo, Chuardach mé do na frásaí seo a leanas agus fuair ionadh beag i dtéarmaí cabhair dhíreach ar an tsaincheist seo:

Gníomhartha suíomh le feiceáil do gach úsáideoir

Gníomhartha suíomh le feiceáil ar na húsáideoirí go léir

Ní ghníomhartha suíomh seo bearrtha slándála

dhaingniú láithreán CAONAIGH

a thabhairt isteach chun caonach slándála

Clibeanna Technorati:

Quick agus Simplí: Bain úsáid Iarratas Eochairfhocal Seasta i Results Core Cuardaigh

Treoracha Quick agus Simplí:

Cuir an leathanach agus cuir Torthaí Core chuid gréasáin Cuardaigh.

Edit that web part and expand "Fixed Keyword Query".

Cuir an cheist eochairfhocal seasta (e.g. ContentType:"Training invoice" TrainingInvoiceNumber:1111)

Expand Results Query Options and change "Cross-Web Part query ID" to a value other than "User Query" (e.g. "Query 2").

Nótaí:

Using core search results in this manner allowed me to create a page that shows information from another site collection. The client has two major site collections: Ranna agus Táirgí.

Éard atá sa bhailiúchán láithreán táirge, go nádúrtha go leor, product information. Each product in the site collection aggregates data from multiple sources.

Ceann de na ranna, cóid agus tástáil, is on such source. When users access product XYZ, they should see codes and testing data directly on the XYZ main page. Since codes and testing is hosted in another site collection, it’s a little awkward. We decided to use the core search results web part since search spans site collections. Codes and Testing manages product data via a custom list that is constrained by a specific content type. Aa keyword query that uses first the content type and then the product number narrow down the search to a single row in the custom list.

The keyword query above is an AND. It returns documents of content type "Training Invoice" and where the invoice number equals "1111".

Buntáiste deas as an gcur chuige seo: We can edit the XSL from the core search results web part and generate any format that we want.

Féach anseo (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) le plé blagaire eile ar an ábhar seo.

</deireadh>Liostáil le mo bhlag.

Inis dom faoi do bhlag!

Má tá tú a choinneáil ar bhlag go bhfuil baint aige ar a laghad minimally ar SharePoint, please let me know in comments. I would love to add you to my liosta bhlag.

Má tá tú a choinneáil ar bhlag nach bhfuil nasctha le SharePoint ach ba mhaith liom a chur air ar aon nós, in iúl dom. I’ll may create a separate blog list.

Le do thoil a thabhairt:

  • Do bhlag URL (ar ndóigh)
  • Tá cur síos gairid ar do bhlag.

I want to keep the link to "active" blogs, which I’m roughly defining as one post per week and minimum three months old. If you don’t meet that "requirement" add your name to comments anyway. It’s *my* list so I can break my own rule if I want to.

Go raibh maith agat!

Sceideal Oiliúint Fostaithe agus Ábhair Teimpléad — Bug decrement sa teimpléad

The client noticed a bug today with the above mentioned template.

Course managers create courses. When creating a course, Sonraíonn an bainisteoir líon uasta na suíochán atá ar fáil.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" a bhaineann leis an gcúrsa.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Mar thoradh air sin, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, no more self-service registration is allowed.

Fortunately, Microsoft provides the workflow for this process. Even better, it’s a straight-forward workflow created via SharePoint Designer.

Follow these high level steps to fix it:

  1. Fire up SDP.
  2. Access the site based off the training template.
  3. Access "Attendee unregistration" sreabhadh oibre.
  4. Insert these steps (Rinne mé iad an dá chéad chéimeanna):
    1. Ríomh Cúrsaí:Suíocháin Líonta lúide 1 (Aschur a Athróg:Calc)
    2. (ansin) Ítim Nuashonraigh i Cúrsaí

Cliceáil Críochnaigh agus tú ag déanamh.

Shots Scáileán:


SharePoint Dearthóir:

íomhá

Sreabhadh oibre Críochnaithe:

íomhá

Ríomh druileáil-síos:

íomhá

Mír Nuashonraigh i gCúrsaí:

íomhá

Tabhair dea-scéal go minic; a thabhairt nuacht olc go luath

Bainim ina chomhairleoir do a lán de na blianta anois agus mar a fhios ag aon sainchomhairleoir taithí, good communication is one of the key pillars to the successful delivery of a project. Tá sé chomh soiléir, it’s really almost boring to talk about. This isn’t a post about generic communication. Ina áit sin, Tá mé ag scríobh mar gheall ar an taobh dorcha na cumarsáide — cumarsáid a dhéanamh droch-nuacht.

Ní gá a rá go bhfuil ag tabhairt dea-scéal don chliant a rinneadh go léir an t-am, as often as possible. Who doesn’t want to give good news? Who doesn’t like to hear good news?

Ar an taobh smeach, bad news is no fun at all. I have always struggled with this. In the earlier days of my career, Bheadh ​​a fhios agam go raibh rud éigin awry le tionscadal agus in ionad ag insint an cliant, I would work longer hours to try and solve the problem. I would enjoin my team to work harder. It’s a natural enough impulse to think that a super-human effort can save the day. Some times this works, some times it does not. Even when it "works" it’s often a mixed bag. Is the quality of the deliverable really up to spec when key parts have been developed over several 60 go 80 seachtaine uair an chloig?

Cad é an bealach is fearr chun déileáil le droch-nuacht? The answer is: tell it early. Don’t wait until one week before the project budget will be consumed. If you know six weeks out that there simply isn’t enough time to deliver some bit of promised functionality, tell the client right then and there. The client may get upset (is dócha), there may be incriminations and accusations and hurt feelings. Ach, nuair a mothúcháin cool as, there’s still six weeks left on the project. Six weeks is a good chunk of time. There’s time to adjust plans, sceidil athrú, a fháil ar an liathróid rollta ar síntí bhuiséad (luck maith!) and just generally come to grips with the "facts on the ground" and devise a new plan that still results in a successful project.

Cás i bpointe: Tá mé ag obair ar thionscadal arb iad is sainairíonna:

  • T&E budget with a capped "Not to exceed" méid Dollar.
  • A "best efforts will be made" gealltanas a sheachadadh X, Y agus Z faoi dheireadh tionscadail.
  • Lack of promised key resources on the client side. These resources were not withheld on purpose, nor for any "bad" cúis, ach coinníodh siar iad.
  • A dawning realization as the project passed the half-way point that we were not going to be able to deliver "Z" (go príomha toisc nach raibh na hacmhainní atá geallta atá ar fáil iarbhír).
  • Regular status reports and "CYA" doiciméadú a tacaíocht dúinn (an fhoireann i gcomhairle le) up.
  • Fhoireann cur i bhfeidhm go docht knit le comhalta a tarraingíodh as an eagraíocht dul i gcomhairle le (mo chuideachta) agus an cliant.
  • Fhoireann bainistíochta i bhfad i gcéin, in both a metaphorical and physical sense. The management team was focused on another large enterprise project and due to space constraints, bhí an fhoireann chun feidhme lonnaithe i bhfoirgneamh ar leith ar an gcampas, down a hill and relatively far way from "civilization".

Le thart ar shé seachtaine fágtha ar an mbuiséad an tionscadail, muid (an fhoireann cur i bhfeidhm) knew that we were trouble. The contract said that we needed to deliver "Z". Even though the project is time & materials and even though we only promised "best efforts" a sheachadadh Z agus cé go raibh muid údar mór do iarraidh a sheachadadh … Is é an líne bun nach raibh sé ag lorg maith — Ní raibh muid ag dul a sheachadadh Z i gcruth ar chaighdeán a bheadh ​​a dhéanamh duine ar bith a bheith bródúil.

Ag aithint seo, Chuaigh muid chuig an mbainistíocht agus dúirt sé leo go mbeadh an buiséad tionscadail a chaitheamh faoi dháta áirithe agus go raibh muid i dtrioblóid le Z.

A firestorm mion erupted thar an lá atá amach romhainn.

Lá 1: Glaonna fhoireann bhainistíochta a fhoireann do chruinniú speisialta (muid, ní na comhairleoirí Tugtar cuireadh). Contracts are printed and handed out to everyone and a line-by-line review ensues. Management puts the staff members on the defensive. I don’t think the phrase "Stócólm Siondróm" Tá * iarbhír * in úsáid, ach gheobhaidh tú an pictiúr. We’re a tight-knit group, tar éis an tsaoil, agus tá an fhoireann ag obair le linn comhairleoirí lá isteach agus amach ar feadh cúpla mí anois.

Lá 2: Management calls another staff meeting. They feel a little better. They want options and ideas for moving forward. They realize there’s still six weeks remaining in the current project budget, which is still a decent bit of time. One of the action items: sceideal cruinniú le foireann cur i bhfeidhm iomlán (lena n-áirítear comhairleoirí).

Lá 5: Buaileann foireann iomlán, constructive meeting ensues and a new achievable plan put into place. Even better, we’ve already begun discussing phase two and the client invites us to prepare proposals for that phase immediately.

Má bhí d'fhan muid go dtí fhan díreach trí seachtaine, nó níos measa fós, ceann amháin nó dhá sheachtain, it would have been much different. Instead of a constructive meeting to re-align the project, ba mhaith linn a bheith ag tarraingt amach tuairiscí stádais, parsing the contract and reviewing old emails to justify this or that decision. We would have "won" but is it really "winning" sa chás seo?

Mar sin,, má tá tú a thabhairt nuacht olc, give it early. Bad news given late isn’t just bad, Tá sé Uafásach.

Ag baint úsáide as “Duine nó an Grúpa” i gcolún ríomh

People commonly ask about using a column of data type "Person or Group" in another column of data type "Calculated".

Bottom line, nach bhfuil an obair i SSU 3.0 (nó CAONAIGH).

Nuair a chur colún ríomh, WSS shows the list of fields it allows you to use for the calculation. If you type in the name of a column that is not in its list, Insíonn sé duit:

Ní amháin nó níos mó tagairtí colún Tá cead, mar go bhfuil sainmhínithe na colúin mar chineál sonraí ann nach dtacaítear leis i foirmlí.

Workaround: Use an event handler. The event handler fires when the user saves the item. It performs the update you would have wanted the calculated column to do for you.

Naisc úsáideacha ar réimsí arna ríomh i gcoitinne:

Quick Fógra dlithiúil-séantóir: Creidim go bhfuil an thuas a bheith fíor agus cruinn, ach mé le feiceáil go leor cleasanna cliste anseo agus ansiúd sa MOSS / SSU go ní ba mhaith liom a bheith an-ionadh (agog más maith leat) if someone has figured out a way to do this without resorting to code. If you’ve figured out clever work-around or know someone that did, cuir in iúl dom!

MOSS / SSU insíonn mé: “Tá an leathanach modhnaithe le údar eile ar …” ach i ndáiríre, Ní raibh sé.

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, an bpróiseas seo (cé go obair sa phríomh-) broke some navigation links in the quick launch. The broken links are characterized by:

  • Wrong URL. Mar shampla, it should be "/sites/departments/HumanResources/…". Mar sin féin, the new link is "/sites/Corporate/HumanResources/…".
  • Giotán Arís agus arís eile ar an teaghrán cheist an cheannteidil, mar atá i:

/suímh / ranna / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS i láthair liom leis seo nuair a thugaim agus é a dhéanamh:

íomhá

Is é fírinne, Tá aon duine a dhéanamh ar aon athrú ann (leataobh ó dom, ar ndóigh).

A cuardach tapa casadh suas an fóraim phlé MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier leagann sé amach nicely sa leathdhéanach an (mar ar 10/02/07) phost:

Is fíric:

Chun a athshocrú ceannteidil truaillithe, caithfidh tú a :

– bhaint as na liostaí faoin gceannteideal truaillithe

– bain gceannteideal truaillithe

– Ón liosta suímh, add a removed list to the quick launch (Seo a athghiniúint neamh truaillithe ceannteideal)

Tá tú ansin go maith chun dul….


Sharepoint Saineolaithe – Cap Gemini Sogeti Eilvéis

Bhí mé beagán mearbhall mar gheall ar choinnigh mé ag iarraidh dul go dtí an leathanach nascleanúint, make the change and then get hit with the "page was modified" message. Faoi dheireadh, I realized I had to go to the list settings and remove/add it to quick launch. That did the trick. Happy times are here again!

</deireadh>

Liostáil le mo bhlag!

Fadhbanna le “Sos Go dtí Dáta” gníomhaíocht i sreabhadh oibre SPD-cruthaíodh

Suas chun dáta 12/10/07: Hotfix as described in MSDN KB929816 solved the problem for us mentioned below. Obtain the hotfix and then install on each server on the farm. Ansin,, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Cúlra:

Tá riachtanas gnó nuair is gá bainisteoir innealtóireachta comhshaoil ​​a chinntiú go 30 some-odd manufacturing locations located throughout the United States needs to ensure that those plants file for their various state-mandated permits in a timely fashion. One approach we’ve investigated leverages the "Pause Until Date" activity available to us via SharePoint Designer worfklow. The engineering manager (nó a cúnta) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Comhshaol:

CAONAIGH, 64 giotán, timpeallacht meaisín fíorúil (bosca forbartha), 2 freastalaithe (SQL ar an bhfreastalaí #1, gach rud eile ar an bhfreastalaí #2).

Fadhbanna:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Mar sin féin, ní oibríonn sé go maith as an bhosca (dúinn).

  1. Ní raibh an post sreabhadh oibre sceidealta a reáchtáil, ever. I discovered this by reading through Christopher White (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:

    C:\>stsadm -o getproperty -propertyname "job-workflow" -moladh http://localhost

    <Property Exist="No" />

    C:\>

    Ba é sin de bharr iontas ach go héasca réiteach:

    C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 nóiméad idir 0 agus 59" -moladh http://localhost

    Oibríocht i gcrích go sásúil.

    C:\>

    Ar déanamh sin, the first "In Progress" sreabhadh oibre fired suas go tapa agus rinne sé post.

  2. Faraor, the next one didn’t work as expected. Thankfully, Christopher refers us anseo (http://support.microsoft.com/kb/932816). As of writing of this entry, táimid ag fanacht leis an roinn TF sin a fháil hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, mar sin tá súil againn go mbeidh sé seo an fhadhb a réiteach.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, garbh 7 nóiméad ina dhiaidh sin, actually wake up and continue along with the workflow.

Ceisteanna / Ceisteanna Aghaidh:

Ní Sos Go dtí Dáta obair.

Ní Sos Go dtí Dáta atosú.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"