Buwanang Archive: Pebrero 2008

Linggo ng nakakatawang: “HINDI PARA SA PAGLULUWAS”

Mag-iwan ng reply

Bumalik sa palibot 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, madali para sa mga end user, marangya, multi-wika, at iba pa. 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.

At sa wakas, 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, kung sa lahat, when I left the U.S., hindi noong papasok ako sa China 🙂 Walang nangyaring hindi kanais-nais at itinuturing ko pa rin iyon na ang pinakamahusay at pinaka-memorable na paglalakbay sa negosyo na nasiyahan ako sa paggawa.

</dulo>

Mag-subscribe sa aking blog!

Technorati Tags: ,

Solusyon: SPQuery ba Hindi Maghanap Folder

3 tugon

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. Ika-line: assign "recursive" sa view na katangian ng mga query.

Aking mga sitwasyong:

  • Sa Monday, I-upload ang dokumento at matustusan ang ilang mga meta data.
  • Ang mga sumusunod na linggo, 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").
  • Lumikha kami ng isang web façade na serbisyo na nagbibigay ng isang BDC-friendly interface sa listahan upang ang mga user ay maaaring madaling mahanap na Lunes dokumento sa pamamagitan ng isang paghahanap pamagat.
  • A BDC data column provides a friendly user interface. (Ito ay bahagi ng aking mga pagtatangka sa paggamit ng BDC para sa isang mas friendly na hanay ng Paghahanap).

Ang huling BDC façade serbisyo ay gumagamit ng isang query tulad nito upang gawin ang paghahanap:

 // Ginamit U2U tool upang makatulong sa pagbuo ng mga ito CAML query.
      oQuery.Query =
        "<Saan>";

      kung (titleFilter.Length > 0)
        oQuery.Query   =
          "  <At>";

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

      kung (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Naglalaman ng>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Halaga>" +
          "    </Naglalaman ng>" +
          "  </At>";
      oQuery.Query   =
        "</Saan>";

Sa panahon ng unang yugto ng pag-unlad, this worked great. Gayunman, ipinakilala namin ang mga folder sa direktoryo upang malutas ang ilang mga problema at bigla, 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, lumikha kami ng isang folder batay sa mga ID ng mga item sa listahan at pagkatapos ay ilipat ang mga file doon (Ko sinulat ni tungkol sa na dito; mayroon kaming halo-halong mga resulta may diskarteng ito ngunit sa kabuuan, ito ay mahusay na gumagana). 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 = bago SPQuery();

Ko sa halip ay gumamit ng isang constructor na tinukoy ng tanawin:

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

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

Na malulutas ang problema ko at sinimulan upang makakuha ng aking mga resulta.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, sa ngayon bilang ang maaari kong sabihin, ay hindi gumagana sa view ng ang parehong paraan tulad ng isang mas simpleng GEQ / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", tulad ng sa:

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

That solved the problem for CONTAINS. Sa katunayan, ito rin malutas sa aking orihinal na problema sa paghahanap at kung ako ay tinukoy ang recursive katangian sa unang pagkakataon, Hindi ko nais na tumakbo sa mga isyu muli.

Ang katotohanan na ang isang pagtingin na batay sa SPQuery gumagana para sa ilang mga operator (GEQ/LEQ) at hindi ang iba (NAGLALAMAN), isinama sa ang katunayan na ang KPI hindi mukhang gumana sa lahat ng mga may-folder na naglalaman ng mga library dokumento humantong sa akin upang maniwala na SPQuery ay may ilang mga isyu orthogonality.

Espesyal na Salamat:

</dulo>

Mag-subscribe sa aking blog!

Moss KPI bug? Listahan Tagapagbatid ng nakatali sa Library ng Dokumento Sa Folder

1 Sumagot

I-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 dito). 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, I did the following:

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

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:

imahen

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

Lumilitaw sa akin na kahit na iyong tinukoy ng tanawin, the KPI doesn’t honor the "show all items without folders" pagtatakda at sa halip ay, paligid mismo sa folder na root.

Kung ako ay mali, mangyaring i-drop ako ng isang linya o mag-iwan ng komento.

</dulo>

Mag-subscribe sa aking blog!

Technorati Tags:

SPD workflow “Mangolekta ng Data Mula sa Isang User”: Baguhin ang Binuo ng Form Task

4 tugon

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" pagkilos upang maaari naming prompt ng gumagamit para sa iba't ibang piraso ng impormasyon, tulad ng kung aprubahan nila ito, ilang mga komento at maaaring magtanong kung ano ang kanilang ay may para sa hapunan sa iba pang mga gabi.

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. Gayunman, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, kailangan namin sa resort sa iba't ibang trick upang makakuha ng paligid nito (halimbawa, pagse-set ng priority sa isang gawain).

Kailangan ko upang magbigay ng isang link sa mga form ng gawain na binuksan ang mga katangian ng tanawin (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:

imahen

Thankfully, we can do that and it’s not very hard. Broadly speaking, painitin 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, paghahanap o iba pang mga sitwasyon ng XSL, this will be easy for you. Sa katunayan, Nakita ko ito sa pangkalahatang mas madali dahil ang nabuong form ay medyo madali upang sundin kumpara sa mga resulta ng paghahanap core bahagi web (o ang kakila-kilabot CWQP).

Talaga, 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" hakbang.

Pagsubok 1:

  • Baguhin ang ASPX file sa pamamagitan ng kamay.
  • Subukan ito (i-verify na ang iyong mga pagbabago ay maayos na-save at ay hindi lumalabag sa anumang).
  • Buksan ang workflow at magdagdag ng isang hindi nauugnay na pagkilos (such as "log to history").
  • I-save ang workflow.

Magbunga: Sa kasong ito, SPD hindi muling likhain ang form.

Pagsubok 2:

  • Gawin ang parehong bilang #1 except directly modify the "collect data from a user" aksyon.

Magbunga: Ito muling lumilikha ng form mula sa simula, over-sumusulat ng iyong mga pagbabago.

Final Tala:

  • Hindi bababa sa dalawang SPD pagkilos lumikha ng mga form tulad nito: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ form nang manu-mano ang binagong.
  • Ako ay magagawang upang bumuo ng aking link sa dispform.aspx dahil, sa kasong ito, 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, kaya hindi ko alam kung nakakakuha ng sa iba pang mga gilid ng bangin.
  • Hindi ko sinisiyasat, ngunit hindi ako magiging magulat kung may ilang mga uri ng file ng template sa 12 pugad na maaari kong baguhin upang makaapekto sa kung paano bumubuo ng SPD ang form na default (halos tulad ng maaari naming baguhin ang mga template ng alerto).

</dulo>

Mag-subscribe sa aking blog!

Technorati Tags: ,

Sigurado “Hindi Kilalang Pagkakamali” Mensahe Talagang Mas mahusay na Hihigit Trace Stack?

3 tugon

Ako ay nagbabasa ng blog post Madhur kung paano ito isalansan paganahin ang display trace at ngayon ako nagtataka: bakit hindi kami palaging magpapakita ng isang stack trace?

Sino ang dumating up na may mga panuntunan at bakit namin sundin ito?

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

</dulo>

Technorati Tags:

Linggo (Nakakahiya) Nakakatawa: “Aking Pangalan ay Paul Galvin”

1 Sumagot

Ang isang grupo ng mga taon na nakalipas, 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. Sa oras, ito ay dinisenyo upang tumakbo sa mga berdeng tubes (e.g. Wyse 50 hantungan) connected to a Unix box via telnet.

My default answer to any question that starts with "Can you … " is "Yes" at na kung saan ang lahat ng mga problema sa magsimula.

Ang client ay isang kemikal kumpanya out sa southern California at si lamang tungkol sa balot up ng isang pangunahing pagpapatupad ng ERP batay sa QAD ni 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. Gayunman, Ako ay isinasagawa ng isang bilang ng iba pang mga klase sa pagsasanay at naging mabilis sa aking mga paa, so I was not too worried. Dennis, ang tunay na full-time na magtuturo Resulta, 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?

Upang makapagpalubha bagay 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, pumunta sa Chicago, meet for an hour with prospect and then continue on to California.

Mahusay, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Kaya, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, Tingin ko out na ang kliyente ay pag-aaral ng mas mababa sa 24 hours before my arrival that "Paul Galvin" ay nagtuturo ng klase, 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 "magbigay ng masamang balita maaga" philosophy. Awesome.

Dumating ako sa airport at para sa ilang mga hindi kapani-paniwalang nakababagod dahilan, I had checked my luggage. I made it to LAX but my luggage did not. Sa akin, nawawala ang luggage ay isang maraming tulad ng pagpunta sa pamamagitan ng pitong yugto ng kalungkutan. Eventually I make it to the hotel, na walang luggage, pagod, gutom at suot ang aking (sa ngayon, napaka bayuot) business suit. It takes a long time to travel from Newark — to O’Hare — sa isang client — pabalik sa O'Hare — at sa wakas sa LAX.

Ako sa wakas mahanap ang aking sarili upo sa kuwarto hotel, munching sa isang bar paggalikgik, 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.

Ako woke up sa susunod na araw, 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, sa tao siya ay magaling, 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 o 20 mga mag-aaral mabagal mag-ipon, most them still expecting Dennis.

Ako palaging simulan-off ang aking mga klase sa pagsasanay sa pamamagitan ng pagpapakilala ng aking sarili, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", Isulat ko ang aking pangalan, 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, at iba pa. 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, ito ay mukhang ganito: There is this "Paul Galvin" tao, 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!

Ito ang lahat ng natapos na maligaya, gayunman. This was a chemical company, sa wakas. A grizzled veteran employee pulled something off the shelf and, malamang na lumalabag sa mga regulasyon EPA, 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, kaya ako ay higit na mas maganda araw ng dalawa at tatlong.

Habang ako ay paglalaan ng red eye kamalig, 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, gayunman, noon ito: laging subukan ang isang marker sa ibabang kaliwang sulok ng isang puting board bago magsulat, sa malaking titik, "Paul Galvin".

</dulo>

Technorati Tags: ,

Pananaw: SharePoint vs. ang Large Hadron Collider

Mag-iwan ng 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.

Tulad ng software / pagkonsulta sa mga tao, 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? Sa tingin ko: 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!" Mas mahusay pa, 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). Pero, 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 🙂

</dulo>

Technorati Tags:

Mabilis na Impression: System Center Kapasidad Planner para sa SharePoint

Mag-iwan ng reply

Ko lang fired up ang kapasidad tool sa pagpaplano na ang lahat ng mga kinahuhumalingan mga araw na ito.

May nakita akong ito madaling gamitin at mabilis na imo-modelo ng client kapaligiran ko nagtrabaho sa nakalipas na ito ng tag-init.

Sa ilang mga pangamba, Pinindot ko ang pangwakas na pindutan na OK at ito inirerekomenda ng isang bagay na ay medyo katulad sa kung ano ang aming ibinigay sa aming mga kliyente (talaga namin threw sa isang pangalawang server application para sa hinaharap na paggamit excel). I take that to be a good sign and increases my confidence in the tool.

Mukhang medyo malakas na mga bagay-bagay sa isang mas mas mahusay na panimulang punto sa isang blangkong pahina.

I like that lets you get into some good detail about the environment. How many users, paano mo maipakita ang mga ito gamitin ang sistema (paglilimbag, pakikipagtulungan, at iba pa), sangay ng opisina at pagkakakonekta / network capacity between them and the mama server. Good stuff.

Ito Humihingi malawak na batay sa mga tanong at pagkatapos ay hinahayaan kang mag-tweak ang mga detalye para sa isang marikit na butil-butil na modelo ng iyong kapaligiran.

Ako hesitated download nito dahil mayroon akong kaya maraming iba pang mga bagay upang tumingin sa ito, 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.

Batay sa aking mabilis na impression, Hindi ko makita kung paano ito account para sa:

  • Hanapin: Kabuuang mga dokumento, siguro mga uri ng mga dokumento, mga wika.
  • Excel server: magkano, kung sa lahat?
  • Forms server: magkano, kung sa lahat?
  • BDC: magkano, kung sa lahat.

Yaong maaaring imo-modelo at ko lang ay hindi makita ang mga ito sa 10 minutong pagsusuri.

Ako ay talagang gamitin ito sa aking mga susunod na client.

Kung ako ay hindi isang kasangguni at sa halip ay nagtatrabaho para sa isang kumpanya ng real :), 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.

</dulo>

Technorati Tags:

Solusyon: System.IO.FileNotFoundException sa “SPSite = bagong SPSite(url)”

11 tugon

I-UPDATE: I-post ang tanong na ito sa MSDN dito (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

Lumikha ako ng serbisyo sa web upang kumilos bilang isang BDC-friendly harapan to a SharePoint list. When I used this from my development environment, ito ay nagtrabaho fine. Kailan ko migrate na ito sa isang bagong server, Nakatagpo ako ng error na ito:

System.IO.FileNotFoundException: Ang mga Web application sa http://localhost/sandbox ay hindi mahanap. Pinapatunayan na ikaw ay tama ang URL. Kung ang URL ay dapat na naghahain ng umiiral na nilalaman, ang system administrator ay maaaring kailangan upang magdagdag ng bagong kahilingan URL pagmamapa sa nilalayon application. sa Microsoft.SharePoint.SPSite .. ctor(SPFarm bukid, Uri requestUri, Boolean contextSite, SPUserToken userToken) sa Microsoft.SharePoint.SPSite .. ctor(String requestUrl) sa Conchango.xyzzy.GetExistingDocument(String minId, String maxId, String pamagat filter) sa C:\Documents and Settings Paul My Documents Visual Studio 2005 Proyekto xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:linya 69

Narito ang linya 69:

paggamit (SPSite site = bagong SPSite("http://localhost/sandbox"))

Sinubukan kong iba't-ibang mga pagkakaiba-iba sa mga URL, kabilang ang paggamit ng tunay na pangalan ng server, nito IP address, trailing slashes sa URL, at iba pa. I always got that error.

Ginamit ko Ang Google to research it. Lots of people face this issue, o mga pagkakaiba-iba ng mga ito, ngunit walang isa tila na ito malulutas.

Makisig Moss ibinigay tulad ng isang detalyadong error na hindi ito mangyayari sa akin upang suriin ang 12 hive logs. Eventually, tungkol sa 24 oras matapos aking kasamahan Inirerekumenda gagawin ko kaya, I-check out ang 12 kaharian ng mga laywan log at natagpuan na ito: 

Exception naganap na error habang sinusubukang upang makuha ang mga lokal na bukid:
System.Security.SecurityException: Hiniling na registry access ay hindi pinapayagan.
sa System.ThrowHelper.ThrowSecurityException(ExceptionResource mapagkukunan) sa
(String pangalan, Boolean writable) sa
(String pangalan) sa
() sa
() sa
(SPFarm& bukid, Boolean& isJoined)
Ang Zone ng assembly na nabigo noon ay:  MyComputer

Ito ay nagbukas ng mga bagong avenues ng pananaliksik, kaya ito ay bumalik sa Ang Google. Na humantong sa akin na ito 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 ni 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. Gayunman, aking kasamahan nagpunta at ibinigay ang app na pool pagkakakilanlan account ganap na access sa SQL.

Sa sandali na siya ay ginawa ang pagbabagong iyon, everything started working.

Ano ang nangyari susunod ay pinakamahusay na ipinahiwatig bilang isang hayku tula:

Problema sa itaas ang kanilang mga kamay.
You swing and miss. Try again.
Tagumpay! But how? Bakit?

Hindi niya ay nais na mag-iwan mga bagay tulad ng nag-iisa na, preferring upang bigyan ang minimum na kinakailangang pahintulot (at marahil ay may isang mata sa pagsusulat ng isang blog entry; Matalo ko siya sa mga pamutas, muhahahahaha!).

Inalis niya ang sunud-sunod na pahintulot mula sa app account pool pagkakakilanlan hanggang sa … 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.

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

Kung sinuman ang nakakaalam kung bakit na dapat nakapagtrabaho, mangyaring mag-iwan ng komento.

</dulo>

Technorati Tags: