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:

Ufumbuzi (aina ya): Kuweka kipaumbele juu ya Task Kutumia SharePoint Designer

1 Kujibu

I have a business scenario like this:

  • A user uploads a document to a document library.
  • She selects a content type and enters meta data as needed. One of the meta data fields is a flag, "Urgent".
  • This triggers a SharePoint Designer workflow that, miongoni mwa mambo mengine, uses the "Collect Data from a User" hatua.

"Collect Data from a User" creates an item in a task list requesting approval for that document.

I needed to create a view of the task list that showed urgent requests for approval.

Ufumbuzi: Put the word "URGENT:" into the title of these tasks.

I would have preferred to specify the priority field directly. Hata hivyo, I was unable to do that for several reasons:

  1. The collect data action does not provide a mechanism to update any field other than title (na wale mashamba ya ziada kwa ajili ya ambayo unataka kukusanya data).
  2. The "assign a to do item" hatua ina tatizo moja.
  3. Inawezekana kuingiza bidhaa katika orodha (i.e. kuingiza bidhaa katika orodha ya kazi moja kwa moja) but this not a blocking action. That means that the workflow will not wait for the user to complete that task.

Nikaziangalia mbinu chache kabla ya (nashiriki) realizing we could just put "urgent" katika cheo.

  1. Kuanza workflow kwenye orodha ya kazi yenyewe ili wakati kazi mpya ni kuundwa, marejeo ni kwa namna fulani kuvuka nyuma ya hati ambayo ilianza workflow kwanza, pull out the urgent flag value and update priority as needed.
  2. Do something similar with an event receiver. On create of the task, Machapisho ya hati ya kuhusishwa na update kipaumbele kama inahitajika.
  3. Use the "create list item" action in conjunction with the "wait for field change" action and an event receiver. If we create a list item, we can specify all the fields we want. Use an event receiver to update the original item when the user completes the task and the "wait for field change" action’s condition would be met and the workflow would proceed. (Kwa sababu baadhi ya, Mimi nilikuwa zaidi au chini ya makazi ya mbinu hii kabla ya busara ya kuamua kutembea mbali kwa muda).

Kuna Drawback kwa ufumbuzi yangu (mbali ya ukweli dhahiri kwamba tu Nakala ya cheo inaonyesha uharaka). Since "collect feedback" tu anapokea ngumu coded cheo majina, I need to use two different collect feedback actions whose only difference is that hard coded title.

Lakini, angalau kuna ufumbuzi kwamba hauhitaji kupokea tukio au desturi vitendo SPD.

Kama mtu ana kutatuliwa hili kwa njia ya wajanja zaidi, tafadhali napenda kujua.

</mwisho>

Jumapili Mapenzi: Kutunza Mwana wako On Vidole wake

Acha reply

One of the many joys I take in being the parent of a ten year old boy is finding new ways to make him laugh or think a little differently about questions and things in the world. I’ve used these techniques over the years:

===

Misconstrue maswali yake:

Yake: Siku gani ni?

Baba: Siku moja kabla ya Jumatano.

S: Si, nini siku ya mwezi ni?

D: Oh, ni 4 siku baada ya Jan 25.

===

Tekenya naye na kumwambia wewe itabidi kuacha wakati yeye ataacha laughing.

===

Kwenda chini ya ngazi ya chumba TV na kutangaza, "It’s good to be the daddy." Kisha, kumchukua kupata doa joto juu ya kitanda na kubadili channel kitu kizuri, kama channel SciFi.

===

Read stories out loud. Insert ridiculous sentences in the middle of the story. My favorite is to add "killing him instantly" when the main characters encounters some minor trouble. Kwa mfano, "the knife slipped in his hand, kukata index kidole chake, kumuua papo hapo." Nothing quite gets your son out of a complacent and passive listening mode as the main character being killed instantly.

===

Read stories incorrectly. Read sentences backward. The best part of this is that the first couple of times I did this, my son thought he was helping me out by pointing out that I wasn’t reading the words in the right order. The down side is that he really doesn’t want me to read to him any more.

===

Go to Burger King for lunch. My son would eat BK morning, night and day if we let him. When going, kumwambia, "I know you hate going there, but we simply have no choice." When he tries to explain that he loves BK, talk over him and say things like "We don’t have time to argue about it! We’re going and I don’t want to have a discussion!"

(Hii inanikumbusha utani favorite Borg: "Borger King: We do it our way. Your way is irrelevant." hahaha!)

===

Kufungua kitabu ukurasa 9 na kusema, "hmm, that’s an odd page".

===

Fill the world with arch enemies. "We’re going to run quick over toe 7-11, arch-enemy of 11-7".

"Your aunt lives in Ringwood, Arch adui wa mji wa Squarewood."

===

Sisi kuendesha hadi Massachusetts kutoka New Jersey mara kadhaa kwa mwaka na mara nyingi inachukua kuhusu 5 hours door to door. As we arrive home and pull into the driveway say, "oh, Nimesahau, tunahitaji kufanya dash haraka Home Depot."

===

Wakati kuangalia sehemu ya vurugu katika TV show (kama vile Heroes), kuwaambia mwanao, "some times, kazini, I need to destroy my enemies by burning them alive using the powers of my mind. I don’t like doing it, lakini gotta kufanya nini gotta kufanya."

===

Wakati kuangalia sinema horror mbaya (see "It’s good to be the Daddy" juu ya), ascribe improbable motives to the evil character. Kwa mfano, tell your son that the reason Jason is so angry is because he wants some cake and they won’t let him have any.

===

Explain phone numbers incorrectly. Instead of telling your son to dial "201-111-2222", tell him it’s "2-011-1-12222".

===

Mbinu gani unaweza kutumia?

</mwisho>

Tags technorati:

Guest mabalozi?

Acha reply

It seems fairly common in the political blogging world for a given blog to host a "guest blogger". When I’m in political blog land I must be wearing a different pair of eye glasses because it never occurred to me that "guest blogging" might make sense for a technical blog like mine. That is, mpaka mimi kusoma makala hii na Khipple Kanwal zaidi ya saa Juu ya SharePoint Buzz- Januari 2008.

Kufikiri juu yake, Naamini kuna inaweza kuwa mengi ya watu huko nje katika nchi SharePoint kwamba kuwa na kujikuna kuweka pamoja makala, mfupi au mrefu, kiufundi au biashara zaidi oriented, nk, but don’t run their own blog for all the usual reasons. If you’re one of those people, I’d be happy to host it. You can reach me via email or leave a comment. I haven’t thought through any kind of guidelines, lakini nadhani ningependa wanataka kuwa ni karibu oriented SharePoint, lakini mimi pia kama kutupa katika baadhi ya uchunguzi binafsi kuhusu kushauriana sasa na kisha. I’m also trying to publish a "Jumapili Mapenzi" kila wiki na mimi nina amefungwa kwa kukimbia nje ya mawazo kwa ajili ya kwamba.

Kama wewe ni mwanablogu wa mara kwa mara tayari lakini angependa majaribio na mabalozi mgeni, Mimi dhahiri wazi kwamba pia, either as a host or a guest 🙂

</mwisho>

Tags technorati:

Ufumbuzi wa Kushindwa BDC ADF Import: “makosa yafuatayo ilitokea:”

Acha reply

Mimi mara kwa mara nyingine tena kuandika BDC files ADF kwa mkono (so that I can build up my "get off my lawn!" Mimi) na kugonga kosa hili lovely:

picha

"Application definition import failed. makosa yafuatayo ilitokea:"

Kama unaweza kuona, kuna makosa, lakini … si kwenda kuwaambia mimi ni nini.

Katika kesi yangu, the issue turned out that I had started off with a functional ADF for a different project that connected to a database and executed a SQL query against a view. In this new project, I am calling a method on a web service. I had stripped out the DB specific stuff and added my web service stuff, but failed to update the <LobSystem>’s Type attribute. I switched it to "WebService" and I happily moved on to newer and more exciting import errors, which were handled in due course.

Here is the wrong LobSystem:

<LobSystem
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation=http://schemas.microsoft.com/office/2006/03/BusinessDataCatalogBDCMetadata.xsd
Type="Database"
Version="1.0.0.0" Name="xyzzy"
xmlns="http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog">

This is correct:

<LobSystem
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation=http://schemas.microsoft.com/office/2006/03/BusinessDataCatalogBDCMetadata.xsd
Type="WebService"
Version="1.0.0.0" Name="xyzzy"
xmlns="http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog">

</mwisho>

Tags technorati:

BDC Inaonekana Badala ya faida kwa ajili ya lookups

1 Kujibu

UPDATE: Hii MSDN posting ina baadhi ya uchunguzi ya kuvutia kutoka JXJ msingi wake, hasa hasi, uzoefu kwenda chini njia hii: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2623565&SiteID=1

We have a business scenario where we need to link two documents libraries via a common "document ID" shamba.

We often use a lookup column to implements links like this. There are several drawbacks to lookup columns, tatu ambayo ni:

  1. Only one column from the lookup lookup library can be linked.
  2. Utendaji: The source library could contain hundreds of entries. That’s too many entries in the lookup.
  3. Kutafuta: There is no integrated search. I don’t mean in the MOSS sense of search, lakini hakuna njia ya kutafuta / kuchuja na nguzo nyingi kutoka maktaba hati chanzo na Machapisho kiungo unataka.

Yanayoambatana na BDC, we can use a "business data" column type and it provides a superior search and even allows multiple columns of data to appear in list views.

Nimepata baadhi ya mafanikio ya awali na mbinu hii na mpango wa kuandika zaidi kuhusu hilo.

Kama umefanya kazi hii kabla ya angle na kuwa na maoni yoyote, tafadhali kushiriki!

</mwisho>

Tags technorati:

Ufumbuzi wa Hitilafu BDC Import: “Haikuweza kupakia Aina ilivyoelezwa na TypeName TypeDescriptor ya …”

4 majibu

Nimekuwa kazi na leo BDC, coding ADF files by hand and generating myself some errors. One such error:

Maombi ufafanuzi kuagiza wameshindwa. makosa yafuatayo ilitokea: Haikuweza kupakia Aina ilivyoelezwa na TypeName TypeDescriptor ya. Parameter jina: Hitilafu typeName lilipatikana katika au kabla tu Line: '35’ na Msimamo: ’20’.

MOSS kuonyeshwa kosa hili wakati nilijaribu kuagiza ADF XML faili.

Mimi utafiti Internets na kukuta kwamba nilikuwa referencing mfano LOB jina (kutoka <LobSystemInstance>) katika wangu <TypeDescriptor> nodi wakati mimi wanapaswa inatazamwa jina LOB yenyewe (kutoka <LobSystem>).

Vibaya:

<TypeDescriptor TypeName="Conchango.KeyValue, LOB tukio la" Name="KeyValue">

Kusahihisha:

<TypeDescriptor TypeName="Conchango.KeyValue, LOB Jina" Name="KeyValue">

Matumaini hii moja anaokoa mtu saa moja au mbili ya muda.

</mwisho>

Kujiunga na blog yangu!

Tags technorati: