Impresión rápida: System Center Capacity Planner para SharePoint

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

Eu penso doado de usar e rápido modelado nun ambiente de cliente que eu traballei neste verán pasado.

Con certa aprehensión, Eu apertei o botón Aceptar final, e recomendou algo que é moi semellante ao que demos o noso cliente (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, etc), 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:

  • Procurar: Total documents, maybe types of documents, languages.
  • Excel server: how much, a todos?
  • Forms server: how much, a todos?
  • BDC: how much, a todos.

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.

</final>

Solución: System.IO.FileNotFoundException en “SPSite = new SPSite(url)”

Actualización: Poño esta pregunta para MSDN aquí (http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2808543&SiteID=1&mode=1) and Michael Washam of Microsoft responded with a concise answer.

Eu creei un servizo web para actuar como un Fachada BDC-friendly to a SharePoint list. When I used this from my development environment, funcionou moi ben. Cando migrei este para un novo servidor, Eu atopei este erro:

System.IO.FileNotFoundException: A aplicación web en http://localhost/sandbox non puido ser atopada. Comprobe se inseriu a URL correctamente. Se a URL debe estar servindo contido existente, o administrador do sistema pode ter que engadir un novo mapeamento da URL da solicitude á aplicación desexada. en Microsoft.SharePoint.SPSite .. ctor(SPFarm Facenda, Uri requestUri, Booleana contextSite, SPUserToken userToken) en Microsoft.SharePoint.SPSite .. ctor(Cordas requestURL) en Conchango.xyzzy.GetExistingDocument(Cordas miniD, Cordas maxId, Secuencia de filtros título) en C:\Documents and Settings Galicia Os ​​meus documentos Visual Studio 2005 Projects xyzzy BDC_DocReview BDC_DocReview DocReviewFacade.asmx.cs:liña 69

Aquí é a liña 69:

utilización (Lugar SPSite = new SPSite("http://localhost/sandbox"))

Intento varias variacións sobre a URL, ata usar o nome real do servidor, o seu enderezo IP, barra ao final da URL, etc. I always got that error.

Eu soía Google to research it. Lots of people face this issue, ou variacións dela, pero ninguén parecía telo resolto.

Tricksy Moss solicitado un erro tan detallado que non se me ocorreu para comprobar o 12 hive logs. Eventualmente, sobre 24 horas despois meu compañeiro recomenda-me facelo, Eu comproba o 12 rexistro colmea e atopei este:

Unha excepción ocorreu durante o intento de adquirir a facenda local:
System.Security.SecurityException: Acceso ao rexistro solicitado non se admite.
en System.ThrowHelper.ThrowSecurityException(ExceptionResource recurso) en
(String nome, Booleana gravable) en
(String nome) en
() en
() en
(SPFarm& Facenda, Booleana& isJoined)
A Zona da assembly que non foi:  MyComputer

Isto abriu novos camiños de investigación, polo que estaba de volta a Google. Isto levoume a este foro post: http://forums.codecharge.com / posts.php?post_id = 67135. 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 de 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. Con todo, meu compañeiro foi e deu o app conta de identidade do pool acceso total ao SQL.

Así que fixo ese cambio, everything started working.

O que pasou despois é mellor expresada como un haiku poema:

Problemas levantar as mans.
You swing and miss. Try again.
Éxito! But how? ¿Por que?

Ela non quería deixar as cousas só, como que, preferindo dar permiso mínima necesaria (e, probablemente, con un ollo para escribir un post no blog; Eu batía nela co zócalo, muhahahahaha!).

Ela eliminou os permisos sucesivas da súa conta de identidade do pool de aplicacións ata … 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.

Así, para recapitular: we gave the app pool identity full access and then took it away. The web service started working and never stopped working. Bizarre.

Se alguén sabe por que isto debería funcionar, por favor, deixe un comentario.

</final>

Technorati Tags:

Solución (tipo de): Establecer prioridade nunha tarefa Usando o SharePoint Design

Eu teño un escenario de negocios coma este:

  • Un usuario carga un documento a unha biblioteca de documentos.
  • Ela selecciona un tipo de contidos e entra meta datos polo que sexa. Un dos campos de datos de meta é unha bandeira, "Urgent".
  • Isto desencadea un fluxo de traballo do SharePoint Design que, entre outras cousas, uses the "Collect Data from a User" acción.

"Collect Data from a User" crea un elemento nunha lista solicitando a aprobación tarefa para aquel documento.

Eu precisaba crear unha visualización da lista de tarefas que amosa as solicitudes urxentes de aprobación.

Solución: Put the word "URGENT:" into the title of these tasks.

I would have preferred to specify the priority field directly. Con todo, Eu era capaz de facelo por varias razóns:

  1. A recollida de datos acción non ofrece un mecanismo para actualizar calquera outro campo de título (e os campos adicionais para o que quere recadar datos).
  2. The "assign a to do item" acción ten o mesmo problema.
  3. É posible inserir un elemento nunha lista (i.e. introducir un elemento da lista de tarefas directamente) but this not a blocking action. That means that the workflow will not wait for the user to complete that task.

Considerei algunhas enfoques antes (agradecidamente) realizing we could just put "urgent" no título.

  1. Iniciar un fluxo de traballo na lista de tarefas a si mesmo de xeito que, cando unha nova tarefa créase, que dalgún xeito cruzar referencias ao seu documento, que comezou o primeiro fluxo de traballo, pull out the urgent flag value and update priority as needed.
  2. Do something similar with an event receiver. On create of the task, atopar o documento asociado e actualizar prioridade que corresponda.
  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. (Por algunha razón, Eu tiña máis ou menos resolto sobre esta visión antes sabios decide afastarse por un tempo).

Hai unha desvantaxe para a miña solución (ademais do feito evidente de que o texto do título indica urxencia). Since "collect feedback" só acepta nomes de título codificado, I need to use two different collect feedback actions whose only difference is that hard coded title.

Pero, polo menos hai unha solución que non require receptores de eventos ou accións SPD personalizados.

Se alguén xa resolveu isto dun xeito máis intelixente, por favor me aviso.

</final>

Domingo divertido: Mantendo o seu Fillo na punta dos pés

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:

===

Interpretar mal as súas preguntas:

A súa: Que día é hoxe?

Pai: Un día antes do mércores.

S: Non, what day of the month is it?

D: Oh, it’s 4 days after Jan 25.

===

Tickle him and tell him you’ll stop when he stops laughing.

===

Go down stairs to the TV room and announce, "It’s good to be the daddy." Entón, pick him up to get the warm spot on the couch and change the channel to something good, like the Scifi channel.

===

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. Por exemplo, "the knife slipped in his hand, cutting his index finger, killing him instantly." 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, tell him, "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!"

(This reminds me of my favorite Borg joke: "Borger King: We do it our way. Your way is irrelevant." hahaha!)

===

Open a book to page 9 and say, "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 enemy to the town of Squarewood."

===

We drive up to Massachusetts from New Jersey several times a year and it often takes about 5 hours door to door. As we arrive home and pull into the driveway say, "oh, I forgot, we need to make a quick dash to Home Depot."

===

When watching a violent episode in a TV show (such as Heroes), tell your son, "some times, at work, I need to destroy my enemies by burning them alive using the powers of my mind. I don’t like doing it, but you gotta do what you gotta do."

===

When watching bad horror movies (see "It’s good to be the Daddy" arriba), ascribe improbable motives to the evil character. Por exemplo, 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".

===

What tricks do you use?

</final>

Technorati Tags:

Blogging Visitante?

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, ata eu ler este post por Khipple Kanwal sobre a O Mellor do SharePoint zumbido- Xaneiro 2008.

Pensando niso, Creo que podería haber unha chea de xente alí fóra, no SharePoint rexión que ten a coceira para montar un artigo, curto ou longo, negocio técnico ou máis orientada, etc, 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, pero supoño que quero que sexa orientado arredor de SharePoint, pero eu tamén gosto de xogar en algunhas observacións persoais sobre consultoría agora e entón. I’m also trying to publish a "Domingo divertido" Cada semana e eu son obrigado a quedar sen ideas para que.

Se vostede é un blogueiro regular xa, pero quere probar con blogs invitado, Eu sempre estou aberto a iso tamén, either as a host or a guest 🙂

</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:

Solución para BDC ADF Import fallo: “Ocorreu o seguinte erro:”

Eu estaba unha vez máis a elaboración arquivos BDC ADF á man (para que eu poida construír o meu "saia do meu gramos!" Eu) e bateu esta linda erro:

imaxe

"Application definition import failed. Ocorreu o seguinte erro:"

Como se pode ver, hai un erro, pero … non me vai dicir o que é.

No meu caso, 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, pero non puido actualizar o <LobSystem>’s Type attribute. I switched it to "WebService" e eu por sorte mudouse para os erros máis recentes e máis emocionante de importación, que foron tratadas no seu tempo.

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">

</final>

Technorati Tags:

BDC Parece un substituto viable para investigacións

Actualización: Este MSDN post ten algunhas observacións interesantes de JXJ con base na súa, sobre todo negativo, experiencias indo por este camiño: 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" campo.

We often use a lookup column to implements links like this. There are several drawbacks to lookup columns, tres dos cales son:

  1. Only one column from the lookup lookup library can be linked.
  2. Actuación: The source library could contain hundreds of entries. That’s too many entries in the lookup.
  3. Procurar: There is no integrated search. I don’t mean in the MOSS sense of search, pero non hai ningunha forma de buscar / filtrar varias columnas dende a biblioteca do documento de orixe e atopar a ligazón que quere.

Apoiado por 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.

Tiven algún éxito preliminar con esta visión e pretendo escribir máis sobre el.

Se xa traballou este ángulo antes e ten algún comentario, por favor, comparta!

</final>

Technorati Tags:

Solución para BDC Erro de Importación: “Non se puido cargar o tipo descrito por NomeTipo de TypeDescriptor …”

Eu estou traballando con BDC hoxe, coding ADF files by hand and generating myself some errors. One such error:

Importación de definición de aplicación fallou. Ocorreu o seguinte erro: Non se puido cargar o tipo descrito por NomeTipo de TypeDescriptor. O nome do parámetro: typeName erro se atopou en ou antes de Liña: '35’ e posición: ’20’.

Moss aparece este erro cando intento descargar o arquivo XML ADF.

Eu searched as Internets e penso que eu estaba facendo referencia ao nome da instancia LOB (do <LobSystemInstance>) o meu <TypeDescriptor> nó cando eu debería ter mencionado o nome propio LOB (a partir de <LobSystem>).

Mal:

<TypeDescriptor TypeName="Conchango.KeyValue, LOB Nome da Instancia" Name="KeyValue">

Corrixa:

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

Espero que isto se salva alguén unha ou dúas horas de tempo.

</final>

Rexístrate para o meu blog!

Technorati Tags: