Arquivo da Categoría: Sen categoría

SharePoint Conference Mellores Prácticas, “Mellores Prácticas,” eo elefante na sala

I was lucky to attend and present at last week’s SharePoint Best Practices conference. I’m still new to the whole speaking "thing" e, francamente, 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 (Non é que eu ignorei). Pola, Eu me concentrei un pouco máis sobre os participantes.

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, pero eu creo que foi, polo menos, 60% foco cuestións non-dev, 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 (que ata agora, foi ben establecida).

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.

Dito isto, 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, formación, levantamento de requisitos, buscar, desenvolvemento, arquitectura da información, etc. I think that the missed opportunity has to do with the "green field" suposicións subxacentes moitas das mellores prácticas.

Cando falamos en campo verde, 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, arquitectura da información, etc. Con todo … o que ocorre cando xa está en produción, con varios miles de usuarios (or 10’s of thousands) e non seguir as mellores prácticas no inicio? I’ve seen companies with … ahem … moi estraño information architecture baked into their environment. I don’t think that this conference provided much guidance for organizations with that kind of problem (e non me refiro só IA, senón de gobernanza, buscar, moitas outras áreas). Por suposto, sabendo que ten un problema é unha gran parte da solución, e iso é moi valioso.

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. Con todo, 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, "uninstall and reinstall" ea comunidade que afrontalo lo na cabeza.

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, etc.

</final>

Rexístrate para o meu blog.

Technorati Tags:

SharePoint Dashboards liña Seminario

O meu amigo en liña, Mark Miller e máis Usuario final SharePoint (www.endusersharepoint.com) está executando unha hora un seminario gratuíto obxectivo, como sempre fai, at the SharePoint End User community. It takes place at 1pm EDT. Details are here: http://www.endusersharepoint.com/?p=785

Eu participei dun seminario en liña do seu último mes e se fixo moi ben e, se vostede está interesado en algunha información moi práctico sobre dashboards en SharePoint, Estou seguro de que paga a pena 1 investimento horas.

</final>

Rexístrate para o meu blog.

Technorati Tags: ,

FBA e SQL Server: Unha Historia de Amor

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 (en oposición a incorporación dun ID de usuario nunha consulta SQL ou algunha outra visión).

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, por falta dunha palabra mellor, manually impersonating an AD user so that we could connect to SQL such that SQL data level security works.

Aínda FBA é unha característica ASP.NET, nós SharePoint Nación persoas teñen ensinado os distintos buscadores que se está consultando a 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.

No curso de investigar este, que re-ler este artigo: ASP.NET representación

Máis investigación nos levou a este artigo codproject: http://www.codeproject.com/KB/cs/cpimpersonation1.aspx

Iso nos axudou a escribir o noso código, which I’ve included below. It’s not the most elegant stuff, but it worked. I hope you find it helpful.

Aquí está o código que funcionou para nós:

protexido baleiro btnSearchCarrier_Click(object sender, EventArgs e)
 {
 intentar
 {
 U = ImpersonateUser novo ImpersonateUser();
 // ALL: Substitúe as credenciais
 ("DomainName", "UserName", "Password");

//
 CODE
//

 iU.Undo();
 }
 incorporarse (Exception ex)
 {

 }
 }

// A través da representación de clase, como mencionado continuación.

público clase ImpersonateUser
 {
 [DllImport("advapi32.dll", SetLastError = certo)]
 público estático externamente bool LogonUser(
 LpszUsername cadea,
 Cordas lpszDomain,
 Cordas lpszPassword,
 int dwLogonType,
 int dwLogonProvider,
 ref IntPtr phToken);

 [DllImport("kernel32.dll", Charset = CharSet.Auto)]
 privado externamente estático bool CloseHandle(IntPtr);

 privado estático IntPtr tokenHandle = novo IntPtr(0);
 privado estático WindowsImpersonationContext impersonatedUser;

 // Se incorporar este código nunha DLL, asegúrese de esixir que
 // carreiras con FullTrust.
 [PermissionSetAttribute(SecurityAction.Demand, Name = "FullTrust")]
 público anular Representar(corda Nome_Domínio, cadea usuario, cadea contrasinal)
 {
 intentar
 {

 // Utilice a función LogonUser xestionado para o token de usuario para
 // o usuario especificado, dominio, e contrasinal.
 const int LOGON32_PROVIDER_DEFAULT = 0;

 // Pasando este parámetro fai que LogonUser para crear un token primario.
 const int LOGON32_LOGON_INTERACTIVE = 2;
 tokenHandle = IntPtr.Zero;

 // Paso -1 Chama LogonUser para obter un identificador para un token de acceso.
 bool returnValue = LogonUser(
 Nome de usuario,
 nome de dominio,
 contrasinal,
 LOGON32_LOGON_INTERACTIVE,
 LOGON32_PROVIDER_DEFAULT,
 Propiedade tokenHandle); // tokenHandle - novo token de seguridade

 se (teito == returnValue)
 {
 int ret = Marshal.GetLastWin32Error();
 Console.WriteLine("LogonUser call failed with error code : " +
 dereito);
 xogar novo System.ComponentModel.Win32Exception(dereito);
 }

 // Paso - 2
 WindowsIdentity NewID = novo WindowsIdentity(tokenHandle);
 // Paso -3
 impersonatedUser = newId.Impersonate();

 }
 incorporarse (Exception ex)
 {
 Console.WriteLine("Exception occurred. " + ex.Message);
 }
 }


 /// <resumo>
 /// Deixa representación
 /// </resumo>
 público anular Desfacer()
 {
 impersonatedUser.Undo();
 // Liberar os tokens.
 se (tokenHandle != IntPtr.Zero)
 CloseHandle(tokenHandle);
 }
 }

</final>

Rexístrate para o meu blog.

Technorati Tags:

Sumándose a Lore: SSRS dime “rsAccessDenied”, Pero … Realmente teño acceso

Algunhas semanas atrás, 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 (A principal característica ser unha busca intelixente en un parámetro con varios miles de valores searchable detrás del).

Iso foi moi bo traballar no ámbito de desenvolvemento, pero a proba de aceptación do usuario (UAT) ambiente, it wouldn’t work. Firing up the debugger, queremos ver detalles de excepción como este:

Os permisos concedidas ao usuario 'UAT_domain mosssvc' son insuficientes para realizar esta operación.(rsAccessDenied).

Se se fai unha busca en directo sobre o erro anterior, 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" dereito. We probably tried them all.

No noso caso, the problem was that we had done a backup/restore of DEV to UAT. Somewhere in the data, something was still referring to "DEV_domain" (instead of the updated "UAT_Domain"). We created a new site, engadida á parte web e que resolveu o noso problema.

Esperemos que isto ha salvar a alguén dunha hora ou dúas para abaixo da liña.

</final>

Rexístrate para o meu blog.

Technorati Tags:

Edital Menor: Windows Live Configuración de Seguridade e entrar en contacto con Propietarios espazo

Eu recibín un puñado de mensaxes de persoas a través do built-in "enviar unha mensaxe" Microsoft ofrece función con espazos vivos (que tamén aloxa o meu blog) todos os meses.

Cerca dun terzo do tempo, those users have secured their live spaces account such that I cannot reply. This is some kind of anti-spam feature I assume.

</final>

Son “Erro descoñecido” Mensaxes realmente mellor que un Stack Trace?

Eu estaba lendo post de Madhur sobre como permitir seguimento de pila exhibe e agora eu estou querendo saber: por que non mostrar sempre un seguimento de pila?

Quen xurdiu con esa regra e por que seguilo?

End users will know something is wrong in either case. At least with a stack trace, poden premer Control-PrintScreen, copiar / pegar en un correo-e e enviá-lo para TI. Isto reduciría claramente o tempo eo esforzo necesarios para resolver o problema.

</final>

Technorati Tags:

É por iso que eu non me gusta de usar ferramentas Cero Day

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

Se a ferramenta está facendo cousas que non entende e, a continuación, el falla no paso n dun número descoñecido de pasos, está morto na auga…

</final>

Technorati Tags:

ID do evento 1023: “Windows non pode cargar extensibles MSSCNTRS DLL do contador”

Actualización (04/08/08): I seem to have solved this problem. From the command line, Eu corrín "c:\Windows system32 lodctr / R" por unha entrada falando sobre problemas InstallShield e que parece ter resolto iso por min.

Teño notado que ultimamente, 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 non pode cargar UGatherer DLL extensible contador, a primeira DWORD na sección de datos é o código de erro de Windows.

Windows non pode cargar UGTHRSVC DLL extensible contador, a primeira DWORD na sección de datos é o código de erro de Windows.

Windows non pode cargar extensibles MSSCNTRS DLL do contador, a primeira DWORD na sección de datos é o código de erro de Windows.

Se eu furar os detalles dunha daquelas mensaxes, Eu teño ese:

Orixe: Perflib

Tipo: Erro

Categoría: Ningún

ID do evento 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 estaba me incomodando sobre como executar unha actualización por un tempo, entón eu anotei a versión que eu tiña instalado (aparentemente "1.0.1 construír 29.996") and did the update. This upgraded me to v1.04. Desafortunadamente, non resolver o problema.

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, así … not such a great option.

O sistema operativo anfitrión é o Windows XP 64 bocado.

Eu non creo que iso sempre pasou, pero eu non me recordo de ningún evento específico que podería levar a el.

É por iso que eu odio ordenadores.

</final>

Technorati Tags:

Foro de debate: Impoñendo prácticas en Compliance Ambiente Moss non-trivial

Un compañeiro, "Mark", has started up a potentially interesting newsgroup discussion focusing on "establishing excellent SharePoint Governance from the start" para unha 35,000 ambiente do usuario.

A discusión é aquí: http://groups.google.com/group/microsoft.public.sharepoint.portalserver/browse_thread/thread/6d9a738d981af772/1c390b15c5407db6?#1c390b15c5407db6

Pop en máis e contribuír!

</final>