kategorie Argief: Uncategorized

SharePoint Best Practices Konferensie, “Beste praktyke,” en die olifant in die kamer.

I was lucky to attend and present at last week’s SharePoint Best Practices conference. I’m still new to the whole speaking "thing" en, eerlik, I was a bit nervous for the first half while I sweated out waiting to speak myself. That sort of nervous feeling made it a little hard for me to pay attention to the presenters (nie dat ek dit geïgnoreer). In plaas daarvan, Ek gefokus op die deelnemers 'n bietjie meer.

Conferences always set my mind racing and there was a lot take in at this one. This conference was excellent. I think it was unusual in several ways. It wasn’t a heavy developer conference. There were certainly dev parts to it, maar ek dink dit was ten minste 60% gefokus op die nie-dev kwessies, maybe as high as 80%. I think that speaks to the evolving nature of the SharePoint market. Companies are implementing SharePoint in a variety of ways and they are looking for guidance on how to do it right. And not just guidance on how to create features/solutions (wat nou, is baie goed gevestigde).

I believe the conference was tremendously valuable to most everyone that attended and I know that the organizers plan to do the conference again early next year.

Noudat dit gesê is, I believe there was a missed opportunity which I hope the next conference addresses. I say it’s a missed opportunity, but that’s not a bad thing. Discovering a community need is in and of itself a good thing. The conference discussed a number of best practices in a variety of areas such as governance, opleiding, vereistes byeenkoms, soek, ontwikkeling, inligting argitektuur, ens.. I think that the missed opportunity has to do with the "green field" aannames onderliggend aan baie van die beste praktyke.

Wanneer ons praat oor 'n groen veld, we mean that SharePoint hasn’t gone into production and we’re starting with a clean slate. This is ideal because you can start straight away using best practices for defining and managing governance, inligting argitektuur, ens.. Egter … wat gebeur as jy reeds in die produksie met 'n paar duisend gebruikers (or 10’s of thousands) en julle het nie die beste praktyke aan die begin? I’ve seen companies with … Ahem … 'n baie vreemd information architecture baked into their environment. I don’t think that this conference provided much guidance for organizations with that kind of problem (en ek bedoel nie net IA, maar bestuur, soek, baie ander gebiede). Natuurlik, weet jy het 'n probleem is 'n groot deel van die oplossing en dit is baie waardevol.

I think that the online SharePoint community hasn’t done much to address this either. I know I have not. It’s a very hard problem to solve at many levels. Technically it’s hard. Budget-wise it’s hard. Culturally, it’s hard. Egter, it’s probably a bigger real world problem than most. Since the conference ended, I’ve been thinking about these kinds of problems and how one would solve them. There has to be a better answer than, "Verwyder en weer" en die gemeenskap moet dit hoof te bied.

I think that this a great opportunity for the blogging community and experienced thought leaders to lay out some guidance on how to repair their environments. I think there’s a small but non-zero risk that SharePoint could end up with a bad and enduring reputation as a result of poorly architected implementations that fail due to poor governance, IA, ens..

</einde>

Skryf in op my blog.

Technorati Tags:

SharePoint Tabellen Online Seminaar

My online vriend, Mark Miller oor en End User SharePoint (www.endusersharepoint.com) die bestuur van 'n gratis een uur seminaar geteiken, soos hy nie altyd, at the SharePoint End User community. It takes place at 1pm EDT. Details are here: http://www.endusersharepoint.com/?p=785

Ek het gaan sit op een van sy aanlyn-seminaar verlede maand en dit was nogal goed gedoen en as jy belangstel in 'n paar baie praktiese inligting oor dashboards in SharePoint, Ek is seker dit is die moeite werd 1 uur belegging.

</einde>

Skryf in op my blog.

Technorati Tags: ,

Die FBA en SQL Server: 'N Love Story

My colleague has been working on a web part in an FBA environment. Among other things, the web part pulls some data from SQL server. The grand plan for this project dictates that a DBA configures data level security in SQL (in teenstelling met die inbedding van 'n gebruiker-ID in 'n SQL-navraag of 'n ander benadering).

The problem is that SQL server doesn’t know anything about our FBA environment so it can’t trust us. We solved this problem by, vir 'n gebrek van 'n beter woord, manually impersonating an AD user so that we could connect to SQL such that SQL data level security works.

Selfs al FBA is 'n ASP.NET-funksie, ons die SharePoint Nasie mense geleer het om die verskillende soekenjins dat as jy bevraagteken vir FBA, you must mean you want know how to configure FBA in SharePoint. I failed to find find any information on how to enable an FBA oriented ASP.NET application to communicate with SQL in the way we needed.

In die loop van die ondersoek, ons weer lees hierdie artikel: ASP.NET imiteren

Meer navorsing gelei het tot hierdie codproject artikel: http://www.codeproject.com/KB/cs/cpimpersonation1.aspx

Wat gehelp het om ons skryf ons kode, which I’ve included below. It’s not the most elegant stuff, maar dit het gewerk. I hope you find it helpful.

Hier is die kode wat vir ons gewerk het:

beskerm nietig btnSearchCarrier_Click(voorwerp sender, EventArgs e)
 {
 probeer
 {
 ImpersonateUser IE = nuwe ImpersonateUser();
 // ALLE: Plaas geloofsbriewe
 ("Domain Name", "Gebruikersnaam", "Password");

//
 KODE
//

 iU.Undo();
 }
 vang (Uitsondering ex)
 {

 }
 }

// Die gebruik van imiteren klas soos hieronder vermeld.

openbare klas ImpersonateUser
 {
 [DllImport("Advapi32.dll", SetLastError = waar)]
 openbare statiese eksterne Bool LogonUser(
 String lpszUsername,
 String lpszDomain,
 String lpszPassword,
 int dwLogonType,
 int dwLogonProvider,
 ref IntPtr phToken);

 [DllImport("Kernel32.dll", Charset = CharSet.Auto)]
 private eksterne statiese Bool Close Handle(IntPtr hanteer);

 private statiese IntPtr tokenHandle = nuwe IntPtr(0);
 private statiese WindowsImpersonationContext impersonatedUser;

 // As jy hierdie kode insluit in 'n DLL, seker wees om dit te eis dat
 // lopies met FullTrust.
 [PermissionSetAttribute(SecurityAction.Demand, Noem = "FullTrust")]
 openbare nietig voorhou(string domein, string gebruikersnaam, string wagwoord)
 {
 probeer
 {

 // Gebruik die onbeheerde LogonUser funksie te kry die gebruiker teken vir
 // die gespesifiseerde gebruiker, domein, en wagwoord.
 konst int LOGON32_PROVIDER_DEFAULT = 0;

 // Aparte slaag van hierdie parameter veroorsaak LogonUser 'n primêre teken te skep.
 konst int LOGON32_LOGON_INTERACTIVE = 2;
 tokenHandle = IntPtr.Zero;

 // Stap -1 Bel LogonUser 'n handvatsel te verkry tot 'n toegang teken.
 die Bool returnValue = LogonUser(
 gebruikersnaam,
 Domeinnaam,
 wagwoord,
 LOGON32_LOGON_INTERACTIVE,
 LOGON32_PROVIDER_DEFAULT,
 ref tokenHandle); // tokenHandle - nuwe sekuriteit gebrand

 indien (valse == returnValue)
 {
 int ret = Marshal.GetLastWin32Error();
 Console.WriteLine("LogonUser oproep misluk met foutkode : " +
 reg);
 gooi nuwe System.ComponentModel.Win32Exception(reg);
 }

 // Stap - 2
 WindowsIdentity newId = nuwe WindowsIdentity(tokenHandle);
 // Stap -3
 impersonatedUser = newId.Impersonate();

 }
 vang (Uitsondering ex)
 {
 Console.WriteLine(Msgstr "Uitsondering het voorgekom. " + ex.Message);
 }
 }


 /// <opsomming>
 /// Tops nabootsing
 /// </opsomming>
 openbare nietig Undo()
 {
 impersonatedUser.Undo();
 // Vry om die tekens.
 indien (tokenHandle != IntPtr.Zero)
 Close Handle(tokenHandle);
 }
 }

</einde>

Skryf in op my blog.

Technorati Tags:

Toe te voeg tot die Lore: SSRS my vertel “rsAccessDenied”, Maar … Ek het regtig Het Access

'N Paar weke terug, I was working with my developer colleague on a project involving SQL Server Reporting Services plug-in for MOSS. He was developing a web part that provides a fancy front-end to the report proper (die belangrikste kenmerk van 'n slim lookup op 'n parameter met 'n paar duisend soekbare waardes agter dit).

Dit was groot werk in die omgewing nie, maar in die gebruiker aanvaarding toets (UAT) omgewing, it wouldn’t work. Firing up the debugger, ons sal sien uitsondering besonderhede soos hierdie:

Die regte aan gebruikers 'UAT_domain mosssvc' onvoldoende is vir die uitvoering van hierdie aksie.(rsAccessDenied).

As jy 'n live soektog op die bogenoemde fout, you find it’s quite common. Scarily common. The worst kind of common because it has many different potential root causes and everyone’s suggested solution "feels" reg. We probably tried them all.

In ons geval, the problem was that we had done a backup/restore of DEV to UAT. Somewhere in the data, iets was nog verwys na "DEV_domain" (in plaas van die updated "UAT_Domain"). We created a new site, bygevoeg op die web deel en wat ons probleem opgelos.

Hopelik sal iemand 'n uur of twee te red in die ry.

</einde>

Skryf in op my blog.

Technorati Tags:

Minor openbare aankondiging: Windows Live security en Ruimte Eienaars Kontak met

Ek kry 'n handvol van die boodskappe van individue via die ingeboude "stuur 'n boodskap" funksie Microsoft bied met lewendige ruimtes (huisves ook my blog) elke maand.

Ongeveer een derde van die tyd, those users have secured their live spaces account such that I cannot reply. This is some kind of anti-spam feature I assume.

</einde>

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

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:

Dit is Hoekom het ek hou nie van die gebruik van gereedskap Dag Zero

http://groups.google.com/group/microsoft.public.sharepoint.portalserver.development/browse_thread/thread/41e8cbe4f15e8b4c/76506ea401403e35?#76506ea401403e35

As die instrument dinge doen wat jy nie verstaan ​​nie en dan is dit nie in stap n van 'n onbekende aantal stappe, jy is dood in die water…

</einde>

Technorati Tags:

Event ID 1023: “Windows kan nie laai nie extensible toonbank DLL MSSCNTRS”

UPDATE (04/08/08): I seem to have solved this problem. From the command line, Ek het "C:\windows system32 lodctr / R" soos per 'n inskrywing praat oor Install probleme en dit blyk opgelos het dit vir my.

Ek het wat die afgelope tyd opgemerk, my desktop/server fan never turns off. I know it used to turn off. I took a moment to check it out noticed that the a VMware process was running a consistent 20% utilization on one of the CPU’s. I checked the event log and saw these errors in the application log happening dozens of times per minute:

Windows kan nie laai extensible toonbank DLL UGatherer, die eerste DWORD in data-afdeling is die Windows fout kode.

Windows kan nie laai extensible toonbank DLL UGTHRSVC, die eerste DWORD in data-afdeling is die Windows fout kode.

Windows kan nie laai nie extensible toonbank DLL MSSCNTRS, die eerste DWORD in data-afdeling is die Windows fout kode.

As ek boor in die besonderhede van een van die boodskappe, Ek kry hierdie:

Bron: Perflib

Tipe: Fout

Kategorie: Geen

Event ID 1023

I did some research and there was some indication it could be a permission problem in terms of access to the DLLs in question. I played around with that stuff but could not affect things in a positive way so I gave up on that.

VMware had been nagging me about performing an update for quite some time, so I jotted down the version I had installed (apparently "1.0.1 build 29996") and did the update. This upgraded me to v1.04. Ongelukkig, it did not fix the issue.

I can stop the insane number of messages going to my application log if I shut down a service named "VMware Authorization Service". This prevents me from using the VMware software, so … not such a great option.

The host operating system is Windows XP 64 bietjie.

Ek dink nie dit was nog altyd gebeur, maar ek kan nie onthou dat enige spesifieke gebeurtenis wat kan dit daartoe gelei het.

Dit is waarom ek haat rekenaars.

</einde>

Technorati Tags:

Discussion: Toepassing van Beste Praktyke nakoming in 'n nie-triviale mos Omgewing

'N mede, "Mark", het begin met 'n potensieel interessante nuusgroep bespreking fokus op "die stigting van 'n uitstekende SharePoint Bestuur van die begin af" vir 'n 35,000 gebruiker omgewing.

Die gesprek is hier: http://groups.google.com/group/microsoft.public.sharepoint.portalserver/browse_thread/thread/6d9a738d981af772/1c390b15c5407db6?#1c390b15c5407db6

Pop op meer as en dra!

</einde>