Monthly Archives: Febrúar 2008

Sunnudagur Fyndið: “EKKI til útflutnings”

Skildu eftir skilaboð

Aftur um 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, auðvelt fyrir notendur, áberandi, multi-tungumál, o.fl.. Sad to say, Ég sennilega ekki haft eins metnaðarfulla setja vinnu til að ná frá þeim heady daga.

This effort pre-dated Microsoft.NET. Plain vanilla ASP was still somewhat new (eða amk mjög framandi fyrir fyrirtæki mitt). "Brick and mortar" companies were doomed. Skapadómur! This is to say that it was pioneering work. Ekki Hadron Collider brautryðjendastarf, en fyrir okkur í litla heiminum okkar, það var brautryðjandastarf.

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.

Og að lokum, 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.

Lokum, I started to read the packaging material on a piece of software I was hand-carrying with me to the client, Netscape’s web server. I’m reading the hardware/software requirements, the marketing blurbs, looking at the pretty picture and suddenly, I zero in on the giant "NOT FOR EXPORT" warning, something about 128 bit encryption. I stuffed the box back into my carry bag, warning face-down (as if that would have helped) and tried to keep visions of Midnight Express out of my head.

Looking back on it now, I should have been worried, if at all, when I left the U.S., ekki þegar ég var að fara inn í Kína 🙂 Ekkert óeðlilegt gerðist og ég tel þetta enn vera besta og eftirminnilegasta viðskiptaferð sem ég hef notið þeirrar ánægju að fara í..

</enda>

Gerast áskrifandi að bloggið mitt!

Technorati Tags: ,

Lausn: SPQuery Er Ekki Leita Mappa

3 Svör

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. Neðsta lína: assign "recursive" að skoða eiginleiki af fyrirspurninni.

Atburðarás minn:

  • Á mánudaginn, Ég hlaða skjal og veita sumir meta gögn.
  • The following week, 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").
  • We’ve created a web service façade that provides a BDC-friendly interface to the list so that users can easily locate that Monday document via a title search.
  • A BDC data column provides a friendly user interface. (This is part of my attempt at using BDC for a more friendly Lookup column).

The final BDC façade service uses a query like this to do the lookup:

 // Used U2U tool to assist in generating this CAML query.
      oQuery.Query =
        "<Hvar>";

      ef (titleFilter.Length > 0)
        oQuery.Query  =
          "  <Og>";

      oQuery.Query  =
        "    <Og>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + minId + "</Gildi>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</Gildi>" +
        "      </Leq>" +
        "    </Og>";

      ef (titleFilter.Length > 0)
        oQuery.Query  =
          "    <Inniheldur>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Gildi>" +
          "    </Inniheldur>" +
          "  </Og>";
      oQuery.Query  =
        "</Hvar>";

During the initial stage of development, this worked great. Hins, we introduced folders into the directory to solve some problems and suddenly, 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, we create a folder based on the list item’s ID and then move the file there (I wrote about that hér; we’ve had mixed results with this approach but on the whole, it’s working well). 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 = ný SPQuery();

I instead used a constructor that specified a view:

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

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

That solved the problem and I started to get my results.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, so far as I can tell, does not work with the view the same way as the a simpler GEQ / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", eins og í:

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

That solved the problem for CONTAINS. Í raun, þetta leyst einnig upprunalega leita vandamál mitt og ef ég hefði tilgreint endurkvæma eiginleiki í fyrsta sinn, Ég myndi ekki hafa keyrt inn í málið aftur.

Sú staðreynd að skoða byggir SPQuery virkar fyrir suma rekstraraðila (GEQ / LEQ) og ekki aðra (Inniheldur), ásamt þeirri staðreynd að KPIs virðist ekki vinna á öllum með möppu innihalda skjal bókasöfnum leiðir mig að trúa því að SPQuery hefur sumir orthogonality málefni.

Sérstakar þakkir:

</enda>

Gerast áskrifandi að bloggið mitt!

MOSS KPI galla? Listi Vísir bundin Document Library með möppur

1 Svara

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 hér). 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 með fullt af skjámyndum ef þú hefur áhuga.

Í stuttu máli, Ég gerði eftirfarandi:

  • Create a view on the doc library called "Pending".
  • Stilltu útsýnið til að hunsa möppuskipulag.
  • Búðu til KPI lista.
  • Create an indicator in the list that points to the doc lib and that "Pending" skoða.

Þetta einfaldlega gengur ekki. KPI sýnir markmiðið mitt (e.g. fimm brýn skjöl) en sýnir alltaf raunverulegan fjölda brýnna skjala sem núll. Þversagnakennt, ef þú kafar niður í smáatriðin, það sýnir fimm brýn skjöl á listanum. Ég bjó til mjög einfalda atburðarás með tveimur skjölum, einn í möppu og einn ekki. Here is the screen shot:

mynd

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.

</enda>

Gerast áskrifandi að bloggið mitt!

Technorati Tags:

SPD Vinnuflæði “Safna gögnum frá notanda”: Breyta Mynda Verkefni Form

4 Svör

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" aðgerð svo að við getum hvetja notandann fyrir mismunandi bita af upplýsingum, svo sem hvort þeir samþykkja það, sumir athugasemdir og kannski spyrja hvað þeir höfðu í kvöldmat um daginn.

The forms are perfectly functional. They are tied to a task list as a content type. Þau eru 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Hins, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, við þurfum að grípa til ýmissa bragðarefur til að fá í kringum það (til dæmis, setja forgang á verkefni).

Ég þurfti að gefa upp tengil á þessa verkefni form sem opnaðist útsýnið eignir (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:

mynd

Sem betur fer, we can do that and it’s not very hard. Broadly speaking, skjóta upp 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, leit eða önnur XSL atburðarás, this will be easy for you. Í raun, Ég fann það að vera almennt auðveldara þar sem mynda mynd er nokkuð auðveldara að fylgja samanborið við algerlega leitarniðurstöður vefur hluti (eða nightmarish CWQP).

Auðvitað, 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" stíga.

Próf 1:

  • Breyta aspx skrá við hönd.
  • Prófa það (staðfesta að breytingar þínar voru rétt vistuð og ekki brjóta neitt).
  • Opinn upp workflow og bæta óskyld aðgerð (such as "log to history").
  • Vista workflow.

Niðurstaða: Í þessu tilviki, SPD ekki tilvísun til-skapa það form.

Próf 2:

  • Gera það sama og #1 except directly modify the "collect data from a user" aðgerð.

Niðurstaða: Þetta aftur skapar form frá grunni, yfir-skrifa breytingarnar.

Final Skýringar:

  • Að minnsta kosti tveir SPD aðgerðir skapa form eins og þetta: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ form er hægt að höndunum breytt.
  • ÉG var fær til að mynda minn hlekkur til dispform.aspx því, í þessu tilfelli, 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, svo ég veit ekki hvort gerist hinum megin á hyldýpi.
  • Ég vissi ekki að rannsaka, en ég myndi ekki vera hissa ef það er einhvers konar skrá sniðmát í 12 Hive, að ég gæti breytt til að hafa áhrif á hvernig SPD býr sjálfgefin eyðublöð (mikið eins og við getum breytt viðvörun sniðmát).

</enda>

Gerast áskrifandi að bloggið mitt!

Eru “Óþekkt villa” Skilaboð Really betri en a Stack Trace?

3 Svör

Ég var að lesa blogg Madhur um hvernig á að gera stafla ummerki sýna og nú er ég að velta fyrir mér: Hvers vegna eigum við ekki að sýna alltaf stafla ummerki?

Sem kom upp með þeirri reglu og hvers vegna fylgjum við það?

End users will know something is wrong in either case. At least with a stack trace, þeir geta stutt stjórn-PrintScreen, copy/paste into an email and send it to IT. That would clearly reduce the time and effort required to solve the issue.

</enda>

Technorati Tags:

Sunnudagur (Vandræðaleg) Fyndið: “Nafn mitt er Paul Galvin”

1 Svara

A fullt af árum, 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. At the time, það var hannað til að keyra á græna rör (e.g. Wyse 50 flugstöðinni) connected to a Unix box via telnet.

My default answer to any question that starts with "Can you … " is "Yes" og það er þar sem allar vandræði byrjaði.

Viðskiptavinurinn var efna fyrirtæki í Suður-Kaliforníu og hafði bara um umbúðir upp stórt ERP framkvæmd á grundvelli Er QAD 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. Hins, Ég hafði fram fjölda annarra flokka þjálfun og var fljótur á fætur, so I was not too worried. Dennis, alvöru fullur-tími niðurstöður kennari, 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?

Til að flækja hlutina 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, fara til Chicago, meet for an hour with prospect and then continue on to California.

Jæja, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Svo, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, Ég komast að því að viðskiptavinurinn er að læra minna en 24 hours before my arrival that "Paul Galvin" er að kenna bekknum, 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 "gefa slæmar fréttir snemma" philosophy. Awesome.

Ég kem á flugvellinum og fyrir sumir ótrúlega heimskur ástæða, I had checked my luggage. I made it to LAX but my luggage did not. Fyrir mig, tapa farangur er mikið eins og að fara í gegnum sjö stigum sorg. Eventually I make it to the hotel, án farangri, þreyttur, svangur og þreytandi minn (nú, mjög krumpuðum) business suit. It takes a long time to travel from Newark — to O’Hare — til viðskiptavinar — aftur til O'Hare — og að lokum til LAX.

Mér finnst loksins sjálfur situr á hótelherbergi, munching á 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.

Ég vaknaði næsta 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, í eigin persónu hún var 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 eða 20 nemendur saman rólega, most them still expecting Dennis.

Ég byrja alltaf á þjálfun bekkinn með því að kynna mig, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", Ég skrifa nafn mitt, 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, o.fl.. 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, það leit svona út: There is this "Paul Galvin" manneskja, 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 varanleg merki. What a sight!

Það endaði allt hamingjusamlega, þó. This was a chemical company, eftir allt. A grizzled veteran employee pulled something off the shelf and, líklega í bága EPA reglugerðir, 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, svo ég var miklu meira frambærilegur dagar tveir og þrír.

Eins og ég var að taka rauða augað heim, 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, þó, var þetta: alltaf prófa merki í neðri vinstra horninu á hvítum borð áður en að skrifa, í stórum stöfum, "Paul Galvin".

</enda>

Technorati Tags: ,

Sjónarmið: SharePoint Vs. The Large Hadron Collider

Skildu eftir skilaboð

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.

Og hugbúnaður / ráðgjöf fólk, we encounter many difficult business requirements in our career. Most the time, við elskum fundinn þeim kröfum og í raun, 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, á þessum stað og tíma í sögu heimsins? Ég held: nokkuð hræðileg.

Í gegnum árin, some of the requirements I’ve faced have been extremely challenging to meet. Complex SharePoint stuff, bygging vefur vinnslu ramma byggt á non-vefur-vingjarnlegur tækni, complex BizTalk orchestrations and the like. We can all (vonandi) líta stolti baka á feril okkar og segja, "yeah, sem var erfitt einn til að leysa, en á endanum ég pwned að sumbitch!" Better yet, Jafnvel fleiri áhugaverður og gaman áskoranir bíða.

Ég held persónulega að ný minn, í þessu sambandi, er nokkuð djúpt og ég er nokkuð stolt af því (þó að ég veit konan mín mun aldrei skilja 1/20th af því). But this week, Ég var að lesa grein um að Large Hadron Collider in my Scientific American magazine and had one of those rare humbling moments where I realized that despite my "giant" staða í ákveðnum hópum eða hversu djúpt ég held vel minn reynslu, 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 (þó að ég hef verið mjög grunsamlega um það síðan ég lærði að það er hægur snúningur jarðar, sem getur ekki verið gott fyrir okkur mönnum í langan tíma). En, the LHC team does have to worry. LHC’s measuring devices are so sensitive that they are affected by the Moon’s (Earth-snúningur-hægur-og-að lokum-morð-allt-líf) gravity. That’s a heck of a requirement to meet — framleiða réttar mælingar þrátt truflunum tunglsins.

Ég var að velta þessi mál þegar ég las þessa setningu: "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.

Næst þegar ég er út með nokkrum vinum, Ég ætla að hækka á ristuðu brauði til góða sem vinna á LHC, hope they don’t successfully weigh the Higgs boson particle and curse the Moon. I suggest you do the same. Það verður alveg ristað brauð 🙂

</enda>

Technorati Tags:

Quick Impression: System Center Stærð Skipuleggjandi fyrir SharePoint

Skildu eftir skilaboð

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

Mér fannst það auðvelt í notkun og fljótt fyrirmynd viðskiptavinur umhverfi ég vann á þessu síðasta sumar.

Með sumum trepidation, Ég sótti endanlega lagi hnappinn og það er mælt með eitthvað sem er nokkuð svipað og það sem við gáfum viðskiptavinur okkar (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, o.fl.), 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:

  • Leita: Total documents, maybe types of documents, languages.
  • Excel server: how much, if at all?
  • Forms server: how much, if at all?
  • BDC: how much, if at all.

Those may be modeled and I just didn’t see them in the 10 minute review.

I will definitely use it at my next client.

If I were not a consultant and instead working for a real company :), I’d model my current environment and see how the tool’s recommended model matches up against reality. That would be pretty neat. It could lead to some good infrastructure discussion.

</enda>

Technorati Tags:

Lausn: System.IO.FileNotFoundException á “SPSite = new SPSite(url)”

11 Svör

UPDATE: ÉG staða þessa spurningu til MSDN hér (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

Ég bjó til vefur þjónusta til að starfa sem BDC-vingjarnlegur framhlið to a SharePoint list. When I used this from my development environment, það í uppnámi fínn. Þegar ég flytja þetta til nýja miðlara, Ég fundur this villa:

System.IO.FileNotFoundException: The Web umsókn á http://localhost/sandbox Ekki var hægt að finna. Staðfestu að þú hefur slegið inn vefslóð rétt. Ef slóðina skal þjóna núverandi innihald, kerfisstjóri getur þurft að bæta við nýjum beiðni URL kortlagning á fyrirhugaða notkun. á Microsoft.SharePoint.SPSite .. ctor(SPFarm bæ, Uri requestUri, Boolean contextSite, SPUserToken userToken) á Microsoft.SharePoint.SPSite .. ctor(String requestUrl) á Conchango.xyzzy.GetExistingDocument(String minId, String maxId, String titill síu) í C:\Documents and Settings Paul My Documents Visual Studio 2005 Verkefni xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:lína 69

Hér er lína 69:

með (SPSite síða = new SPSite("http://localhost/sandbox"))

Ég reyndi mismunandi afbrigði á vefslóðinni, þ.mt overusing raunverulegt nafn miðlarans, IP tölu þess, slóð rista á vefslóðina, o.fl.. I always got that error.

Ég notaði The Google to research it. Lots of people face this issue, eða afbrigði af henni, en enginn virtist tvö hafa það leyst.

Tricksy MOSS veitt svo nákvæma villa að það var ekki komið að mér tvo athuga 12 hive logs. Lokum, um 24 klukkustundum eftir samstarfsmaður minn mælt ég gera það, Ég skoðaði út 12 Hive þig og fann þetta: 

Undantekning kom upp þegar reynt tvö Fá staðbundin bæ:
System.Security.SecurityException: Umbeðin skrásetning aðgangur er ekki leyft.
á System.ThrowHelper.ThrowSecurityException(ExceptionResource úrræði) á
(String nafn, Boolean skrifanleg) á
(String nafn) á
() á
() á
(SPFarm& bæ, Boolean& isJoined)
The Zone á þingi sem ekki var:  MyComputer

Þetta opnaði nýjar leiðir rannsóknir, svo það var aftur til Google. Það leiddi mig til þessa vettvangur staða: 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 er Connell post finally triggered the thought that I should make sure that the application pool’s identity account had appropriate access to the database. I thought it already did. Hins, samstarfsmaður minn fór og gaf laug app kennimark reikning fullan aðgang að SQL.

Um leið og hún gerði þessi breyting, everything started working.

Hvað gerðist næst er best lýst sem Haiku ljóð:

Vandamál hækka hendur þeirra.
You swing and miss. Try again.
Velgengni! But how? Hvers vegna?

Hún vildi ekki láta hlutina einn svona, preferring að gefa nauðsynlegar eru leyfi (og sennilega með auga til að skrifa bloggfærslu; Ég barði hana til að kýla, muhahahahaha!).

Hún fjarlægt röð leyfi frá laug app sjálfsmynd reikning þar … 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.

Svo, að ágrip: we gave the app pool identity full access and then took it away. The web service started working and never stopped working. Bizarre.

Ef einhver veit hvers vegna það ætti að hafa unnið, vinsamlegast eftir athugasemd.

</enda>

Technorati Tags: