Arkivat mujore: Shkurt 2008

E diel Funny: “NUK PËR EKSPORT”

Lini një përgjigje

Mbrapsht rreth 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, lehtë për përdoruesit përfundimtarë, flakërues, Multi-gjuha, etj. 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.

Dhe së fundi, 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.

</fund>

Abonohen në blogun tim!

Technorati Tags: ,

Zgjidhje: SPQuery Does Not Kërko Dosjet

3 Përgjigje

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. Bottom line: assign "recursive" për atribut pamje të query.

Skenari im:

  • Të hënën, Unë ngarkoj një dokument dhe të furnizimit me disa të dhëna të meta.
  • Javën e ardhshme, 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").
  • Ne kemi krijuar një fasadë të shërbimit të internetit që ofron një ndërfaqe QZHB-miqësore në listë në mënyrë që përdoruesit mund të lehtë të gjetur atë dokument e hëna nëpërmjet një kërkim të titullit.
  • A BDC data column provides a friendly user interface. (Kjo është pjesë e përpjekjes sime në përdorimin e QZHB për një kolonë Lookup më miqësore).

Përfundimtar QZHB Fasada shërbim përdor një pyetje si kjo për të bërë lookup:

 // U2U mjet i përdorur për të ndihmuar në gjenerimin këtë query CAML.
      oQuery.Query =
        "<Ku>";

      nëse (titleFilter.Length > 0)
        oQuery.Query   =
          "  <Dhe>";

      oQuery.Query   =
        "    <Dhe>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + MinID + "</Vlerë>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</Vlerë>" +
        "      </Leq>" +
        "    </Dhe>";

      nëse (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Përmban>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Vlerë>" +
          "    </Përmban>" +
          "  </Dhe>";
      oQuery.Query   =
        "</Ku>";

Gjatë fazës fillestare të zhvillimit, this worked great. Megjithatë, ne kemi prezantuar dosjet në directory për të zgjidhur disa probleme dhe papritmas, 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, ne kemi krijuar një dosje të bazuar në ID e list item-së dhe pastaj të lëvizë skedarin atje (Kam shkruar në lidhje me atë këtu; ne kemi pasur rezultate të përziera me këtë qasje, por në tërësi, ajo është duke punuar mirë). 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 = i ri SPQuery();

Unë në vend të përdorur një konstruktor që specifikuar një pamje:

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

SPQuery oQuery = i ri SPQuery(oList.Views["All Documents"]);

Kjo zgjidhur problemin dhe kam filluar për të marrë rezultatet e mia.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, aq sa unë mund të them, nuk punojnë me pamje të njëjtën mënyrë si një GEQ thjeshtë / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", si në:

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

That solved the problem for CONTAINS. Në të vërtetë, kjo zgjidhur edhe problemin e mia Kërko origjinal dhe në qoftë se unë kam specifikuar atribut rekursive për herë të parë, Unë nuk do të kandidojë në çështjen përsëri.

Fakti që një pikëpamje e bazuar SPQuery punon për disa operatorëve (GEQ/LEQ) dhe jo të tjerët (PËRMBAN), shoqëruar me faktin se KPIs nuk duket për të punuar në të gjitha me dosje që përmbajnë bibliotekat dokument shpie mua të besoj se ka disa çështje SPQuery orthogonality.

Falënderime të veçanta:

</fund>

Abonohen në blogun tim!

MOSS bug KPI? Treguesi Lista Lidhur me Bibliotekën dokument me Folders

1 Përgjigje

UPDATE 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 përshkruar se në pak më tepër hollësira këtu.

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 (duke përdorur një teknikë të ngjashme me atë që kam shkruar në lidhje këtu). 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" por në vend të kësaj të krijojnë docs në nivel lokal dhe pastaj ngarkoni atyre).

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

Kjo zakonisht është e thjeshtë për të bërë dhe kam përshkruar diçka shumë si kjo në Beagle SharePoint me shumë të shtëna ekran, nëse ju jeni të interesuar.

Me pak fjalë, Unë e bëri në vijim:

  • Create a view on the doc library called "Pending".
  • Konfiguro pikëpamjen për të injorojë strukturës dosje.
  • Krijo një listë KPI.
  • Create an indicator in the list that points to the doc lib and that "Pending" pamje.

This simply does not work. The KPI shows my target (e.g. pesë dokumente urgjente) but always shows the actual number of urgent documents as zero. Paradoxically, në qoftë se ju stërvitje poshtë për detaje, it shows the five urgent documents in the list. I created a very simple scenario with two documents, one in a folder and one not. Here is the screen shot:

imazh

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

Kjo duket për mua se edhe pse ju specifikoni një pamje të, the KPI doesn’t honor the "show all items without folders" vendosjen dhe në vend të, kufizohet në dosjen rrënjë.

Nëse unë jam gabim, ju lutem të më bjerë një linjë apo të lënë një koment.

</fund>

Abonohen në blogun tim!

Technorati Tags:

SPD Workflow “Të mbledhë të dhëna nga një përdorues”: Modifikojë formën gjeneruar Task

4 Përgjigje

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" veprim në mënyrë që ne mund të shpejtë përdorues për copa të ndryshme të informacionit, të tilla si nëse ata miratojnë atë që, disa komente dhe ndoshta pyesin se çfarë ata kishin për darkë natën tjetër.

The forms are perfectly functional. They are tied to a task list as a content type. They are 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Megjithatë, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, ne kemi nevojë të përdorë për truket të ndryshme për të marrë rreth tij (për shembull, vendosjen prioritet në një detyrë).

Unë e nevojshme për të siguruar një lidhje në këto forma task që hapën Shiko Pronat (dispform.asxp) of the "related item" in a new window. This provides one-click access to the meta data of the related item. This is what I mean:

imazh

Fatmirësisht, we can do that and it’s not very hard. Broadly speaking, zjarr deri 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, kërko ose skenarë të tjerë XSL, this will be easy for you. Në të vërtetë, Kam gjetur atë të jetë përgjithësisht e lehtë që gjeneruar forma është disi më e lehtë për të ndjekur, në krahasim me pjesën bërthamë Search Results web (ose CWQP ankthi).

Sigurisht, 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" hap.

Provë 1:

  • Modifikojë file aspx me dorë.
  • Provuar atë (të verifikojë se ndryshimet tuaja janë ruajtur siç duhet dhe nuk e thyejnë asgjë).
  • Hapur deri rrjedhën e punës dhe të shtoni një veprim të palidhur (such as "log to history").
  • Ruaj punës.

Pasojë: Në këtë rast, SPD nuk ri-krijoni forma.

Provë 2:

  • A njëjtë si #1 except directly modify the "collect data from a user" veprim.

Pasojë: Ky ri-krijon formën nga zeroja, mbi-shkrim ndryshimet tuaja.

Shënime përfundimtare:

  • Së paku dy veprime SPD krijojnë forma si kjo: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ Formularët mund të modifikohen me dorë.
  • Unë kam qenë në gjendje të gjenerojnë lidhjen time për shkak dispform.aspx, në këtë rast, the relate item always has its ID embedded in the related item’s URL. I was able to extract it and then build an <a href> 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, kështu që unë nuk e di nëse merr në anën tjetër të humnerë.
  • Unë nuk e kam hetuar, por unë nuk do të jetë i habitur në qoftë se nuk është një lloj i file template në 12 hive që unë mund të modifikoj të ndikojë se sa SPD gjeneron format e parazgjedhura (ashtu si ne mund të modifikoj templates vigjilent).

</fund>

Abonohen në blogun tim!

Technorati Tags: ,

Jeni “Error Unknown” Mesazhet vërtetë më mirë se një stack trace?

3 Përgjigje

Unë u lexuar postin Madhur blog se si të mundësojë rafte tregon gjurmë dhe tani unë jam i pyesin: pse ne nuk tregojnë gjithmonë një gjurmë rafte?

Kush doli me këtë rregull dhe pse ne ndjekim atë?

End users will know something is wrong in either case. At least with a stack trace, ata mund të shtypni kontroll-Printscreen, copy/paste into an email and send it to IT. That would clearly reduce the time and effort required to solve the issue.

</fund>

Technorati Tags:

E diel (I ngatërruar) Qesharak: “Emri im është Paul Galvin”

1 Përgjigje

Një bandë e vjet më parë, 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. Në kohën, ajo është projektuar për të kandiduar në tubat e gjelbër (e.g. Wyse 50 terminal) connected to a Unix box via telnet.

My default answer to any question that starts with "Can you … " is "Yes" and that’s where all the trouble started.

The client was a chemical company out in southern California and had just about wrapped up a major ERP implementation based on QAD’s 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. Megjithatë, I had conducted a number of other training classes and was quick on my feet, so I was not too worried. Dennis, the real full-time Results instructor, 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?

To complicate things logistically, 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, go to Chicago, meet for an hour with prospect and then continue on to California.

Mirë, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Kështu, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, I find out that the client is learning less than 24 hours before my arrival that "Paul Galvin" is teaching the class, 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 "jap lajme të këqija në fillim" philosophy. Awesome.

I arrive at the airport and for some incredibly stupid reason, I had checked my luggage. I made it to LAX but my luggage did not. Për mua, losing luggage is a lot like going through the seven stages of grief. Eventually I make it to the hotel, with no luggage, tired, hungry and wearing my (by now, very crumpled) business suit. It takes a long time to travel from Newark — to O’Hare — to a client — back to O’Hare — and finally to LAX.

I finally find myself sitting in the hotel room, munching on a snickers bar, 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.

I woke up the next day, 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, in person she was nice, 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 ose 20 students slowly assemble, most them still expecting Dennis.

I always start off my training classes by introducing myself, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", I write my name, 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, etj. 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, it looked like this: There is this "Paul Galvin" person, 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 permanent marker. What a sight!

It all ended happily, megjithatë. This was a chemical company, në fund të fundit. A grizzled veteran employee pulled something off the shelf and, probably in violation of EPA regulations, 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, so I was much more presentable days two and three.

As I was taking the red eye back home, 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, megjithatë, was this: always test a marker in the lower left-hand corner of a white board before writing, in huge letters, "Paul Galvin".

</fund>

Technorati Tags: ,

Perspektivat: SharePoint vs. Large Hadron Collider

Lini një përgjigje

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.

Si software / njerëz të konsulencës, 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!" Better yet, 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). Por, 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. It will be quite the toast 🙂

</fund>

Technorati Tags:

Përshtypje të shpejtë: Qendra e Sistemit Kapaciteti Planifikues për SharePoint

Lini një përgjigje

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

Kam gjetur të lehtë për t'u përdorur dhe modeluar shpejt një ambient të klientit Unë kam punuar në këtë verë kaluar.

Me disa ankth, I shtypur butonin OK përfundimtar dhe ajo rekomandohet diçka që është shumë e ngjashme me atë që ne kemi dhënë klientit tonë (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, etj), 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:

  • Kërko: Total documents, maybe types of documents, languages.
  • Excel server: how much, if at all?
  • Forms server: how much, if at all?
  • QZHB: 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.

</fund>

Technorati Tags:

Zgjidhje: System.IO.FileNotFoundException në “SPSite = new SPSite(url)”

11 Përgjigje

UPDATE: I postuar këtë pyetje për MSDN këtu (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

Unë të krijova një shërbim web për të vepruar si një QZHB-miqësore fasada to a SharePoint list. When I used this from my development environment, ai ka punuar mirë. Kur kam emigruar këtë në një server të ri, Kam hasur këtë gabim:

System.IO.FileNotFoundException: Web aplikacion në http://localhost/sandbox nuk mund të gjendet. Verifikoni se keni shtypur URL saktë. Nëse URL duhet të shërbejnë përmbajtjen e ekzistuese, administratori i sistemit mund të kenë nevojë të shtoni një të re URL hartë kërkesë të aplikimit të destinuara. në Microsoft.SharePoint.SPSite .. ctor(SPFarm fermë, Uri requestUri, Boolean contextSite, SPUserToken userToken) në Microsoft.SharePoint.SPSite .. ctor(String requestUrl) në Conchango.xyzzy.GetExistingDocument(String minId, String maxId, String titleFilter) në C:\Dokumente dhe Settings Paul My Documents Visual Studio 2005 Projects xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:linjë 69

Këtu është linjë 69:

përdorim (Faqe SPSite = new SPSite("http://localhost/sandbox"))

Unë u përpoq variacione të ndryshme në URL, duke përfshirë përdorimin e emrin e vërtetë e serverit, IP adresa e saj, zvarritës ul mbi URL, etj. I always got that error.

I përdorur Google to research it. Lots of people face this issue, ose variacione të saj, por askush nuk duket se e kanë atë zgjidhur.

Kapriçioz MOSS siguruar një gabim të tillë të detajuar se kjo nuk ka ndodhur për mua për të kontrolluar 12 hive logs. Eventually, për 24 orë pas Kolegu im rekomandoi të bëj kështu, I kontrolluar nga 12 log zgjua dhe e gjeti këtë: 

Një përjashtim ndodhi ndërsa duke u përpjekur për të blerë fermë lokale:
System.Security.SecurityException: Qasje kërkuar regjistrit nuk është e lejuar.
në System.ThrowHelper.ThrowSecurityException(ExceptionResource burimeve) në
(Emri String, Shkruajtshme Boolean) në
(Emri String) në
() në
() në
(SPFarm& fermë, Boolean& isJoined)
Zona e kishës që ishte e dështuar:  MyComputer

Kjo hapi shtigje të reja të hulumtimit, kështu që ishte kthyer në Google. Kjo çoi mua në këtë Post Forum: http://forums.codecharge.com / posts.php?post_id = 67135. 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 Andrew Connell 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. Megjithatë, Kolegu im shkoi dhe i dha pishinë app identitetit qasje të plotë të llogarisë në SQL.

Sapo ajo e bëri këtë ndryshim, everything started working.

Çfarë ndodhi më tej është shprehur më së miri si një haiku poemë:

Problemet ngrenë duart e tyre.
You swing and miss. Try again.
Sukses! But how? Përse?

Ajo nuk duan të lënë gjërat vetëm si kjo, preferuar të japë leje minimal të kërkuar (dhe ndoshta me një sy në shkrim një blog entry; I rrihte me grusht, muhahahahaha!).

Ajo hequr lejet e njëpasnjëshme nga llogaria pishinë app identitetit deri … 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.

Kështu, për radhitje: we gave the app pool identity full access and then took it away. The web service started working and never stopped working. Bizarre.

Nëse dikush e di se pse duhet të ketë punuar, ju lutemi të lënë një koment.

</fund>

Technorati Tags: