Arkivji ta 'Kull Xahar: Frar 2008

IL-ĦADD Funny: “MHUX GĦALL-ESPORTAZZJONI”

Ħalli Risposta

Lura madwar 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, faċli għall-utenti finali, flashy, multi-lingwa, eċċ. 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.

U finalment, 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.

Eventwalment, 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, jekk xejn, 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.

</aħħar>

Abbona għall-blog tiegħi!

Soluzzjoni: SPQuery Does Mhux Fittex folders

3 tweġibiet

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" għall-attribut dawl tal-mistoqsija.

Xenarju tiegħi:

  • Nhar it-Tnejn, I ittella 'dokument u jissupplixxi xi metadata.
  • Il-ġimgħa li ġejja, 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").
  • Imxejna ħolqot faċċata servizz web li jipprovdi interface BDC-friendly mal-lista sabiex l-utenti jistgħu faċilment jillokalizza dak id-dokument it-Tnejn permezz ta 'tfittxija titolu.
  • A BDC data column provides a friendly user interface. (Din hija parti mill tentattiv tiegħi fl-użu BDC għal kolonna Lookup aktar faċli).

Il-finali BDC servizz façade juża mistoqsija bħal din tagħmel l-Lookup:

 // Użati għodda U2U biex jgħinu fil-ġenerazzjoni din il-mistoqsija CAML.
      oQuery.Query =
        "<Fejn>";

      jekk (titleFilter.Length > 0)
        oQuery.Query   =
          "  <U>";

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

      jekk (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Fih>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Valur>" +
          "    </Fih>" +
          "  </U>";
      oQuery.Query   =
        "</Fejn>";

Matul l-istadju inizjali ta 'żvilupp, this worked great. Madankollu, aħna introduċiet folders fil-direttorju biex isolvu xi problemi u f'daqqa waħda, 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, aħna toħloq folder bbażata fuq ID-oġġett lista u mbagħad jimxu l-fajl hemmhekk (I kiteb dwar dan hawn; aħna kellna riżultati mħallta ma dan l-approċċ, iżda fuq kollox, huwa xogħol tajjeb). 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 = ġdid SPQuery();

I minflok jintuża kostruttur dik speċifikata ħsieb:

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

SPQuery oQuery = ġdid SPQuery(oList.Views["All Documents"]);

Li tissolva l-problema u I bdiet tikseb riżultati tiegħi.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, safejn peux, ma taħdem ma 'l-opinjoni l-istess mod bħall-a GEQ sempliċi / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", kif fil-:

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

That solved the problem for CONTAINS. Fil-fatt, dan solvuti wkoll problema tiegħi tfittxija oriġinali u jekk kelli speċifikat l-attribut jirrikorri l-ewwel darba, I ma kien ikun imur lejn il-kwistjoni mill-ġdid.

Il-fatt li SPQuery bbażata view xogħlijiet għal ċerti operaturi (GEQ/LEQ) u mhux oħrajn (FIH), flimkien mal-fatt li KPIs ma jidhirx li jaħdmu fil-livelli kollha mal-libreriji li fihom folder dokument twassalni biex jemmnu li SPQuery għandha xi kwistjonijiet orthogonality.

Grazzi speċjali:

</aħħar>

Abbona għall-blog tiegħi!

MOSS KPI bug? Indikatur Lista Marbuta biex Dokument Librerija Bil folders

1 Irrispondi

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

This is usually simple to do and I described something very much like this at the SharePoint Beagle with lots of screen shots if you’re interested.

In a nutshell, Jien għamilt dan li ġej:

  • Create a view on the doc library called "Pending".
  • Configure the view to ignore folder structure.
  • Create a KPI List.
  • Create an indicator in the list that points to the doc lib and that "Pending" ħsieb.

This simply does not work. The KPI shows my target (e.g. five urgent documents) but always shows the actual number of urgent documents as zero. Paradoxically, if you drill down to the details, 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:

immaġni

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.

</aħħar>

Abbona għall-blog tiegħi!

Tags:

SPD Workflow “Iġbor data minn Utent”: Tibdel il-Formola Task Ġġenerata

4 tweġibiet

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" azzjoni sabiex inkunu nistgħu pront lill-utent għall-bits differenti ta 'informazzjoni, bħal jekk japprovah, xi kummenti u forsi jistaqsu dak li kellhom għall-pranzu oħra bil-lejl.

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. Madankollu, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, għandna bżonn li tirrikorri għal tricks varji biex tikseb madwar dan (per eżempju, iffissar tal-prijoritajiet fuq kompitu).

I meħtieġa biex tipprovdi link fuq dawn il-formoli task li fetħet il-proprjetajiet view (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:

immaġni

Thankfully, we can do that and it’s not very hard. Broadly speaking, fire up 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, tfittxija jew xenarji XSL oħra, this will be easy for you. Fil-fatt, Sibt li huwa li huma ġeneralment aktar faċli peress li l-forma iġġenerat huwa kemmxejn aktar faċli biex isegwu meta mqabbel ma 'qalba riżultati web part tfittxija (jew il- CWQP nightmarish).

Of course, 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" pass.

Test 1:

  • Tibdel il-fajl ASPX bl-idejn.
  • Tittestja (tivverifika li l-bidliet tiegħek kienu salvati sew u ma kisritx xejn).
  • Jiftħu l-fluss tax-xogħol u żid azzjoni relatati (such as "log to history").
  • Salv l-fluss tax-xogħol.

Riżultat: F'dan il-każ, SPD ma jerġgħu joħolqu l-forma.

Test 2:

  • Jagħmlu l-istess bħal #1 except directly modify the "collect data from a user" azzjoni.

Riżultat: Dan jerġa 'joħloq il-formola mill-bidu, over-miktub tibdil tiegħek.

Noti finali:

  • Mill-inqas żewġ azzjonijiet tad-DPW joħolqu forom bħal dan: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ formoli jistgħu jiġu modifikati manwalment.
  • I kien kapaċi li tiġġenera link tiegħi biex dispform.aspx minħabba, f'dan il-każ, 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, so I do not know jekk jiġrilha l-naħa l-oħra tal-chasm.
  • I ma investigatx, iżda I ma tkunx sorpriż jekk ikun hemm xi tip ta 'fajl template fil- 12 doqqajs li I jista 'jbiddel għal jaffettwa kemm SPD jiġġenera l-forom default (ferm simili nistgħu timmodifika templates twissija).

</aħħar>

Abbona għall-blog tiegħi!

Huma “Error Mhux magħruf” Messaġġi Really Aħjar Than a Trace Stack?

3 tweġibiet

I kien qari blog post Madhur dwar kif għandhom jippermettu munzell traċċi displays u issa jien mintix: għaliex ma aħna dejjem juru traċċa munzell?

Min ħarāet bil din ir-regola u għaliex aħna isegwu dan?

End users will know something is wrong in either case. At least with a stack trace, dawn tista 'tagħfas il-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.

</aħħar>

Tags:

Il-Ħadd (Embarrassing) Funny: “Jisimni Paul Galvin”

1 Irrispondi

A mazz ta 'snin ilu, 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. Fil-ħin, li kienet iddisinjata biex jimxu fuq tubi ħodor (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. Madankollu, 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.

Well, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Allura, 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 "jagħtu aħbar ħażina kmieni" 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. Għalija, 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 jew 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, eċċ. 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, madankollu. This was a chemical company, wara kollox. 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, madankollu, was this: always test a marker in the lower left-hand corner of a white board before writing, in huge letters, "Paul Galvin".

</aħħar>

Perspettivi: SharePoint vs. l Hadron Collider

Ħalli Risposta

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.

Bħala softwer / konsulenza nies, we encounter many difficult business requirements in our career. Most the time, aħna imħabba jissodisfaw dawk ir-rekwiżiti u fil-fatt, 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, f'dan il-ħin u l-post fl-istorja dinjija? I think: pretty terrible.

Matul is-snin, some of the requirements I’ve faced have been extremely challenging to meet. Complex SharePoint stuff, oqfsa ipproċessar web bini bbażati fuq teknoloġija mhux web-friendly, complex BizTalk orchestrations and the like. We can all (nisperaw) ħarsa kburi lura fuq karriera tagħna u jgħidu, "yeah, li kienet waħda diffiċli biex isolvu, imma fl-aħħar I pwned li sumbitch!" Aħjar għadhom, isfidi saħansitra aktar interessanti u divertenti tistenna.

Personalment naħseb li jerġa tiegħi, f'dan ir-rigward, hija pjuttost fil-fond u jien pretty kburin minnha (jekk naf mara tiegħi qatt se jifhmu 1/20th ta 'dan). But this week, I kien qari artikolu dwar il- Large Hadron Collider in my Scientific American magazine and had one of those rare humbling moments where I realized that despite my "giant" status f'ċerti ċrieki jew kif deep naħseb ukoll tiegħi ta 'esperjenza, 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). Iżda, 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 🙂

</aħħar>

Impressjoni Quick: Sistema Center Planner kapaċità għall SharePoint

Ħalli Risposta

I biss fired up l-ippjanar għodda kapaċità li l- l-Rage dawn il-jiem.

I sabuha faċli biex tużah u malajr mmudellati f'ambjent klijent I ħadmu fuq dan is-sajf passat.

B'xi trepidation, I ippressat-buttuna OK finali u rrakkomanda xi ħaġa li hija pjuttost simili għal dak li aħna taw klijent tagħna (aħna fil-fatt threw fil-server tieni applikazzjoni għal użu fil-futur jisbqu). I take that to be a good sign and increases my confidence in the tool.

Jidher Jittieħed pretty qawwija punt ta 'tluq ferm aħjar minn paġna vojta.

I like that lets you get into some good detail about the environment. How many users, kif inti proġett se jużaw is-sistema (pubblikazzjoni, kollaborazzjoni, eċċ), fergħa u l-konnettività / network capacity between them and the mama server. Good stuff.

Hija tistaqsi mistoqsijiet ġenerali li bbażati u mbagħad ihallik tweak-dettalji għal mudell pretty granulari ta 'l-ambjent tiegħek.

I eżita tniżżil għaliex għandi ħafna affarijiet oħra biex tħares lejn din, 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.

Ibbażat fuq impressjoni malajr tiegħi, Ma narax kif jista jammontaw għal:

  • Fittex: Dokumenti Total, forsi tipi ta 'dokumenti, lingwi.
  • Excel server: kemm, jekk xejn?
  • Formoli server: kemm, jekk xejn?
  • BDC: kemm, jekk xejn.

Dawn jistgħu jkunu mudellati u I biss ma tara minnhom fil- 10 reviżjoni minuta.

I definittivament se tużah fil-klijent tiegħi li jmiss.

Jekk I ma kinux konsulent u minflok qed jaħdem għal kumpanija reali :), 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.

</aħħar>

Soluzzjoni: System.IO.FileNotFoundException fuq “SPSite = ġdid SPSite(url)”

11 tweġibiet

UPDATE: I stazzjonati din il-kwistjoni MSDN hawn (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

I ħolqot servizz web biex jaġixxi bħala Faċċata BDC-friendly to a SharePoint list. When I used this from my development environment, maħduma multa. Meta I emigraw din lil server ġdida, I jiltaqgħu dan l-iżball:

System.IO.FileNotFoundException: L-applikazzjoni Web fil http://localhost/sandbox ma jistax jinstab. Jivverifikaw li inti għandek ittajpjat-URL b'mod korrett. Jekk il-URL għandhom jservu kontenut eżistenti, l-amministratur tas-sistema jista 'jkollhom bżonn li żżid mapping ġdida URL talba għall-applikazzjoni intenzjonata. fil Microsoft.SharePoint.SPSite .. ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken) fil Microsoft.SharePoint.SPSite .. ctor(String requestUrl) fil Conchango.xyzzy.GetExistingDocument(String minId, String maxId, String filtru titolu) fis-C:\Dokumenti u Settings Dokumenti Tiegħi Pawl Visual Studio 2005 Proġetti xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:linja 69

Hawnhekk huwa linja 69:

użu (Sit SPSite = ġdid SPSite("http://localhost/sandbox"))

I ppruvaw varjazzjonijiet differenti fuq l-URL, inkluż l-użu reali isem tal-server, indirizz IP tiegħu, slashes tkaxkir fuq l-URL, eċċ. I always got that error.

I użati Il-Google to research it. Lots of people face this issue, jew varjazzjonijiet ta 'dan, imma ebda wieħed deher li huwa solvuti.

Tricksy MOSS sakemm tali żball dettaljata li dan ma sarx lili biex jiċċekkja l- 12 hive logs. Eventwalment, dwar 24 siegħa wara kollega tiegħi rakkomandat I jagħmlu dan, I ċċekkjati l- 12 log doqqajs u sabet dan: 

Eċċezzjoni ġara waqt li jipprova li jiksbu l-irziezet lokali:
System.Security.SecurityException: Aċċess reġistru Mitlub ma jkunx permess.
fil System.ThrowHelper.ThrowSecurityException(ExceptionResource riżorsi) fi
(Isem String, Writable Boolean) fi
(Isem String) fi
() fi
() fi
(SPFarm& farm, Boolean& isJoined)
Il-Żona ta 'l-assemblea li naqas kien:  MyComputer

Dan fetħet toroq ġodda ta 'riċerka, allura kien lura lill-Google. Li wasslitni sabiex dan forum post: 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 Andrew Connell tal 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. Madankollu, kollega tiegħi marru u taw l-app pool identità kont aċċess sħiħ għall SQL.

Hekk kif hi magħmula li l-bidla, everything started working.

Dak li ġara jmiss huwa l-aħjar espressa bħala haiku poeżija:

Problemi jgħollu idejhom.
You swing and miss. Try again.
Success! But how? Għaliex?

Hi ma riditx li jħallu l-affarijiet waħdu bħal dik, pprefera li tagħti l-permess minimu meħtieġ (u probabbilment b'attenzjoni għall-kitba ta 'dħul blog; I taħbit tagħha lill-punch, muhahahahaha!).

Hija ħassret permessi suċċessivi mill-pool kont identità app sakemm … 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.

Allura, biex terġa: we gave the app pool identity full access and then took it away. The web service started working and never stopped working. Bizarre.

Jekk xi ħadd jaf għaliex li għandhom ħadmu, jekk jogħġbok leave kumment.

</aħħar>