Nyaraka za kila mwezi: Februari 2008

Jumapili Mapenzi: “SIYO YA USAFIRISHAJI”

Acha reply

Nyuma kote 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, rahisi kwa watumiaji wa mwisho, flashy, lugha mbalimbali, nk. Sad to say, Mimi pengine si alikuwa kama seti kabambe ya kazi ya kukamilisha tangu siku hizo heady.

This effort pre-dated Microsoft.NET. Plain vanilla ASP was still somewhat new (au uchache sana usio wa kawaida na kampuni yangu). "Brick and mortar" companies were doomed. Wamepotea! This is to say that it was pioneering work. Si Hadron Collider pioneering kazi, lakini kwa ajili yetu katika dunia yetu kidogo, ilikuwa ni pioneering kazi.

We were crazy busy. We were doing mini POC’s almost every day, kuhesabia nje ya jinsi ya kudumisha hali katika kati asili wasiokuwa na utaifa, kuhesabia masuala ya lugha mbalimbali, row-level security. We even had create a vocabulary to define basic terms (Mimi kuliko hali ya kuendelea lakini kwa sababu fulani, the awkward "statefull" alishinda siku).

Tulipokuwa madly mzushi bidhaa hii, 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, kwa sababu sisi daima ililenga Kihispania au Kifaransa, lakini katika kesi hii, ilikuwa ni ya Kichina (ambayo ni mara mbili-Byte kuweka tabia na required maalum utunzaji aliyopewa teknolojia sisi kutumika).

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:

  • Kaskazini: "Could you tell me how to get to [XX] ya mitaani?"
  • Kichina: "Sorry, we don’t speak English".
  • Kaskazini: "Oh, vizuri mimi kuzungumza Mandarin." na yeye akawauliza tena katika Kichina, lakini wazi zaidi (kama bora alivyoweza).
  • Kichina: Sana 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] mitaani."

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" katika hisia ya kuishinikiza yangu ndani ya maamuzi ya mbaya biashara.
  • Sisi walikuwa hawaruhusiwi kuendesha magari ya (kulikuwa na baadhi ya machafuko ya kama hii ilikuwa desturi, matakwa ya kisheria au tu utawala mteja).
  • Kulikuwa maalum sheria kwa ajili ya kwenda kwa desturi.
  • Sisi walikuwa hawaruhusiwi kutumia fedha Marekani kwa ajili ya kitu.
  • You’re not supposed to leave tips. It’s insulting if you do.

Na hatimaye, Mimi nilikuwa na kiasi safi kumbukumbu Tiananmen mauaji. When I was at college, I remember seeing real-time Usenet postings as the world looked on in horror.

Kwa kifupi, 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.

Mimi nina juu ya hii 14 saa moja ndege na ingawa ilikuwa darasa biashara, 14 masaa ni damned kwa muda mrefu wakati. Kuna tu hivyo njia nyingi za kuwakaribisha mwenyewe kwa kusoma, watching movies or playing with the magnetized cutlery. Even a really good book is hard to read for several hours straight.

Hatimaye, Mimi ilianza ya kusoma nyenzo ufungaji juu ya kipande cha programu mimi mara mkono-amebeba pamoja nami kwa mteja, Netscape’s web server. I’m reading the hardware/software requirements, blurbs masoko, kuangalia picha pretty na ghafla, I zero in on the giant "NOT FOR EXPORT" onyo, kitu kuhusu 128 bit encryption. I stuffed the box back into my carry bag, onyo uso-chini (kama kama kwamba ingekuwa ulisaidia) na alijaribu kuweka maono ya Usiku wa manane Express out of my head.

Kuangalia nyuma juu yake sasa, Ningeli kuwa na wasiwasi, kama wakati wote, wakati mimi kushoto Marekani, si wakati mimi kuingia China 🙂 Hakuna kiovu kilichotokea na mimi bado kufikiria kwamba kuwa bora na ya kukumbukwa safari ya biashara Nimekuwa na furaha ya kufanya.

</mwisho>

Kujiunga na blog yangu!

Tags technorati: ,

Ufumbuzi: SPQuery Je Si Tafuta Folders

3 majibu

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" kwa sifa mtazamo wa swala.

Yangu mazingira:

  • Jumatatu, Mimi upload hati na ugavi baadhi ya data meta.
  • Wiki iliyofuata, 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").
  • Tumeunda huduma ya mtandao façade ambayo hutoa interface BDC-kirafiki na orodha hivyo kwamba watumiaji urahisi Machapisho kwamba hati Jumatatu kupitia tafuta cheo.
  • A BDC data column provides a friendly user interface. (Hii ni sehemu ya jaribio yangu katika kutumia BDC kwa safu zaidi ya kirafiki Lookup).

mwisho BDC façade huduma anatumia swala kama hii kufanya lookup:

 // Kutumika U2U chombo ili kusaidia katika kuzalisha hii hoja CAML.
      oQuery.Query =
        "<Ambapo>";

      kama (titleFilter.Length > 0)
        oQuery.Query   =
          "  <Na>";

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

      kama (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Ina>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Thamani>" +
          "    </Ina>" +
          "  </Na>";
      oQuery.Query   =
        "</Ambapo>";

Wakati wa hatua ya awali ya maendeleo, this worked great. Hata hivyo, sisi ilianzisha folders katika saraka ya kutatua baadhi ya matatizo na ghafla, 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, sisi kujenga folder msingi ID bidhaa orodha na kisha kuondoka faili huko (Niliandika kuhusu kwamba hapa; tulikuwa na mchanganyiko matokeo na mfumo huu lakini kwa ujumla, ni kazi vizuri). 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 = mpya SPQuery();

Mimi badala kutumika kuujenga kwamba maalum mtazamo:

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

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

Kwamba kutatuliwa tatizo na mimi kuanza kupata matokeo yangu.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, hivyo mbali kama naweza kuwaambia, haifanyi kazi kwa lengo njia ile ile kama GEQ rahisi / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", kama katika:

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

That solved the problem for CONTAINS. Kwa kweli, hii pia kutatuliwa tafuta yangu ya awali tatizo na kama alikuwa maalum sifa kujirudia mara ya kwanza, Mimi bila kuwa na kukimbia katika suala tena.

ukweli kwamba SPQuery maoni makao kazi kwa waendeshaji baadhi (GEQ/LEQ) na si watu wengine (Ina), pamoja na ukweli kwamba KPIs hawaonekani kazi wakati wote na maktaba hati folder zenye inaongoza mimi kuamini kwamba SPQuery ina baadhi ya masuala orthogonality.

Shukrani maalum:

</mwisho>

Kujiunga na blog yangu!

MOSS KPI mdudu? Orodha Kiashiria Amefungwa kwa Maktaba Kudhibiti Kwa Folders

1 Kujibu

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. Mimi alielezea kwamba katika undani zaidi kidogo hapa.

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 (kutumia mbinu sawa na kile aliandika kuhusu hapa). 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" lakini badala yake kuunda maandiko ndani ya nchi na kisha kuzipeleka).

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

Hii ni kawaida rahisi kufanya na mimi ilivyoelezwa kitu sana kama hii ifikapo Beagle SharePoint kwa kura ya screen shots kama wewe ni nia ya.

Kwa kifupi, Nilifanya zifuatazo:

  • Create a view on the doc library called "Pending".
  • Configure maoni kupuuza folder muundo.
  • Kujenga Orodha KPI.
  • Create an indicator in the list that points to the doc lib and that "Pending" mtazamo.

This simply does not work. The KPI shows my target (e.g. tano ya haraka nyaraka) but always shows the actual number of urgent documents as zero. Paradoxically, kama wewe kuchimba chini kwa maelezo, 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:

picha

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

Inaonekana kwangu kwamba hata kama wewe bayana mtazamo, the KPI doesn’t honor the "show all items without folders" kuweka na badala yake, mipaka yenyewe ya folder mzizi.

Kama mimi nina makosa, tafadhali tone mimi line au kuacha maoni.

</mwisho>

Kujiunga na blog yangu!

Tags technorati:

SPD Workflow “Kukusanya Data Kutoka mtumiaji”: Kurekebisha yanayotokana Task Fomu

4 majibu

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" hatua ili tuweze kuchochea mtumiaji kwa bits tofauti ya habari, kama vile kama wao kupitisha, some comments and maybe ask what they had for dinner the other night.

The forms are perfectly functional. They are tied to a task list as a content type. Wao ni 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Hata hivyo, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, we need to resort to various tricks to get around it (kwa mfano, setting priority on a task).

I needed to provide a link on these task forms that opened up the view properties (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:

picha

Nashiriki, 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, search or other XSL scenarios, this will be easy for you. Kwa kweli, Nimeona ni kuwa kwa ujumla rahisi tangu fomu yanayotokana fulani ni rahisi kufuata ikilinganishwa na sehemu tafuta matokeo mtandao msingi (au nightmarish CWQP).

Bila shaka, 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" hatua.

Mtihani 1:

  • Kurekebisha faili ASPX kwa mkono.
  • Mtihani ni (kuhakikisha kwamba mabadiliko yako walikuwa vizuri kuokolewa na hakuwa na kuvunja kitu).
  • Kufungua workflow na kuongeza hatua lisilohusiana (such as "log to history").
  • Ila workflow.

Kusababisha: Katika kesi hiyo, SPD did not re-create the form.

Mtihani 2:

  • Do the same as #1 except directly modify the "collect data from a user" hatua.

Kusababisha: This re-creates the form from scratch, over-writing your changes.

Final Notes:

  • At least two SPD actions create forms like this: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ forms can be manually modified.
  • I was able to generate my link to dispform.aspx because, katika kesi hii, the relate item always has its ID embedded in the related item’s URL. I was able to extract it and then build an <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 don’t know if gets to the other side of the chasm.
  • I didn’t investigate, but I would not be surprised if there is some kind of template file in the 12 hive that I could modify to affect how SPD generates the default forms (much like we can modify alert templates).

</mwisho>

Kujiunga na blog yangu!

Tags technorati: ,

Ni “Haijulikani Hitilafu” Ujumbe Kweli Bora Kuliko Trace Stack?

3 majibu

Nilikuwa kusoma blog Madhur za baada ya jinsi ya kuwawezesha stack maonyesho kuwaeleza na sasa mimi nina anashangaa: kwa nini sio sisi daima kuonyesha mpororo?

Ambaye alikuja na utawala kwamba na kwa nini sisi kufuata?

End users will know something is wrong in either case. At least with a stack trace, wanaweza waandishi wa kudhibiti-printscreen, copy/paste into an email and send it to IT. That would clearly reduce the time and effort required to solve the issue.

</mwisho>

Tags technorati:

Jumapili (Aibu) Mapenzi: “Jina langu ni Paul Galvin”

1 Kujibu

rundo ya miaka iliyopita, 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. Wakati, ilikuwa iliyoundwa na kukimbia kwenye mirija ya kijani (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. Hata hivyo, 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. Kuangalia nyuma juu yake sasa, 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.

Vizuri, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Hivyo, 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 "kutoa habari mbaya mapema" 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. Kwa ajili yangu, 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 au 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, nk. 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, hata hivyo. This was a chemical company, after all. 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, hata hivyo, was this: always test a marker in the lower left-hand corner of a white board before writing, in huge letters, "Paul Galvin".

</mwisho>

Tags technorati: ,

Mitazamo: SharePoint vs. Kubwa Hadron Collider

Acha reply

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.

Kama programu / ushauri watu, we encounter many difficult business requirements in our career. Most the time, sisi love mkutano mahitaji hayo na kwa kweli, pengine ni kwa nini tunafikiri kazi hii ni bora duniani. Mimi mara kwa mara ajabu kile tu katika dunia ingekuwa nimefanya na mimi mwenyewe kama mimi alikuwa amezaliwa wakati mwingine wowote katika historia. 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!" Bora bado, 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). Lakini, 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. Itakuwa kabisa mkate 🙂

</mwisho>

Tags technorati:

Haraka Hisia: Mfumo Center Uwezo Mpangaji kwa SharePoint

Acha reply

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

Nimeona ni rahisi kutumia na haraka inatokana mazingira mteja mimi kazi katika majira hii iliyopita.

Na trepidation baadhi, Mimi taabu mwisho OK kifungo na ilipendekeza kitu ambacho ni pretty sawa na kile sisi alitoa mteja wetu (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, nk), 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:

  • Kutafuta: Total documents, maybe types of documents, languages.
  • Excel server: how much, kama wakati wote?
  • Forms server: how much, kama wakati wote?
  • BDC: how much, kama wakati wote.

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 na badala yake kufanya kazi kwa kampuni halisi :), 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.

</mwisho>

Tags technorati:

Ufumbuzi: System.IO.FileNotFoundException juu ya “SPSite = mpya SPSite(url)”

11 majibu

UPDATE: I posted swali hili kwa MSDN hapa (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

Mimi umba huduma ya mtandao wa kutenda kama BDC-kirafiki facade to a SharePoint list. When I used this from my development environment, ni kazi nzuri. Wakati mimi alihamia hii server mpya, Mimi wamekutana kosa hili:

System.IO.FileNotFoundException: Maombi ya Mtandao katika http://localhost/sandbox hakuweza kupatikana. Kuthibitisha kwamba una typed URL usahihi. Kama URL lazima kuwahudumia bidhaa zilizopo, msimamizi wa mfumo inaweza haja ya kuongeza mpya ombi URL ramani na maombi ya lengo. saa Microsoft.SharePoint.SPSite .. ctor(SPFarm kilimo, Uri requestUri, Boolean contextSite, SPUserToken userToken) saa Microsoft.SharePoint.SPSite .. ctor(Kamba requestUrl) saa Conchango.xyzzy.GetExistingDocument(Kamba minId, Kamba maxId, Kamba cheo filter) katika C:\Nyaraka na Settings Paulo My Documents Visual Studio 2005 Miradi xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:mstari 69

Hapa ni mstari 69:

kutumia (SPSite tovuti = mpya SPSite("http://localhost/sandbox"))

Nilijaribu tofauti tofauti juu ya URL, ikiwa ni pamoja na kutumia seva jina halisi, anwani yake ya IP, trailing mikwaju juu ya URL, nk. I always got that error.

Nilikuwa Google to research it. Lots of people face this issue, au tofauti yake, lakini hakuna mtu walionekana kuwa ni kutatuliwa.

Tricksy MOSS zinazotolewa kosa vile kina kwamba hakuwa kutokea kwangu kuangalia 12 hive logs. Hatimaye, kuhusu 24 baada ya masaa yangu mwenzake ilipendekeza mimi kufanya hivyo, I checked nje 12 mzinga logi na kupatikana hii: 

ubaguzi ilitokea wakati wa kujaribu kupata shamba la mtaa:
System.Security.SecurityException: Tafsiri upatikanaji Msajili haruhusiwi.
saa System.ThrowHelper.ThrowSecurityException(ExceptionResource rasilimali) katika
(Kamba jina, Boolean writable) katika
(Kamba jina) katika
() katika
() katika
(SPFarm& kilimo, Boolean& isJoined)
Kanda ya mkutano kwamba wameshindwa mara:  MyComputer

Hii kufunguliwa fursa mpya ya utafiti, hivyo ilikuwa nyuma ya Google. Kwamba aliniongoza hii jukwaa baada ya: 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 ya 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. Hata hivyo, mwenzangu akaenda akawapa pool programu utambulisho akaunti kamili upatikanaji wa SQL.

Haraka kama yeye alifanya kwamba mabadiliko, everything started working.

Kilichotokea ijayo ni bora walionyesha kama haiku shairi:

Matatizo ya kuinua mikono yao.
You swing and miss. Try again.
Mafanikio! But how? Kwa nini?

Yeye hakutaka kuacha mambo peke yake kama kwamba, wakipendelea kutoa kima cha chini cha required ruhusa (na pengine kwa jicho kwa kuandika kuingia blog; Mimi kuwapiga wake Punch, muhahahahaha!).

Yeye kuondolewa ruhusa mfululizo kutoka akaunti ya programu pool utambulisho mpaka … 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.

Hivyo, kwa kurejea: we gave the app pool identity full access and then took it away. The web service started working and never stopped working. Bizarre.

Kama mtu anajua kwa nini kwamba wanapaswa kuwa na kazi, tafadhali acha maoni.

</mwisho>

Tags technorati: