maandelikse Argiewe: Februarie 2008

Sondag Funny: “NIE vir die uitvoer”

Laat 'n antwoord

Terug rondom 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. Dit het vinnig, maklik vir eindgebruikers, flashy, multi-taal, ens.. Hartseer om te sê, Ek het waarskynlik nie as 'n ambisieuse stel van die werk uit te voer, aangesien dié onstuimige dae.

This effort pre-dated Microsoft.NET. Plain vanilla ASP was still somewhat new (of ten minste baie onbekende vir my maatskappy). "Brick and mortar" companies were doomed. Gedoem! This is to say that it was pioneering work. Nie Hadron Collider baanbrekerswerk, maar vir ons in ons klein wêreld, dit was baanbrekerswerk.

We were crazy busy. We were doing mini POC’s almost every day, uitzoeken hoe om die toestand te handhaaf in 'n inherent staatloos medium, uitzoeken multi-taal kwessies, row-level security. We even had create a vocabulary to define basic terms (Ek verkies staat aanhoudende, maar vir een of ander rede, die ongemaklike "State Full" het die dag).

Soos ons is soos 'n besetene die uitvind van hierdie produk, 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, 'n radikaal verskillende koppelvlak van die "standaard" system but with the same business logic. Multi-language was especially hard in this case, omdat ons altyd gefokus op die Spaanse of Franse, maar in hierdie geval, dit was die Chinese (wat is 'n double-byte karakter stel en vereis spesiale hantering van die tegnologie wat ons gebruik).

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:

  • Amerikaanse: "Kan jy my vertel hoe om te kry [XX] straat?"
  • Chinese: "Ek is jammer, ons praat nie Engels nie ".
  • Amerikaanse: "O, goed ek praat Mandaryns." en Hy vra hulle weer in die Sjinees, maar meer duidelik (as die beste wat hy kon).
  • Chinese: Baie beleefd, "Ek is jammer, ons praat nie Engels nie ".

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, "Ek kon sweer hy het gevra vir aanwysings na [XX] straat."

Ek opgetel het 'n paar stukkies van ander China-verwante kwasi-inligting en "nuttige advies":

  • 'N Koreaanse mede-gewerk het aan my gesê dat die wat ek nodig het om versigtig te wees van die Chinese, want "hulle sal probeer om my dronk te kry en neem voordeel van jou" in die sin van die druk van my in 'n swak sakebesluite.
  • Ons was nie toegelaat om motors te ry (was daar 'n verwarring oor of dit was 'n gewoonte, 'n wetlike vereiste is of net die kliënt se heerskappy).
  • Daar is spesiale reëls vir die wat deur die doeane.
  • Ons was nie toegelaat om Amerikaanse geld te gebruik vir enige iets.
  • You’re not supposed to leave tips. It’s insulting if you do.

En uiteindelik, Ek het relatief vars herinneringe Tiananmen slagting. When I was at college, I remember seeing real-time Usenet postings as the world looked on in horror.

In kort, 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.

Ek is op hierdie 14 uur vlug en al was dit besigheid klas, 14 uur is 'n verdomde lang tyd. Daar is net soveel maniere om jouself te vermaak deur te lees, watching movies or playing with the magnetized cutlery. Even a really good book is hard to read for several hours straight.

Uiteindelik, Ek het begin om die verpakkingsmateriaal te lees op 'n stuk sagteware, was ek die hand wat saam met my aan die kliënt, Netscape’s web server. I’m reading the hardware/software requirements, die bemarking blurbs, op soek na die mooi prentjie en skielik, Ek toespits op die reus "nie vir UITVOER" waarskuwing, iets oor 128 bit encryption. I stuffed the box back into my carry bag, waarskuwing gesig af (asof dit sou gehelp het) en probeer visioene van te hou Midnight Express out of my head.

As ons terugkyk op dit nou, Sou ek bekommerd gewees het, indien enigsins, wanneer ek het die VSA, 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.

</einde>

Skryf in op my blog!

Technorati Tags: ,

Oplossing: SPQuery soek nie na dopgehou

3 antwoorde

Die afgelope week het ek die implementering van 'n "ontwikkelende" solution for a client that uses BDC and SPQuery and ran into some difficulty using SPQuery against a document library containing folders. Bottom line: wys "rekursiewe" die oog kenmerk van die navraag.

My scenario:

  • Op Maandag, Ek laai 'n dokument en verskaf 'n meta data.
  • Die volgende week, I upload a new document. Much of this new document’s meta data is based on the document I uploaded on Monday (wat ons noem die "meester-dokument").
  • Ons het 'n web fasade wat 'n BDC-vriendelike koppelvlak tot die lys sodat gebruikers kan maklik deur middel van 'n titel te soek wat Maandag-dokument vind.
  • A BDC data column provides a friendly user interface. (Dit is deel van my poging om by die gebruik van BDC vir 'n meer vriendelike Lookup kolom).

Die finale BDC gevel diens gebruik 'n navraag, soos die soek om te doen.:

 // U2U hulpmiddel om te help in die opwekking van hierdie CAML navraag.
      oQuery.Query =
        "<Waar>";

      indien (titleFilter.Length > 0)
        oQuery.Query   =
          "  <En>";

      oQuery.Query   =
        "    <En>" +
        "      <Geq>" +
        "        <FieldRef Naam =  "DocumentId " />" +
        "        <Waarde Tipe =  "teks ">" + MinID + "</Waarde>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Naam =  "DocumentId " />" +
        "        <Waarde Tipe =  "teks ">" + maxId + "</Waarde>" +
        "      </Leq>" +
        "    </En>";

      indien (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Bevat>" +
          "      <FieldRef Naam =  "Titel " />" +
          "      <Waarde Tipe =  "teks ">" + titleFilter + "</Waarde>" +
          "    </Bevat>" +
          "  </En>";
      oQuery.Query   =
        "</Waar>";

Gedurende die eerste fase van die ontwikkeling, this worked great. Egter, ons bekendgestel dopgehou in die gids 'n paar probleme op te los en skielik, 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, ons 'n gids skep wat gebaseer is op die lys-item se ID en dan beweeg die lêer daar (Ek het geskryf oor hier; ons het gemengde resultate met hierdie benadering nie, maar oor die algemeen, dit goed werk). 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["Dokumente"];

SPQuery oQuery = nuwe SPQuery();

Ek plaas 'n konstruktor wat die oog gespesifiseer:

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

SPQuery oQuery = nuwe SPQuery(oList.Views["Alle dokumente"]);

Dit is die probleem opgelos het en ek het my resultate te kry.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, so ver as wat ek kan sê, nie werk nie met die oog op dieselfde wyse as die van 'n eenvoudiger GEQ / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", soos in:

oQuery.ViewAttributes = "Scope = " Rekursiewe "";

That solved the problem for CONTAINS. In werklikheid, dit is ook my oorspronklike soek probleem opgelos en as ek het vermeld die rekursiewe kenmerk die eerste keer, Ek wil nie gehardloop het nie weer in die saak.

Die feit dat 'n oog-gebaseerde SPQuery werk vir sommige operateurs (GEQ / LEQ) en ander nie (BEVAT), tesame met die feit dat KPI's nie lyk te alle saam met die gids-bevattende dokument biblioteke, lei my om te glo dat SPQuery het 'n paar ortogonaliteit kwessies.

Spesiale dank:

  • Die goeie mense by U2U en hulle navraag instrument.
  • Michael Hoffer se groot "leer deur te doen" blog post, kommentaar en antwoorde.

</einde>

Skryf in op my blog!

MOSS KPI fout? Lys aanwyser wat gekoppel is aan Document Library met dopgehou

1 Antwoord

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. Ek beskryf wat in 'n bietjie meer detail hier.

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 (met behulp van 'n tegniek wat soortgelyk is aan wat ek geskryf het oor hier). We’ve successfully navigated around the potential issues caused by event receivers that rename uploaded files (hoofsaaklik omdat gebruikers nooit begin hul dokument deur te kliek op die "nuwe" maar eerder die skep van die Dokumente plaaslik en dan oplaai).

Die meta data vir hierdie dokumente sluit in 'n Ja / Nee site kolom genaamd "Dringende" and another site column called "Status". We need to meet a business requirement that shows the percentage of "Urgent" dokumente wie se status "In behandeling".

Dit is gewoonlik maklik om te doen en ek beskryf iets baie soos hierdie by die SharePoint Beagle met baie van die skerm skote, as jy geïnteresseerd is.

In 'n neutedop, Ek het die volgende:

  • Skep 'n uitsig op die doc biblioteek "Hangende geroep".
  • Stel die oog op die struktuur van die gids te ignoreer.
  • Skep 'n KPI Lys.
  • Skep 'n aanduiding in die lys wat verwys na die doc lib en dat "Hangende" sien.

This simply does not work. The KPI shows my target (bijv. vyf dringende) but always shows the actual number of urgent documents as zero. Paradoxically, As jy boor tot in die besonderhede, 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:

beeld

Die bogenoemde screen shot toon duidelik dat daar is twee dokumente in die oog, maar die "waarde" is one. The "CamlSchema" met 'n leeg dokument id is in die wortel-lêergids en die ander is in 'n lêergids met die naam "84".

Dit lyk my dat selfs al het u 'n oog, Die KPI nie eer die "Wys al die items sonder dopgehou nie" stel en in plaas, beperk is tot die hoofdmap.

As ek verkeerd is, asb vir my 'n lyn of 'n opmerking verlaat.

</einde>

Skryf in op my blog!

Technorati Tags:

SPD Workflow “Versamel data van 'n gebruiker”: Verander die gegenereerde taak vorm

4 antwoorde

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" aksie, sodat ons kan die gebruiker gevra word vir verskillende stukkies inligting, soos of hulle dit goedkeur nie, 'n paar opmerkings en miskien vra wat hulle vir aandete gehad het die ander aand.

The forms are perfectly functional. They are tied to a task list as a content type. Hulle is 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Egter, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, ons moet die verskillende truuks te kry om dit (byvoorbeeld, stel van voorkeur op 'n taak).

Ek moes 'n skakel op hierdie taak vorms wat die oog eiendomme oopgemaak om voorsiening te maak (dispform.asxp) van die "verwante item" in a new window. This provides one-click access to the meta data of the related item. This is what I mean:

beeld

Gelukkig, we can do that and it’s not very hard. Broadly speaking, vuur op 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, soek-of ander XSL-scenario's, this will be easy for you. In werklikheid, Ek het dit algemeen makliker te wees sedert die vorm wat gegenereer is ietwat makliker om te volg as in vergelyking met 'n soektog kern resultate web deel (of die nagmerrie CWQP).

Natuurlik, 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" stap.

Toets 1:

  • Verander die ASPX lêer met die hand.
  • Toets dit (seker dat jou veranderings is gered en het nie breek nie).
  • Maak die workflow en voeg 'n onverwante aksie (soos "teken in die geskiedenis").
  • Stoor die workflow.

Uitslag: In hierdie geval, SPD het nie her-skep die vorm.

Toets 2:

  • Doen dieselfde as #1 behalwe direk verander die data in te samel van 'n gebruiker" aksie.

Uitslag: Hierdie her-skep die vorm van nuuts af, Oormekaarskryf jou veranderinge.

Finale Notes:

  • Ten minste twee SPD aksies skep vorms soos hierdie: "Versamel data van 'n gebruiker" and "Assign To Do Item". Both of these actions’ vorms kan met die hand verander word.
  • Ek was in staat om my skakel tot dispform.aspx te genereer, want, in hierdie geval, 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 ek weet nie of kry aan die ander kant van die kloof.
  • Ek het nie ondersoek, maar ek sal nie verbaas wees as daar is 'n soort van template lêer in die 12 korf wat ek kon verander om te beïnvloed hoe SPD die standaard vorms genereer (baie soos ons wakker templates kan verander).

</einde>

Skryf in op my blog!

Technorati Tags: ,

Is “Onbekende fout” Boodskappe werklik beter as 'n Stack Trace?

3 antwoorde

Ek was die lees Madhur se blog post oor hoe om te in staat stel stapel spoor uitstallings en nou is ek wonder: hoekom ons nie altyd wys om 'n stapel spoor?

Wat gekom het met die reël en hoekom volg ons dit?

End users will know something is wrong in either case. Ten minste met 'n stapel spoor, hulle kan beheer-printscreen druk, copy/paste into an email and send it to IT. That would clearly reduce the time and effort required to solve the issue.

</einde>

Technorati Tags:

Sondag (Verleentheid) Snaaks: “My naam is Paul Galvin”

1 Antwoord

'N klomp jare gelede, 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. Op die oomblik, dit is ontwerp om te hardloop op groen buise (bijv. Wyse 50 terminale) connected to a Unix box via telnet.

My default answer to any question that starts with "Can you … " is "Yes" en dit is waar al die moeilikheid begin.

Die kliënt is 'n chemiese maatskappy in die suide van Kalifornië en het net oor toegedraai 'n groot ERP implementering gebaseer op QAD se 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. Egter, Ek het het 'n aantal ander opleiding klasse en was vinnig op my voete, so I was not too worried. Dennis, die werklike voltydse Resultate instrukteur, had given me his training material. As ons terugkyk op dit nou, 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?

Dinge om logistieke bemoeilik, 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, gaan na Chicago, meet for an hour with prospect and then continue on to California.

Wel, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. So, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, Ek vind dat die kliënt is minder as die leer 24 hours before my arrival that "Paul Galvin" word die onderrig van die klas, 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 "gee slegte nuus vroeg" philosophy. Awesome.

Ek kom op die lughawe en vir 'n paar ongelooflik dom rede, I had checked my luggage. I made it to LAX but my luggage did not. Vir my, verloor bagasie is 'n baie soos om deur die sewe stadiums van rou. Eventually I make it to the hotel, met geen bagasie, moeg, honger en die dra van my (deur die nou, baie opgefrommel) business suit. It takes a long time to travel from Newark — to O’Hare — aan 'n kliënt — terug na O'Hare — en uiteindelik na LAX.

Ek het uiteindelik vind myself sit in die hotel kamer, munching op 'n 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.

Ek wakker word die volgende dag, 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 persoon sy was mooi, 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. Die 15 of 20 studente stadig vergader, most them still expecting Dennis.

Ek het altyd begin my opleiding klasse deur die instelling van myself, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", Ek skryf my naam, 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, ens.. 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, dit lyk soos hierdie: There is this "Paul Galvin" persoon, 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 permanente merker. What a sight!

Dit het alles geëindig gelukkig, egter. This was a chemical company, na al. A grizzled veteran employee pulled something off the shelf and, waarskynlik in die skending van die EPA regulasies, 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 ek was baie meer aanvaarbaar dae twee en drie.

Soos ek is die neem van die rooi oë terug by die huis, 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, egter, was dit: altyd die toets van 'n merker in die onderste linkerhoek van 'n wit bord voor te skryf, in groot letters, "Paul Galvin".

</einde>

Technorati Tags: ,

Outlook: SharePoint vs. die Large Hadron Collider

Laat 'n antwoord

Due to some oddball United Airlines flights I took in the mid 90’s, Ek het op een of ander manier geëindig met 'n aanbod te transformeer "ongebruikte myl" into about a dozen free magazine subscriptions. Dit is hoe ek geëindig inskrywing wetenskaplike Amerikaanse tydskrif.

As sagteware / raadgewende mense, 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? Ek dink: 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) kyk met trots terug op ons loopbaan en sê, "yeah, dit was 'n harde een om te los, maar in die einde het ek pwned dat sumbitch!" Beter nog, selfs meer interessant en pret uitdagings wag.

Ek persoonlik dink dat my CV, in hierdie verband, is redelik diep en ek is baie trots op dit (al weet ek my vrou sal nooit verstaan ​​1/20th van dit). But this week, Ek was die lees van 'n artikel oor die 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 sekere kringe of hoe diep dink ek my goed ondervinding, 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). Maar, 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.

Volgende keer as ek uit met 'n paar vriende, Ek gaan 'n heildronk in te samel om die goeie mense wat op die 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 🙂

</einde>

Technorati Tags:

Vinnige indruk: System Center Kapasiteit beplanner vir SharePoint

Laat 'n antwoord

Ek het net afgedank word om die kapasiteit beplanning hulpmiddel wat al die woede hierdie dae.

Ek vind dit maklik om te gebruik en vinnig 'n kliënt omgewing geskoei, ek gewerk het op hierdie afgelope somer.

Met 'n paar angs, Ek die finale OK knoppie gedruk en dit aanbeveel om iets wat is redelik soortgelyk aan wat ons het ons kliënt (ons eintlik gegooi in 'n tweede aansoek bediener vir die toekoms blink gebruik). I take that to be a good sign and increases my confidence in the tool.

Dit lyk redelik kragtige dinge 'n baie beter beginpunt as 'n leë bladsy.

I like that lets you get into some good detail about the environment. How many users, hoe jy die projek sal hulle gebruik om die stelsel (publishing, samewerking, ens.), kantoor en aansluit / network capacity between them and the mama server. Good stuff.

Dit vra breë gebaseerde vrae en dan kan jy verander om die besonderhede vir 'n mooi korrel model van jou omgewing.

Ek aarsel dit te laai want ek het so baie ander dinge om te kyk na dit, 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.

Gebaseer op my vinnige indruk, Ek kan nie sien hoe dit kan rekening vir:

  • Soek: Totale dokumente, Miskien tipes van dokumente, tale.
  • Excel bediener: hoeveel, indien enigsins?
  • Vorms bediener: hoeveel, indien enigsins?
  • BDC: hoeveel, indien enigsins.

Diegene gemodelleer kan word en ek het net nie sien dat hulle in die 10 minuut review.

Ek sal beslis gebruik dit op my volgende kliënt.

As ek nie 'n konsultant en in plaas daarvan om vir 'n werklike maatskappy :), 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.

</einde>

Technorati Tags:

Oplossing: System.IO.FileNotFoundException op “SPSite = nuwe SPSite(url)”

11 antwoorde

UPDATE: Ek gepos hierdie vraag hier aan MSDN (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

Ek het 'n web om op te tree as 'n BDC-vriendelike fasade to a SharePoint list. Toe ek dit uit my ontwikkeling omgewing, dit werk goed. Wanneer ek migreer na 'n nuwe bediener, Ek het hierdie probleem ondervind:

System.IO.FileNotFoundException: Die Web aansoek by http://localhost/sandbox kon nie gevind word nie. Kontroleer dat jy die URL korrek ingetik het. As die URL moet bedien word om bestaande inhoud, die stelsel administrateur mag nodig wees om 'n nuwe versoek URL kartering te voeg tot die voorgenome aansoek. by Microsoft.SharePoint.SPSite .. ctor(SPFarm vrag, Uri requestUri, Boole contextSite, SPUserToken userToken) by Microsoft.SharePoint.SPSite .. ctor(String requestUrl) by Conchango.xyzzy.GetExistingDocument(String minId, String maxId, String titleFilter) in C:\Documents and Settings Paul My Documents Visual Studio 2005 Projekte Xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:lyn 69

Hier is lyn 69:

die gebruik van (SPSite webwerf = nuwe SPSite("http://localhost/sandbox"))

Ek het probeer om die verskillende variasies op die URL, insluitend die gebruik van die bediener se regte naam, die IP-adres, die sleep houe op die URL, ens.. I always got that error.

Ek gebruik Die Google to research it. Lots of people face this issue, of variasies daarvan, maar niemand het dit opgelos.

Speels MOSS so 'n gedetailleerde fout dat dit nie gebeur het nie vir my om seker te maak 12 hive logs. Uiteindelik, oor 24 uur na my kollega Aanbevole ek dit doen, Ek nagegaan word uit die 12 korf log en het gevind dat hierdie: 

'N Uitsondering het voorgekom terwyl hy probeer om die plaas aan te skaf:
System.Security.SecurityException: Versoek register toegang nie toegelaat.
by System.ThrowHelper.ThrowSecurityException(ExceptionResource hulpbron) op
(String naam, Boole skryfbaar) op
(String naam) op
() op
() op
(SPFarm& plaas, Boole& isJoined)
Die Seun van die vergadering wat versuim het om:  MyComputer

Dit het nuwe moontlikhede van navorsing, so was dit terug na die Google. Dit het my gelei tot hierdie 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 se 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. Egter, my kollega het gegaan en het die app swembad identiteit rekening volle toegang tot SQL.

Sodra sy dat verandering, everything started working.

Wat volgende gebeur is die beste uitgedruk as 'n haiku gedig:

Probleme verhoog hul hande.
You swing and miss. Try again.
Sukses! But how? Hoekom?

Sy wou nie dinge te los soos wat, verkies om die minimum vereiste toestemming te gee (en waarskynlik met die oog op die skryf van 'n blog inskrywing; Ek klop haar aan die punch, muhahahahaha!).

Sy verwyder opeenvolgende regte van die app swembad identiteit rekening tot … 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.

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

As iemand weet waarom dit gewerk het, los 'n comment.

</einde>

Technorati Tags: