بایگانی ماهانه: فوریه 2008

یکشنبه های خنده دار: “نه برای صادرات”

پاسخ دهید

بازگشت اطراف 1998, the company I worked for at the time received some funding to create a new e-commerce product. We had the full gamut of business requirements to meet. It had to be fast, آسان برای کاربران نهایی, زرق و برق دار, چند زبان, غیره. Sad to say, I probably haven’t had as an ambitious set of work to accomplish since those heady days.

This effort pre-dated Microsoft.NET. Plain vanilla ASP was still somewhat new (or least very unfamiliar to my company). "Brick and mortar" companies were doomed. Doomed! This is to say that it was pioneering work. Not Hadron Collider pioneering work, but for us in our little world, it was pioneering work.

We were crazy busy. We were doing mini POC’s almost every day, figuring out how to maintain state in an inherently stateless medium, figuring out multi-language issues, row-level security. We even had create a vocabulary to define basic terms (I preferred state-persistent but for some reason, the awkward "statefull" won the day).

As we were madly inventing this product, the marketing and sales people were out there trying to sell it. Somehow, they managed to sell it to our nightmare scenario. Even though we were designing and implementing an enterprise solution, we really didn’t expect the first customer to use every last feature we built into the product day zero. This customer needed multi-language, a radically different user interface from the "standard" system but with the same business logic. Multi-language was especially hard in this case, because we always focused on Spanish or French, but in this case, it was Chinese (which is a double-byte character set and required special handling given the technology we used).

Fast forward a few months and I’m on a Northwest airlines flight to Beijing. I’ve been so busy preparing for this trip that I have almost no idea what it’s like to go there. I had read a book once about how an American had been in China for several years and had learned the language. One day he was walking the city and asked some people for directions. The conversation went something this:

  • American: "Could you tell me how to get to [XX] street?"
  • Chinese: "Sorry, we don’t speak English".
  • American: "Oh, well I speak Mandarin." and he asked them again in Chinese, but more clearly (as best he could).
  • Chinese: Very politely, "Sorry, we don’t speak English".

The conversation went on like that for bit and the American gave up in frustration. As he was leaving them he overheard one man speaking to the other, "I could have sworn he was asking for directions to [XX] street."

I had picked up a few bits and pieces of other China-related quasi-information and "helpful advice":

  • A Korean co-worked told me that the I needed to be careful of the Chinese because "they would try to get me drunk and take advantage of you" in the sense of pressuring me into bad business decisions.
  • We were not allowed to drive cars (there was some confusion as to whether this was a custom, a legal requirement or just the client’s rule).
  • There were special rules for going through customs.
  • We were not allowed to use American money for anything.
  • You’re not supposed to leave tips. It’s insulting if you do.

And finally, I had relatively fresh memories the Tiananmen massacre. When I was at college, I remember seeing real-time Usenet postings as the world looked on in horror.

In short, I was very nervous. I wasn’t just normal-nervous in the sense that I was delivering a solution that was orders of magnitude more complicated than anything I had ever done before. I was also worried about accidentally breaking a rule that could get me in trouble.

I’m on this 14 hour flight and though it was business class, 14 hours is a damned long time. There are only so many ways to entertain yourself by reading, watching movies or playing with the magnetized cutlery. Even a really good book is hard to read for several hours straight.

Eventually, I started to read the packaging material on a piece of software I was hand-carrying with me to the client, Netscape’s web server. I’m reading the hardware/software requirements, the marketing blurbs, looking at the pretty picture and suddenly, I zero in on the giant "NOT FOR EXPORT" warning, something about 128 bit encryption. I stuffed the box back into my carry bag, warning face-down (as if that would have helped) and tried to keep visions of Midnight Express out of my head.

Looking back on it now, I should have been worried, if at all, when I left the U.S., not when I was entering China 🙂 Nothing untoward happened and I still consider that to be the best and most memorable business trip I’ve had the pleasure of making.

</پایان>

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

برچسب ها: ,

راه حل: SPQuery Does Not Search Folders

3 پاسخ ها

This past week I was implementing an "evolving" solution for a client that uses BDC and SPQuery and ran into some difficulty using SPQuery against a document library containing folders. خط پایین: assign "recursive" to the view attribute of the query.

My scenario:

  • On Monday, I upload a document and supply some meta data.
  • The following week, I upload a new document. Much of this new document’s meta data is based on the document I uploaded on Monday (which we call the "master document").
  • We’ve created a web service façade that provides a BDC-friendly interface to the list so that users can easily locate that Monday document via a title search.
  • A BDC data column provides a friendly user interface. (This is part of my attempt at using BDC for a more friendly Lookup column).

The final BDC façade service uses a query like this to do the lookup:

 // Used U2U tool to assist in generating this CAML query.
      oQuery.Query =
        "<جایی که>";

      اگر (titleFilter.Length > 0)
        oQuery.Query  =
          "  <و>";

      oQuery.Query  =
        "    <و>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + minId + "</ارزش>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</ارزش>" +
        "      </Leq>" +
        "    </و>";

      اگر (titleFilter.Length > 0)
        oQuery.Query  =
          "    <شامل>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</ارزش>" +
          "    </شامل>" +
          "  </و>";
      oQuery.Query  =
        "</جایی که>";

During the initial stage of development, this worked great. اما, we introduced folders into the directory to solve some problems and suddenly, my BDC picker wouldn’t return any results. I tracked this down to the fact that the SPQuery would never return any results. We used folders primarily to allow multiple files with the same name to be uploaded but with different meta data. When the file is uploaded, we create a folder based on the list item’s ID and then move the file there (I wrote about that اینجا; we’ve had mixed results with this approach but on the whole, it’s working well). The user don’t care about folders and in fact, don’t really understand that there are any folders. We have configured all the views on the library to show items without regard to folders.

I hit this problem twice as the technical implementation evolved and solved it differently each time. The first time, I wasn’t using the CONTAINS operator in the query. Without a CONTAINS operator, I was able to solve the problem by specifying the view on the SPQuery’s contructor. Instead of using the default constructor:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = جدید SPQuery();

I instead used a constructor that specified a view:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = جدید SPQuery(oList.Views["All Documents"]);

That solved the problem and I started to get my results.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, so far as I can tell, does not work with the view the same way as the a simpler GEQ / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", همانطور که در:

oQuery.ViewAttributes = "Scope=\"Recursive\"";

That solved the problem for CONTAINS. در واقع, this also solved my original search problem and if I had specified the recursive attribute the first time, I would not have run into the issue again.

The fact that a view-based SPQuery works for some operators (GEQ/LEQ) and not others (CONTAINS), coupled with the fact that KPIs don’t seem to work at all with folder-containing document libraries leads me to believe that SPQuery has some orthogonality issues.

Special Thanks:

  • The good folks at U2U and their query tool.
  • Michael Hoffer’s great "learning by doing" پست وبلاگ, comments and responses.

</پایان>

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

خزه اشکال KPI? لیست شاخص با پوشه وابسته به کتابخانهی سند

1 پاسخ

تکمیلی 02/29/08: I solved this problem by creating a folder and then assigning a content type to the folder which has the meta data I need for the KPIs. I described that in a little more detail here.

We have implemented a technical solution where users upload documents to a document library. An event receiver creates a directory and moves the file to that directory (using a technique similar to what I wrote about اینجا). We’ve successfully navigated around the potential issues caused by event receivers that rename uploaded files (mainly because users never start their document by clicking on "New" but instead create the docs locally and then upload them).

The meta data for these documents includes a Yes/No site column called "Urgent" and another site column called "Status". We need to meet a business requirement that shows the percentage of "Urgent" documents whose status is "Pending".

انجام این کار معمولاً ساده است و من چیزی شبیه به این را در شیرپوینت بیگل توصیف کردم با تعداد زیادی عکس از صفحه نمایش اگر علاقه دارید.

به طور خلاصه, من زیر:

  • Create a view on the doc library called "Pending".
  • نمای را طوری پیکربندی کنید که ساختار پوشه را نادیده بگیرد.
  • یک لیست KPI ایجاد کنید.
  • Create an indicator in the list that points to the doc lib and that "Pending" دیدن.

این به سادگی کار نمی کند. KPI هدف من را نشان می دهد (e.g. پنج سند فوری) اما همیشه تعداد واقعی اسناد فوری را صفر نشان می دهد. به طور متناقض, اگر به جزئیات بپردازید, این پنج سند فوری را در لیست نشان می دهد. I created a very simple scenario with two documents, one in a folder and one not. Here is the screen shot:

تصویر

The above screen shot clearly shows there are two documents in the view but the "value" is one. The "CamlSchema" with blank document Id is in the root folder and the other is in a folder named "84".

It appears to me that even though you specify a view, the KPI doesn’t honor the "show all items without folders" setting and instead, confines itself to the root folder.

If I’m wrong, please drop me a line or leave a comment.

</پایان>

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

برچسب ها:

SPD گردش کار “جمع آوری اطلاعات از کاربر”: اصلاح فرم وظیفه تولید

4 پاسخ ها

I’m working on a project that uses five different SharePoint Designer work flows to handle some document approvals. SPD provides the "collect data from a user" اقدام به طوری که ما می تواند کاربر را از بیت های مختلف از اطلاعات به موقع, از جمله اینکه آیا آنها به آن تصویب, برخی از نظرات و شاید آنچه که برای شام شب دیگر بپرسید.

The forms are perfectly functional. They are tied to a task list as a content type. آنها عبارتند از 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. اما, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, ما نیاز به توسل به ترفندهای مختلف در اطراف آن (مثلا, تعیین اولویت در کار).

من نیاز به ارائه یک لینک در این فرم کار که باز کردن خواص نظر (dispform.asxp) "قلم دوم از اقلام مربوط به" in a new window. This provides one-click access to the meta data of the related item. This is what I mean:

تصویر

خوشبختانه, we can do that and it’s not very hard. Broadly speaking, آتش تا SPD, navigate to the directory that houses the workflow files and open the ASPX file you want to modify. These are just classic XSL transform instructions and if you’ve mucked about with itemstyle.xsl, جستجو و یا سایر حالات XSL, this will be easy for you. در واقع, که من پیدا کردم آن را به طور کلی آسان تر از فرم تولید شده است تا حدودی ساده تر به دنبال در مقایسه با نتایج جستجو وب بخش اصلی (و یا CWQP کابوس).

البته, there is one major pitfall. SPD’s workflow editor expects full control over that file. If you modify it, SPD will happily overwrite your changes give the right set of circumstances. I did two quick tests to see how bad this could get. They both presuppose that you’ve crafted a valid SPD workflow that uses the "collect data from a user" گام.

تست 1:

  • اصلاح فایل ASPX با دست.
  • آزمون (کنترل کنید که تغییرات خود را به درستی ذخیره شد و چیزی را پاره کند).
  • باز کردن گردش کار و اضافه کردن یک عمل نامربوط (از قبیل "ورود به سیستم به تاریخ").
  • صرفه جویی در گردش کار.

نتیجه: در این مورد, SPD دوباره ایجاد فرم.

تست 2:

  • همه گروه همان #1 جز به طور مستقیم "جمع آوری اطلاعات از یک کاربر را تغییر دهید" اقدام.

نتیجه: این دوباره ایجاد فرم از ابتدا, بیش از نوشتن همه تغییرات مورد نظرتان را در.

یادداشت های نهایی:

  • حداقل دو عملیات SPD ایجاد اشکال مثل این: "جمع آوری اطلاعات از کاربر" and "Assign To Do Item". Both of these actions’ اشکال را می توان دستی تغییر.
  • من قادر به ایجاد لینک من به dispform.aspx بود، زیرا, در این مورد, the relate item always has its ID embedded in the related item’s URL. I was able to extract it and then build an <یک عکاس هنگام عکسبرداری> based on it to provide the one-click meta data access feature. It’s unlikely that your URL follows this rule. There may be other ways to get the ID of the related item but I have not had to cross that bridge, بنابراین من نمی دانم اگر می شود به طرف دیگر از شکاف.
  • من بررسی, اما من شگفت زده خواهد بود اگر نوعی از فایل های قالب را در وجود دارد 12 کندو که من می توانم تغییر را تحت تاثیر قرار SPD تولید اشکال پیش فرض (ما می توانیم قالب های هشدار را تغییر دهید).

</پایان>

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

آیا “خطا مشخص نشده” پیام واقعا از ردیابی پشته بهتر?

3 پاسخ ها

من خواندن Madhur پست وبلاگ در مورد چگونگی را قادر می سازد پشته نمایش ردیابی و در حال حاضر من نگرانم: چرا ما همیشه یک مسیر بسته را نشان می دهد?

که با آن قانون آمد و چرا من به آن را دنبال می کنیم?

End users will know something is wrong in either case. At least with a stack trace, آنها می توانند با printscreen کنترل را فشار دهید, copy/paste into an email and send it to IT. That would clearly reduce the time and effort required to solve the issue.

</پایان>

برچسب ها:

یکشنبه (شرم آور) خنده دار: “نام من پل گالوین است”

1 پاسخ

دسته سال پیش, my boss asked me to train some users on a product called Results. Results is an end user reporting tool. It’s roughly analogous to SQL Server Reporting Service or Crystal. در آن زمان, آن را به اجرا در لوله های سبز طراحی شده است (e.g. عین 50 پایانه) connected to a Unix box via telnet.

My default answer to any question that starts with "Can you … " is "Yes" و این جایی است که مشکل آغاز شده.

مشتری یک شرکت شیمیایی در جنوب کالیفرنیا بود و فقط در مورد پیچیده پیاده سازی ERP بزرگ بر اساس QAD MFG/PRO. The implementation plan now called for training power end users on the Results product.

I wasn’t a big user of this tool and had certainly never trained anyone before. اما, من تعدادی از کلاس های آموزشی دیگر انجام شده بود و سریع روی پای من بود, so I was not too worried. Dennis, نمایش نتایج: از شماره واقعی تمام وقت مربی, had given me his training material. Looking back on it now, it’s really quite absurd. I didn’t know the product well, had never been formally trained on it and had certainly never taught it. What business did I have training anyone on it?

به چیزهای پیچیده لجستیکی, I was asked to go and meet someone in Chicago as part of a pre-sales engagement along the way. The plan was to fly out of New Jersey, رفتن به شیکاگو, meet for an hour with prospect and then continue on to California.

خوب, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. پس, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, پیدا کنم که مشتری در حال یادگیری کمتر از 24 hours before my arrival that "Paul Galvin" آموزش کلاس, not Dennis. The client loves Dennis. They want to know "who is this Paul Galvin person?" "Why should we trust him?" "Why should we pay for him?" Dennis obviously didn’t subscribe to my "در اوایل دادن خبر بد" philosophy. Awesome.

من در فرودگاه و برای برخی از دلیل فوق العاده احمقانه می رسند, I had checked my luggage. I made it to LAX but my luggage did not. برای من, از دست دادن توشه بسیاری مانند رفتن را از طریق هفت مرحله از غم و اندوه. Eventually I make it to the hotel, بدون توشه, خسته, گرسنه و پوشیدن من (در حال حاضر, بسیار مچاله) business suit. It takes a long time to travel from Newark — اهار — به مشتری — بازگشت به اهار — و در نهایت به LAX.

من در نهایت خودم را در اتاق هتل نشسته, خوردن نوار snickers است, exhausted and trying to drum up the energy to scan through the training material again so that I won’t look like a complete ass in front of the class. This was a bit of a low point for me at the time.

بیدار شدم روز بعد, did my best to smooth out my suit so that I didn’t look like Willy Loman on a bad day and headed on over to the client. As is so often the case, او در فرد خوب بود, polite and very pleasant. This stood in stark contrast to her extremely angry emails/voicemails from the previous day. She leads me about 3 miles through building after building to a sectioned off area in a giant chemical warehouse where we will conduct the class for the next three days. The 15 یا 20 دانش آموزان به آرامی جمع آوری, most them still expecting Dennis.

من همیشه شروع کردن کلاس های آموزشی من با معرفی خودم, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", من نوشتن نام من, email and phone number up on the white board in big letters so that everyone can see it clearly. I address the fact that I’m replacing Dennis and I assure them that I am a suitable replacement, غیره. I have everyone briefly tell me their name and what they want to achieve out of the class so that I can tailor things to their specific requirements as I go along. The usual stuff.

We wrap that up and fire up the projector. I go to erase my contact info and … I had written it in permanent marker. I was so embarrassed. In my mind’s eye, آن را شبیه به این نگاه: There is this "Paul Galvin" شخص, last minute replacement for our beloved Dennis. He’s wearing a crumpled up business suit and unshaven. He has just written his name huge letters on our white board in نشانگر دائمی. What a sight!

این همه با خوشحالی به پایان رسید, اما. This was a chemical company, بعد از همه. A grizzled veteran employee pulled something off the shelf and, احتمالا در تخلف از مقررات سازمان حفاظت محیط زیست, cleared the board. I managed to stay 1/2 day ahead of the class throughout the course and they gave me a good review in the end. This cemented my "pinch hitter" reputation at my company. My luggage arrived the first day, بنابراین من روز بسیار بیشتر قابل ارائه بود دو و سه.

همانطور که من در نظر گرفتن چشم قرمز بازگشت به خانه, I was contemplating "lessons learned". There was plenty to contemplate. Communication is key. Tell clients about changes in plan. Don’t ever check your luggage at the airport if you can possibly avoid it. Bring spare "stuff" in case you do check your luggage and it doens’t make it. I think the most important lesson I learned, اما, این بود: همیشه یک مارکر قبل از نوشتن تست در گوشه سمت چپ پایین تر از تخته سفید, با حروف بزرگ, "پل گالوین".

</پایان>

برچسب ها: ,

دیدگاه: شیرپوینت در مقابل. برخورددهنده بزرگ هادرون

پاسخ دهید

Due to some oddball United Airlines flights I took in the mid 90’s, I somehow ended up with an offer to transform "unused miles" into about a dozen free magazine subscriptions. That is how I ended up subscribing to Scientific American magazine.

As software / consulting people, we encounter many difficult business requirements in our career. Most the time, we love meeting those requirements and in fact, it’s probably why we think this career is the best in the world. I occasionally wonder just what in the world would I have done with myself if I had been born at any other time in history. How terrible would it be to miss out on the kinds of work I get to do now, at this time and place in world history? I think: pretty terrible.

Over the years, some of the requirements I’ve faced have been extremely challenging to meet. Complex SharePoint stuff, building web processing frameworks based on non-web-friendly technology, complex BizTalk orchestrations and the like. We can all (hopefully) look proudly back on our career and say, "yeah, that was a hard one to solve, but in the end I pwned that sumbitch!" بهتر است با این حال, even more interesting and fun challenges await.

I personally think that my resume, in this respect, is pretty deep and I’m pretty proud of it (though I know my wife will never understand 1/20th of it). But this week, I was reading an article about the Large Hadron Collider in my Scientific American magazine and had one of those rare humbling moments where I realized that despite my "giant" status in certain circles or how deep I think my well of experience, there are real giants in completely different worlds.

The people on the LHC team have some really thorny issues to manage. Consider the Moon. I don’t really think much about the Moon (though I’ve been very suspicious about it since I learned it’s slowing the Earth’s rotation, which can’t be a good thing for us Humans in the long term). اما, the LHC team does have to worry. LHC’s measuring devices are so sensitive that they are affected by the Moon’s (Earth-rotation-slowing-and-eventually-killing-all-life) gravity. That’s a heck of a requirement to meet — produce correct measurements despite the Moon’s interference.

I was pondering that issue when I read this sentence: "The first level will receive and analyze data from only a subset of all the detector’s components, from which it can pick out promising events based on isolated factors such as whether an energetic muon was spotted flying out at a large angle from the beam axis." Really … ? I don’t play in that kind of sandbox and never will.

Next time I’m out with some friends, I’m going to raise a toast to the good people working on the LHC, hope they don’t successfully weigh the Higgs boson particle and curse the Moon. I suggest you do the same. کاملا نان تست خواهد بود 🙂

</پایان>

برچسب ها:

شیطان مایکروسافت URL

2 پاسخ ها

من انجام یک جستجوی گوگل:

تصویر

من بر روی لینک مشخص شده در بالا را کلیک کنید ("Download details: ویندوز شیرپوینت…").

من این را دریافت کنید:

تصویر

Note the URL.

Looks pretty suspicious to me. I don’t know if I should laugh, خندیدن تماس بگیرید و یا یک کشیش.

</پایان>

برچسب ها:

قالب سریع: سیستم برنامه ریز ظرفیت مرکز برای شیرپوینت

پاسخ دهید

I just fired up the capacity planning tool that’s all the rage these days.

I found it easy to use and quickly modeled a client environment I worked on this past summer.

With some trepidation, I pressed the final OK button and it recommended something that is pretty similar to what we gave our client (we actually threw in a second application server for future excel use). I take that to be a good sign and increases my confidence in the tool.

It seems pretty powerful stuff a much better starting point than a blank page.

I like that lets you get into some good detail about the environment. How many users, how you project they will use the system (publishing, collaboration, غیره), branch office and connectivity / network capacity between them and the mama server. Good stuff.

It asks broad based questions and then lets you tweak the details for a pretty granular model of your environment.

I hesitated downloading it because I have so many other things to look at it, read and try to digest. I’m glad I did.

It’s an easy two-step process. Download system center capacity planner and then download the SharePoint models. It runs nicely on Windows XP.

Based on my quick impression, I don’t see how it might account for:

  • جستجو: Total documents, maybe types of documents, languages.
  • Excel server: how much, if at all?
  • Forms server: how much, if at all?
  • BDC: how much, if at all.

Those may be modeled and I just didn’t see them in the 10 minute review.

I will definitely use it at my next client.

If I were not a consultant and instead working for a real company :), I’d model my current environment and see how the tool’s recommended model matches up against reality. That would be pretty neat. It could lead to some good infrastructure discussion.

</پایان>

راه حل: System.IO.FileNotFoundException در “SPSite = جدید SPSite(آدرس)”

11 پاسخ ها

تکمیلی: من در این سوال در اینجا به MSDN (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

ایجاد یک وب سرویس به عنوان یک BDC-دوستانه نما to a SharePoint list. When I used this from my development environment, مشغول به کار خوب. وقتی که من مهاجرت به یک سرور جدید, من با این خطا مواجه:

System.IO.FileNotFoundException: برنامه وب http://localhost/sandbox می تواند یافت نمی شود. تایید کنید که شما تایپ صحیح URL. اگر URL را باید در خدمت محتوا های موجود, ممکن است مدیر سیستم نیاز به نگاشت URL درخواست جدید برای اضافه کردن به برنامه مورد نظر. در Microsoft.SharePoint.SPSite .. ctor(محموله SPFarm, یوری requestUri, بولی contextSite, SPUserToken userToken) در Microsoft.SharePoint.SPSite .. ctor(عبارات requestUrl) در Conchango.xyzzy.GetExistingDocument(عبارات minId, عبارات maxId, عبارات titleFilter) در C:\اسناد و تنظیمات پل اسناد و مدارک من ویژوال استودیو 2005 پروژه xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:خط 69

در اینجا خط 69:

با استفاده از (سایت SPSite = جدید SPSite("http://localhost/sandbox"))

من سعی کردم تغییرات مختلف بر روی URL, از جمله با استفاده از نام واقعی سرور, آدرس آی پی خود را, کاهش انتهایی بر روی URL, غیره. I always got that error.

من استفاده می شود گوگل to research it. Lots of people face this issue, و یا تغییرات از آن, اما هیچ یک به نظر می رسید که آن را حل.

Tricksy خزه یک خطای دقیق که رخ می دهد نه برای من برای بررسی 12 hive logs. Eventually, در حدود 24 ساعت پس از همکارم توصیه من این کار را, من چک کردن 12 ورود به سیستم کندو و این: 

یک استثنا رخ می داد در حالی که تلاش برای به دست آوردن مزرعه محلی:
System.Security.SecurityException: درخواست دسترسی به رجیستری مجاز نمی باشد.
در System.ThrowHelper.ThrowSecurityException(ExceptionResource منابع) در
(نام رشته, بولی را قابل نوشتن کنید) در
(نام رشته) در
() در
() در
(SPFarm& مزرعه, بولی& isJoined)
منطقه مونتاژ که شکست خورده بود:  MyComputer

این باز کردن راه های جدید پژوهشی, پس از آن دوباره به گوگل. که منجر به این پست انجمن: HTTP://forums.codecharge.com / posts.php?post_id = 67،135. That didn’t really help me but it did start making me think there was a database and/or security issue. I soldiered on and اندرو در کانل post finally triggered the thought that I should make sure that the application pool’s identity account had appropriate access to the database. I thought it already did. اما, همکارم رفت و به برنامه استخر هویت برای دسترسی به حساب به SQL.

به محض این که او ساخته شده است که تغییر, everything started working.

بعد چه اتفاقی افتاد بهتر است به عنوان یک بیان شعر بی قافیه سه سطری ژاپنی شعر:

مشکلات بالا بردن دست خود را.
You swing and miss. Try again.
موفقیت! But how? چرا?

او نمی خواست به ترک تنهایی می خواهم که, ترجیح می دهند به دادن مجوز حداقل (و احتمالا با یک چشم به نوشتن یک وبلاگ; من او را مورد ضرب و شتم به پانچ, muhahahahaha!).

او مجوز های پی در پی از نرم افزار حساب استخر هویت تا حذف … there was no longer any explicit permission for the app pool identity account at all. The web service continued to work just fine.

We went and rebooted the servers. Everything continued to work fine.

پس, برای روکش کردن: we gave the app pool identity full access and then took it away. The web service started working and never stopped working. Bizarre.

اگر کسی می داند چرا که باید کار می کرد, لطفا ترک یک نظر.

</پایان>