امروز, 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. (If/when the network wizards tell me what it is, من این پست را به روز رسانی کنید).

Windows explorer couldn’t connect. I did some research and eventually, the network wizards said that WebDAV هستید is disabled by / not supported by / beneath the dignity of the NLB.

پس, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", I have to wonder — does NLB, by nature, disable WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Soup Nazi?

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.

I keep up to speed with them via a service provide by the good folks at 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.

(UPDATED 11/29 to explain how to access web application policy settings via the UI)

I had one of those "why is MOSS doing this to me????" moments today. در پایان, it’s all my fault.

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. Go to the site.
2. Break the security inheritance.
3. Remove every user/group from site permissions.

The above should leave just the site collection administrator with permission to see the site.

If anyone else logs in, they should no longer see the site and it should be security-trimmed from all the usual places.

اما … آن نبود. در همان زمان, 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, سرانجام, I find that at Ethan’s blog, his opening graph makes it quite simple:

خزه 2007 has a new feature called Web Application Policies. These are security permissions that is tied to a Web Application. These security settings override any security setting that is set at the Site Collection or Site (Web) level for that user.

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, اما, to strain a quote, "It does not mean what you think it means."

Access web application policies this way:

1. Go to Central Administration
2. Select Application Management
3. Select "Policy for Web Application"
4. On that screen, make sure you pick the correct web application. برای من, it defaults to the web application of central admin which may not be the one you want.

When I had this problem, I searched for the following phrases and got surprisingly little in terms of direct help on this issue:

Site actions visible for all users

Site actions visible to all users

site actions are not security trimmed

secure a MOSS site

introduction to moss security

برچسب ها: شیرپوینت

Quick and Simple Instructions:

Edit a page and add a Search Core Results web part.

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

Add the fixed keyword query (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").

یادداشت ها:

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: Departments and Products.

The product site collection contains, naturally enough, product information. Each product in the site collection aggregates data from multiple sources.

One of the departments, codes and testing, 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".

A nice benefit from this approach: We can edit the XSL from the core search results web part and generate any format that we want.

See here (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) for another blogger’s discussion on this topic.

</پایان>مشترک شدن در وبلاگ من.

اگر شما حفظ یک وبلاگ است که حداقل حداقل به شیرپوینت متصل, please let me know in comments. I would love to add you to my لیست وبلاگ.

اگر شما حفظ یک وبلاگ است که به شیرپوینت متصل نشده است، اما من می خواهم به آن اضافه کنید به هر حال, let me know. I’ll may create a separate blog list.

لطفا:

• آدرس وبلاگ شما (بدیهی است که)
• شرح کوتاه از وبلاگ خود.

I want to keep the link to "active" وبلاگ ها, 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.

سپاس ها!

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

Course managers create courses. When creating a course, the manager specifies maximum number of available seats.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" associated with that course.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. به عنوان یک نتیجه, 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" گردش کار.
4. Insert these steps (I made them the first two steps):
   1. Calculate Courses:Filled Seats minus 1 (Output to متغیر:calc)
   2. (سپس) Update item in Courses

Click Finish and you’re done.

Screen shots:

شیرپوینت طراح:

Finished workflow:

Calculate drill-down:

Update item in Courses:

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

خط پایین, این در WSS کار نمی کند 3.0 (یا MOSS).

در هنگام اضافه کردن یک ستون محاسبه شده, 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, آن را به شما می گوید:

یک یا چند ستون منابع امکان پذیر نیست., زیرا ستون ها به عنوان یک نوع داده تعریف شده است که در فرمول پشتیبانی نمی شود.

راهحل: 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.

لینک های مفید در زمینه های محاسبه شده به طور کلی:

• با استفاده از [به من] در یک ستون محاسبه شده
• نمونه هایی از عبارات فرمول (حسن نیت ارائه میدهد http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

سلب مسئولیت سریع: من باور دارم بالا به درست و دقیق, اما من دیده ام ترفندهای به اندازه کافی باهوش اینجا و آنجا در MOSS / WSS که من نمی می تواند بسیار شگفت زده (نگران اگر شما خواهد شد) 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, لطفا اجازه دهید من می دانم!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, این فرآیند (هر چند کار اصلی) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. مثلا, it should be "/sites/departments/HumanResources/…". اما, the new link is "/sites/Corporate/HumanResources/…".
• بیت های مکرر در رشته پرس و جو از عنوان, همانطور که در:

/سایت / ادارات و / HumanResources / _layouts / viewlsts.aspx?BaseType = 0?BaseType = 0?BaseType = 0?BaseType = 0

That’s easy enough to fix via site settings/navigation. Except, MOSS من با این زمانی که من سعی می کنم و آن را انجام دهید:

واقعیت این است, هیچ کس در حال انجام هر گونه تغییر وجود دارد (جدا از من, البته).

جستجوی سریع تبدیل این MSDN بحث و تبادل نظر: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

ویلیام Heurdier آن را میسازد از سادگی در یکی به اخر مانده (به عنوان 10/02/07) پست:

واقعیت این است:

برای تنظیم مجدد سرفصل های خراب, شما را به :

– حذف تمام فهرست تحت خراب عنوان

– حذف خراب شده عنوان

– از تنظیمات لیست, add a removed list to the quick launch (این بازسازی غیر خراب عنوان)

شما خوب به آن بروید….

---

کارشناس شیرپوینت – Sogeti درپوش جمینای سوئیس

من کمی گیج بود چون من نگه داشته که مایل به رفتن به صفحه ناوبری, make the change and then get hit with the "page was modified" message. Eventually, 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!

</پایان>

مشترک شدن در وبلاگ من!

تکمیلی 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. سپس, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

زمینه:

ما باید یک نیاز کسب و کار که در آن یک مدیر مهندسی محیط زیست نیاز به اطمینان حاصل شود که 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 (یا دستیار او) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

محیط:

خزه, 64 ذره, محیط ماشین مجازی (جعبه توسعه), 2 سرور (SQL بر روی سرور #1, هر چیز دیگری بر روی سرور #2).

مشکلات:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. اما, آن کار نمی کند به خوبی در خارج از جعبه (برای تماس با ما).

1. کار گردش کار برنامه ریزی شده بود برای اجرای, ever. I discovered this by reading through کریستوفر سفید (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" -آدرس HTTP://در localhost

   <Property Exist="No" />

   C:\>

   که نتیجه تعجب آور بود اما به راحتی حل:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 دقیقه بین 0 و 59" -آدرس HTTP://در localhost

   عملیات با موفقیت انجام شد.

   C:\>

   پس از انجام این کار, the first "In Progress" گردش کار به سرعت از کار اخراج و کار آن.

2. متاسفانه, the next one didn’t work as expected. خوشبختانه, Christopher refers us اینجا (http://support.microsoft.com/kb/932816). As of writing of this entry, ما در حال انتظار برای بخش فناوری اطلاعات برای به دست آوردن این هاتفیکس, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, بنابراین امیدوارم این مشکل را حل.

راهحل:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, تقریبا 7 دقیقه بعد, actually wake up and continue along with the workflow.

پرسش و پاسخ / مسائل مربوط به خطاب:

مکث تا تاریخ کار نمی کند.

مکث تا تاریخ از سرگیری نیست.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"