﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Helpful Things</title>
    <description>A general blog for helpful things</description>
    <link>http://www.nitiative.com/portal/Home/tabid/36/BlogId/1/Default.aspx</link>
    <language>en-US</language>
    <webMaster>admin@nitiative.com</webMaster>
    <pubDate>Sun, 20 May 2012 17:00:28 GMT</pubDate>
    <lastBuildDate>Sun, 20 May 2012 17:00:28 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.5.1.19887</generator>
    <item>
      <title>Amazon AWS (EC2/VPC) Network Connectivity/Latency Issues</title>
      <description>&lt;p&gt; Another day, another nugget - this was too was so obscure I had to share. We recently migrated to use Amazon's AWS and EC2 (VPC) for a great deal of our infrastructure. Overall, fantastic - we can respond and build complete environments in hours. However, we started to see random network connectivity and latency issues with certain machines - they would be available for a couple hours at a time and then completely stop responding to *ANY* network requests. The only way to recover was to reboot the instance and start over...&lt;/p&gt;&lt;a href=http://www.nitiative.com/portal/Home/tabid/36/EntryId/19/Amazon-AWS-EC2-VPC-Network-Connectivity-Latency-Issues.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/19/Amazon-AWS-EC2-VPC-Network-Connectivity-Latency-Issues.aspx</link>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/19/Amazon-AWS-EC2-VPC-Network-Connectivity-Latency-Issues.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/19/Amazon-AWS-EC2-VPC-Network-Connectivity-Latency-Issues.aspx</guid>
      <pubDate>Thu, 02 Jun 2011 20:29:00 GMT</pubDate>
      <slash:comments>2</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=19</trackback:ping>
    </item>
    <item>
      <title>IIS7 Web Setup / Install on 64-bit OS Trickery</title>
      <description>&lt;p&gt;Another offering of random web deployment goodness...If you have been developing web applications for some time and turn the key to install the solution on a 64-bit system, in particular one hosted on a Windows 2008 solution, you may run into any one of the following errors (even if you are doing any Any CPU build):...&lt;/p&gt;&lt;a href=http://www.nitiative.com/portal/Home/tabid/36/EntryId/18/IIS7-Web-Setup-Install-on-64-bit-OS-Trickery.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/18/IIS7-Web-Setup-Install-on-64-bit-OS-Trickery.aspx</link>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/18/IIS7-Web-Setup-Install-on-64-bit-OS-Trickery.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/18/IIS7-Web-Setup-Install-on-64-bit-OS-Trickery.aspx</guid>
      <pubDate>Tue, 16 Nov 2010 18:17:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=18</trackback:ping>
    </item>
    <item>
      <title>.NET 2.0 Web Setup Project Install Requiring .NET 4.0</title>
      <description>&lt;p&gt;If you have been successfully deploying web setup projects built in Visual Studio 2008 and migrate to VS2010 to find that your resulting installations require .NET 4, and correctly setting the pre-requisites on the installation doesn't help, this entry is for you...&lt;/p&gt;&lt;a href=http://www.nitiative.com/portal/Home/tabid/36/EntryId/17/-NET-2-0-Web-Setup-Project-Install-Requiring-NET-4-0.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/17/-NET-2-0-Web-Setup-Project-Install-Requiring-NET-4-0.aspx</link>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/17/-NET-2-0-Web-Setup-Project-Install-Requiring-NET-4-0.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/17/-NET-2-0-Web-Setup-Project-Install-Requiring-NET-4-0.aspx</guid>
      <pubDate>Sat, 22 May 2010 15:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=17</trackback:ping>
    </item>
    <item>
      <title>Visual Studio "Unrecoverable build error"</title>
      <description>&lt;p&gt; Not too long ago, after uninstalling a trial of a .NET licensing component (that shall remain nameless), I started receiving random errors within Visual Studio 2008.  It wasn't until I received the following error from building a deployment project that a solution became clear...&lt;/p&gt;&lt;a href=http://www.nitiative.com/portal/Home/tabid/36/EntryId/16/Visual-Studio-Unrecoverable-build-error.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/16/Visual-Studio-Unrecoverable-build-error.aspx</link>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/16/Visual-Studio-Unrecoverable-build-error.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/16/Visual-Studio-Unrecoverable-build-error.aspx</guid>
      <pubDate>Tue, 05 May 2009 05:13:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=16</trackback:ping>
    </item>
    <item>
      <title>DotNetNuke and GoDaddy</title>
      <description>&lt;p&gt;****UPDATED FOR USE ON GODADDY 2/2009****&lt;/p&gt;
&lt;p&gt;Not too long ago, I spent FARRRR to much time trying to figure out how to do a manual install of DotNetNuke on my GoDaddy hosting account.  After MUCH pain and frustration, I finally figured it out.  However, for those lucky saps out there who don't want to experience this and simply get something working within 15 minutes, you can find the &lt;a href="http://forums.asp.net/thread/958251.aspx"&gt;solution here&lt;/a&gt; and regurgitated below; I have validated it with the 4.x.x releases as well (and BTW, a "Deluxe" GoDaddy plan at the time of this writing went for around $6/mo):&lt;/p&gt;
&lt;p&gt;First off, you need a &lt;a href="https://www.godaddy.com/gdshop/hosting/shared.asp?se=%2B&amp;ci=260"&gt;GoDaddy hosting account&lt;/a&gt;. You need at &lt;i&gt;least &lt;/i&gt;the "Deluxe Plan" because DNN requires a MS SQL 2000 database, and that is not an option on the "Economy Plan"&lt;br /&gt;
&lt;br /&gt;
Step 1: Get your virtual directory setup&lt;br /&gt;
 &lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Login to your GoDaddy.com account&lt;/li&gt;
    &lt;li&gt;From the top menu, click &lt;strike&gt;My Account&lt;/strike&gt; "Hosting -&gt; My Hosting Account"&lt;/li&gt;
    &lt;li&gt;&lt;strike&gt;On the icon that says "Hosting &amp; Email", click "Web Hosting &amp; Databases" &lt;/strike&gt;&lt;/li&gt;
    &lt;li&gt;You should see a list of your hosted sites, for the site in question, click &lt;strike&gt;"Settings"&lt;/strike&gt; "Manage Account"&lt;/li&gt;
    &lt;li&gt;Expand the "Content" section, and click on the "File Manager" icon&lt;/li&gt;
    &lt;li&gt;On the &lt;strike&gt;right, click "Custom Directory Permissions"&lt;/strike&gt; left in File Manager, click the "Create New Directory" link&lt;/li&gt;
    &lt;li&gt;In the box, pick a name, this will be the location of your DNN site (eg www.mysite/portal, portal being the name you put in the box now). &lt;strike&gt;Click EACH checkbox. &lt;/strike&gt;Write down the folder name you use here (eg "portal"), we'll need this later.&lt;/li&gt;
    &lt;li&gt;Save your settings by clicking "OK"&lt;/li&gt;
    &lt;li&gt;In the directory listing, check the directory we just created, and click the "Permissions" button at the top right.  Select the Read and Write checkboxes&lt;/li&gt;
    &lt;li&gt;Save your settings by clicking "OK"&lt;/li&gt;
    &lt;li&gt;Now lets go back to the &lt;strike&gt;page where it lists your sites (look at step 3 above)&lt;/strike&gt; manage account screen&lt;/li&gt;
    &lt;li&gt;&lt;strike&gt;Click&lt;/strike&gt; Expand "Databases"&lt;/li&gt;
    &lt;li&gt;Select "Sql Server".  &lt;strike&gt;Under&lt;/strike&gt; In the database screen, click "Create New Database", &lt;strike&gt;Create a MS SQL database&lt;/strike&gt;. For username/password I suggest using the same as your GoDaddy login, or just write it down, we'll need this later.&lt;/li&gt;
    &lt;li&gt;Its going to take a while for the new folder to process and be setup, same with the database.&lt;/li&gt;
    &lt;li&gt;The last part here is that after the database has been created and setup, we need both the server and database name. Going back to &lt;strike&gt;where your sites are (again look at step 3)&lt;/strike&gt; the manage account screen, &lt;strike&gt;click on&lt;/strike&gt; expand Databases, click on Sql Server, and you should see a new record showing your new database. From here we need the server name by clicking on the "edit" or pencil icon to the right of the database; this should be the &lt;strike&gt;leftmost column&lt;/strike&gt; "Host Name" and should look something like: whsql-v02.prod.mesa1.secureserver.net (write this down).&lt;/li&gt;
    &lt;li&gt;On this same line, under DB Name, is the database name, should look something like: DB_10421 (write this down)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Step 2: Get DNN &amp; Config&lt;br /&gt;
 &lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;First off, goto &lt;a href="http://www.dotnetnuke.com/"&gt;http://www.dotnetnuke.com/&lt;/a&gt; and register for an account (takes 1 min), then login&lt;/li&gt;
    &lt;li&gt;Now you have access to the &lt;a href="http://www.dotnetnuke.com/Project/About/Downloads/tabid/125/Default.aspx"&gt;download site.&lt;/a&gt;&lt;/li&gt;
    &lt;li&gt;Get the Source Distribution (for this example I got version 3.0.13), and download it to your computer.&lt;/li&gt;
    &lt;li&gt;Unzip the file to some folder.&lt;/li&gt;
    &lt;li&gt;Before we upload, lets modify the web.config file, this should be in your new unzipped folder, or if you have version 3.1.0, then locate a file named release.config and copy this file and rename it as web.config.&lt;/li&gt;
    &lt;li&gt;There is only one line you need to modify, its about the 22nd line and looks like this:  &lt;add value="Server=(local);Database=DotNetNuke;uid=;pwd=;" key="SiteSqlServer"&gt;&lt;/add&gt;&lt;/li&gt;
    &lt;li&gt;For Server, replace "(local)", with the database server name that you wrote in the above steps.&lt;/li&gt;
    &lt;li&gt;For Database, replace DotNetNuke with the database name that you wrote in the above steps&lt;/li&gt;
    &lt;li&gt;For uid &amp; pwd, this is the username and password that you used to create your database, write them here.&lt;/li&gt;
    &lt;li&gt;Your new line should look something like this: &lt;add value="Server=whsql-v02.prod.mesa1.secureserver.net;Database=DB_10421;uid=thekubrix;pwd=mypass;" key="SiteSqlServer"&gt;&lt;/add&gt;&lt;/li&gt;
    &lt;li&gt;OPTIONAL (yet recommended): On the 55th line you'll see:  &lt;customerrors mode="RemoteOnly"&gt;&lt;/customerrors&gt;. If you want to get useful errors, you need to change this parameter to "Off", like this: &lt;customerrors mode="Off"&gt;&lt;/customerrors&gt;&lt;/li&gt;
    &lt;li&gt;Save this file.&lt;br /&gt;
     &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Step 3: Upload DNN to your site&lt;br /&gt;
 &lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Now FTP to your site (don't have a client? try CuteFtp, or search google for a client), your FTP server name/ip is the same as your site, and your login is the same as your GoDaddy login.&lt;/li&gt;
    &lt;li&gt;Locate the virtual folder you created from the first steps above. Copy all the files from your recent download into here.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Step 4: Install&lt;br /&gt;
 &lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Just go to your virtual directory, and the install will start itself, so for example: http://www.mysite.com/portal&lt;/li&gt;
    &lt;li&gt;The setup will begin to run and display its progress and any error messages&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Thats it! Its recommend that you immediately change the password for both the Host and Admin accounts.&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/5/DotNetNuke-and-GoDaddy.aspx</link>
      <category domain="http://www.nitiative.com/portal/home/tabid/36/blogid/10/default.aspx">Software :: DotNetNuke</category>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/5/DotNetNuke-and-GoDaddy.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/5/DotNetNuke-and-GoDaddy.aspx</guid>
      <pubDate>Sat, 28 Feb 2009 04:41:03 GMT</pubDate>
      <slash:comments>8</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=5</trackback:ping>
    </item>
    <item>
      <title>IIS7 Web Setup/Install &amp; Error Status 1603</title>
      <description>&lt;p&gt;So, its been a while since I have had the opportunity to blog, but this one was obscure enough that I had to share a little bit of 'know'.  Recently I built a staging environment for my company to be able to push our applications through typical deployment 'tiers', and decided that Windows Server 2008 and IIS7 would be a jolly challenge for the web environment.  So, off I went installing the minimum amount of information needed in order to deploy our compiled web setup MSIs.&lt;/p&gt;
&lt;p&gt;The time came to install the MSI for the web solution, and the setup simply died with the message &lt;em&gt;'The installer was interrupted before &lt;product&gt; could be installed.  You need to restart the installer to try again&lt;/em&gt;'.  Like a good little instruction follower, I did, to the same result.  Upon inspecting the application log files, this knowledge packed message gets displayed:&lt;/p&gt;
&lt;p&gt;&lt;span lang="EN"&gt;
&lt;p&gt;&lt;em&gt;Windows Installer installed the product. Product Name: &lt;product&gt;. Product Version: &lt;version&gt;. Product Language: 1033. Installation success or error status: 1603.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Long nights and story short, in order to install a web setup project on Windows Server 2008 and IIS 7, you need to install the &lt;em&gt;IIS 6 Metabase Compatibility&lt;/em&gt; role service.&lt;/p&gt;
&lt;p&gt;I hope this serves you as well as it served me.&lt;/p&gt;
&lt;/span&gt;&lt;/p&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/15/IIS7-Web-Setup-Install-Error-Status-1603.aspx</link>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/15/IIS7-Web-Setup-Install-Error-Status-1603.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/15/IIS7-Web-Setup-Install-Error-Status-1603.aspx</guid>
      <pubDate>Thu, 20 Nov 2008 15:58:52 GMT</pubDate>
      <slash:comments>56</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=15</trackback:ping>
    </item>
    <item>
      <title>Escaping XML in C#</title>
      <description>&lt;p&gt;=== UPDATE ===&lt;/p&gt;
&lt;p&gt;Although the solution below is fine and dandy, this one is MUCH better...&lt;/p&gt;
&lt;p&gt;XmlDocument document = new XmlDocument();&lt;br /&gt;
return document.CreateTextNode("YB &lt; U").OuterXml;&lt;/p&gt;
&lt;p&gt;If you want to add the text as the inner text of another XmlNode, simply add the XmlText result from the CreateTextNode(...) via the node's AppendChild(...) method.&lt;/p&gt;
&lt;p&gt;Enjoy.&lt;/p&gt;
&lt;p&gt;=== ORIGINAL ENTRY ===&lt;/p&gt;
&lt;p&gt;Typically, when dealing with text in XML it is best practice to wrap the text secion in a CDATA element to ensure that there will be no issues when dealing with illegal characters.  However, for the times when manually escaping characters in XML is necessary, rather than writing your own escaping helper class, use this one:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn2.microsoft.com/en-us/library/system.security.securityelement.escape(VS.80).aspx"&gt;http://msdn2.microsoft.com/en-us/library/system.security.securityelement.escape(VS.80).aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Best of luck!&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/11/Escaping-XML-in-C.aspx</link>
      <category domain="http://www.nitiative.com/portal/home/tabid/36/blogid/13/default.aspx">Software :: In General</category>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/11/Escaping-XML-in-C.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/11/Escaping-XML-in-C.aspx</guid>
      <pubDate>Thu, 14 Feb 2008 03:29:09 GMT</pubDate>
      <slash:comments>2</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=11</trackback:ping>
    </item>
    <item>
      <title>Team Foundation Server - Deleting a Project</title>
      <description>&lt;p&gt;At some point in time when you are learning to leverage TFS, you will notice the lack of graphical support to remove projects that you no longer wish to have in your repository - sure, you could use the ol' "command line", but why?  I found a great resource from a gentleman by the name of Julien Lavigne, who shared the source to his graphical solution &lt;a href="http://julien.lavigneducadet.com/index.php?2006/08/03/7-user-interface-to-delete-a-tfs-project"&gt;found here&lt;/a&gt;.  I took it one step further and made the gui stretch the way I expected it to during a resize, and created an MSI setup file with credit to Julien that you can download from my 'Downloads' section also &lt;a href="http://www.nitiative.com/portal/Downloads/tabid/53/Default.aspx"&gt;found here&lt;/a&gt;.  After fixing some compile errors, this worked right out of the gate for me and was exactly what I was looking for.&lt;/p&gt;
&lt;p&gt;Cheers.&lt;/p&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/14/Team-Foundation-Server-Deleting-a-Project.aspx</link>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/14/Team-Foundation-Server-Deleting-a-Project.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/14/Team-Foundation-Server-Deleting-a-Project.aspx</guid>
      <pubDate>Tue, 13 Nov 2007 19:57:33 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=14</trackback:ping>
    </item>
    <item>
      <title>SharePoint 2007 - Identity references could not be translated error</title>
      <description>&lt;p&gt;So, if you have ever 'hap-hazardly' renamed a sharepoint 2007 host machine (without preparing sharepoint for the event), you will notice that sharepoint will refuse to work and documentation is 'skinny' to say the least.  Here is what worked for me on a windows 2003 host (mine was in a farm):&lt;/p&gt;
&lt;p&gt;1.  Make sure Windows 2003 SP2 is installed.&lt;br /&gt;
2.  Locate the 'stsadm.exe' file (e.g. &lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;em&gt;&lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;font size="2"&gt;&lt;drive&gt;&lt;/drive&gt;:\program files\common files\Microsoft Shared\Web Server Extensions\12\bin)&lt;/font&gt;&lt;/span&gt;&lt;/em&gt;&lt;/span&gt;&lt;br /&gt;
3.  Open a command window, navigate the the location of the file, and run the following command (obviously changing the
&lt;oldservername&gt;&lt;/oldservername&gt;
appropriate values):&lt;br /&gt;
&lt;em&gt;     &lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;font size="2"&gt;stsadm -o renameserver -oldservername $OLDSERVERNAME
&lt;oldservername&gt;&lt;/oldservername&gt;
-newservername $NEWSERVERNAME&lt;newservername&gt;&lt;/newservername&gt;&lt;/font&gt;&lt;/span&gt;&lt;/em&gt;&lt;br /&gt;
4.  Now, run the following command (obviously changing the appropriate values):&lt;br /&gt;
     &lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;em&gt;&lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;font size="2"&gt;stsadm -o updatefarmcredentials -identitytype configurableid -userlogin $USERLOGIN &lt;domian name=""&gt;&lt;/domian&gt;-password $PASSWORD
&lt;password&gt;&lt;/password&gt;
&lt;br /&gt;
&lt;/font&gt;&lt;/span&gt;&lt;/em&gt;&lt;/span&gt;     4a.  If you receive an &lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;em&gt;&lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;font size="2"&gt;'Invalid parameter'&lt;/font&gt;&lt;/span&gt;&lt;/em&gt;&lt;/span&gt; error, run the following command:&lt;br /&gt;
             &lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;em&gt;&lt;span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;font size="2"&gt;stsadm -o updatefarmcredentials -userlogin $USERLOGIN &lt;domian name=""&gt;&lt;/domian&gt;-password $PASSWORD
&lt;password&gt;&lt;/password&gt;
&lt;/font&gt;&lt;/span&gt;&lt;/em&gt;&lt;/span&gt;&lt;br /&gt;
5.  Run the following command: &lt;br /&gt;
     &lt;em&gt;&lt;font size="1"&gt;IISRESET /NOFORCE&lt;/font&gt;&lt;/em&gt;&lt;br /&gt;
6.  Run the 'Sharepoint Products and Technologies Configuration Wizard', usually found at: Start &gt;&gt; All Programs &gt;&gt; Microsoft Office Server.  Just click next, next, next, finish (don't change anything).&lt;/p&gt;
&lt;p&gt;Hope this helps!&lt;/p&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/13/SharePoint-2007-Identity-references-could-not-be-translated-error.aspx</link>
      <category domain="http://www.nitiative.com/portal/home/tabid/36/blogid/13/default.aspx">Software :: In General</category>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/13/SharePoint-2007-Identity-references-could-not-be-translated-error.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/13/SharePoint-2007-Identity-references-could-not-be-translated-error.aspx</guid>
      <pubDate>Fri, 27 Jul 2007 19:47:23 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=13</trackback:ping>
    </item>
    <item>
      <title>Sheep, Wolves, and Sheep Dogs</title>
      <description>&lt;p&gt;OK, I wasn't going to place anything opinionated on this blog, but I found the following article and thought it deserved at least some daylight...&lt;/p&gt;
&lt;p&gt;This letter was written by Charles Grennel and his comrades, veterans of the Global War On Terror. Grennel is an Army Reservist who spent two years in Iraq and was a principal in putting together the first Iraq elections in January 2005.&lt;/p&gt;
&lt;p&gt;They wrote it to Jill Edwards, student at the University of Washington, who did not want to honor Medal of Honor winner USMC Colonel Greg Boyington.&lt;/p&gt;
&lt;p&gt;Ms. Edwards, other students and faculty do not think those who serve in the U.S. armed services are good role models.&lt;/p&gt;
&lt;p&gt;To: Jill Edwards, Student, University of Washington&lt;/p&gt;
&lt;p&gt;Sheep, Wolves, and Sheepdogs&lt;/p&gt;
&lt;p&gt;Miss Edwards, I read of your student activity regarding the proposed memorial to Colonel Greg Boyington, USMC, and a Medal of Honor winner. I suspect you will receive many angry emails from conservative people like me.&lt;/p&gt;
&lt;p&gt;You may be too young to appreciate fully the sacrifices of generations of servicemen and servicewomen on whose shoulders you and your fellow students stand. I forgive you for the untutored ways of youth and your naivete. It may be that you are simply a sheep. There's no dishonor in being a sheep, as long as you know and accept what you are.&lt;/p&gt;
&lt;p&gt;William J. Bennett, in a lecture to the United States Naval Academy November 24, 1997, said "Most of the people in our society are sheep. They are kind, gentle, productive creatures who can only hurt one another by accident. We may well be in the most violent times in history, but violence is still remarkably rare. This is because most citizens are kind, decent people, not capable of hurting each other except by accident or under extreme provocation. They are sheep.&lt;/p&gt;
&lt;p&gt;Then there are the wolves who feed on the sheep without mercy. Do you believe there are wolves out there who will feed on the flock without mercy? You better believe it. There are evil men in this world and they are capable of evil deeds. The moment you forget that, or pretend it is not so, you become a sheep. There is no safety in denial.&lt;/p&gt;
&lt;p&gt;Then there are sheepdogs, and I'm a sheepdog. I live to protect the flock and confront the wolf. If you have no capacity for violence, then you are a healthy productive citizen, a sheep. If you have a capacity for violence and no empathy for your fellow citizens, then you have defined [yourself as] an aggressive sociopath, a wolf. But what if you have a capacity for violence, and a deep love for your fellow citizens? What do you have then? A sheepdog, a warrior, someone who is walking the unsheltered path.&lt;/p&gt;
&lt;p&gt;Someone who can walk into the heart of darkness, into the universal human phobia, and walk out unscathed.&lt;/p&gt;
&lt;p&gt;We know that the sheep live in denial, that is what makes them sheep.&lt;/p&gt;
&lt;p&gt;They do not want to believe that there is evil in the world. They can accept the fact that fires can happen, which is why they want fire extinguishers, fire sprinklers, fire alarms, and fire exits throughout their kids' schools. But many of them are outraged at the idea of putting an armed police officer in their kids' school. Our children are thousands of times more likely to be killed or seriously injured by school violence than fire, but the sheep's only response to the possibility of violence is denial. The idea of someone coming to kill or harm their child is just too hard. So they choose the path of denial.&lt;/p&gt;
&lt;p&gt;The sheep generally do not like the sheepdog. He looks a lot like the wolf. He has fangs and the capacity for violence. The difference, though, is that the sheepdog must not, cannot, and will not ever harm the sheep. Any sheepdog who intentionally harms the lowliest little lamb will be punished and removed. The world cannot work any other way, at least not in a representative democracy or a republic, such as ours. Still, the sheepdog disturbs the sheep. He is a constant reminder that there are wolves in the land.&lt;/p&gt;
&lt;p&gt;They would prefer that he didn't tell them where to go, or give them traffic tickets, or stand at the ready in our airports, in camouflage fatigues, holding an M-16. The sheep would much rather have the sheepdog cash in his fangs, spray paint himself white, and go Baa. Until the wolf shows up. Then the entire flock tries desperately to hide behind one lonely sheepdog.&lt;/p&gt;
&lt;p&gt;The students, the victims, at Columbine High School were big, tough high school students, and under ordinary circumstances would not have had the time of day for a police officer. They were not bad kids; they just had nothing to say to a cop. When the school was under attack, however, and SWAT teams were clearing the rooms and hallways, the officers had to physically peel those clinging, sobbing kids off of them.&lt;/p&gt;
&lt;p&gt;This is how the little lambs feel about their sheepdog, when the wolf is at the door. Look at what happened after September 11, 2001, when the wolf pounded hard on the door. Remember how America, more than ever before, felt differently about their law enforcement officers and military personnel? Understand that there is nothing morally superior about being a sheepdog; it is just what you choose to be.&lt;/p&gt;
&lt;p&gt;Also understand that a sheepdog is a funny critter. He is always sniffing around out on the perimeter, checking the breeze, barking at things that go bump in the night, and yearning for a righteous battle. That is, the young sheepdogs yearn for a righteous battle. The old sheepdogs are a little older and wiser, but they move to the sound of the guns when needed, right along with the young ones.&lt;/p&gt;
&lt;p&gt;Here is how the sheep and the sheepdog think differently. The sheep pretend the wolf will never come, but the sheepdog lives for that day.&lt;/p&gt;
&lt;p&gt;After the attacks on September 11, 2001, most of the sheep, that is, most citizens in America, said "Thank God I wasn't on one of those planes." The sheepdogs, the warriors, said "Dear God, I wish I could have been on one of those planes. Maybe I could have made a difference." You want to be able to make a difference. There is nothing morally superior about the sheepdog, the warrior, but he does have one real advantage. Only one. And that is that he is able to survive and thrive in an environment that would destroy 98 percent of the population.&lt;/p&gt;
&lt;p&gt;Research was conducted a few years ago with individuals convicted of violent crimes. These cons were in prison for serious, predatory crimes of violence: assaults, murders, and killing law enforcement officers. The vast majority said they specifically targeted victims by body language:&lt;/p&gt;
&lt;p&gt;Slumped walk, passive behavior, and lack of awareness. They chose their victims like big cats do in Africa, when they select one out of the herd that is least able to protect itself.&lt;/p&gt;
&lt;p&gt;Some people may be destined to be sheep, and others might be genetically primed to be wolves or sheepdogs. But I believe that most people can choose which one they want to be, and I'm proud to say that more and more Americans are choosing to become sheepdogs.&lt;/p&gt;
&lt;p&gt;Seven months after the attack on September 11, 2001, Todd Beamer was honored in his hometown of Cranbury, New Jersey. Todd, as you recall, was the man on Flight 93 over Pennsylvania who called on his cell phone to alert an operator from United Airlines about the hijacking. When they learned of the other three passenger planes that had been used as weapons, Todd and the other passengers confronted the terrorist hijackers. In one hour, a transformation occurred among the passengers - athletes, business people, and parents - from sheep to sheepdogs - and together they fought the wolves, ultimately saving an unknown number of lives on the ground.&lt;/p&gt;
&lt;p&gt;Edmund Burke said "There is no safety for honest men except by believing all possible evil of evil men." Here is the point I want to emphasize, especially to the thousands of police officers and soldiers I speak to each year. In nature, the sheep, real sheep, are born as sheep. Sheepdogs are born that way, and so are wolves. They don't have a choice.&lt;/p&gt;
&lt;p&gt;But you are not a critter. As a human being, you can be whatever you want to be. It is a conscious, moral decision. If you want to be a sheep, then you can be a sheep - and that is okay, but you must understand the price you pay. When the wolf comes, you and your loved ones are going to die, if there is not a sheepdog there to protect you.&lt;/p&gt;
&lt;p&gt;If you want to be a wolf, you can be one, but the sheepdogs are going to hunt you down, and you will never have rest, safety, trust, or love. But if you want to be a sheepdog and walk the warrior's path, then you must make a conscious and moral decision every day to dedicate, equip, and prepare yourself to thrive in that toxic, corrosive moment when the wolf comes knocking at the door.&lt;/p&gt;
&lt;p&gt;This business of being a sheep or a sheepdog is not a yes/no dichotomy.&lt;/p&gt;
&lt;p&gt;It is not an all-or-nothing, either-or choice. It is a matter of degrees, a continuum. On one end is an abject, head-in-the-sand-sheep, and on the other end is the ultimate warrior. Few people exist completely on one end or the other. Most of us live somewhere in between.&lt;/p&gt;
&lt;p&gt;Since 9/11, almost everyone in America took a step up that continuum, away from denial. The sheep took a few steps toward accepting and appreciating their warriors, and the warriors started taking their job more seriously.&lt;/p&gt;
&lt;p&gt;Its OK to be a sheep, but do not kick the sheepdog. Indeed, the sheepdog may just run a little harder, strive to protect a little better, and be fully prepared to pay an ultimate price in battle and spirit with the sheep moving from "baa" to "thanks."&lt;/p&gt;
&lt;p&gt;We do not call for gifts or freedoms beyond our lot. We just need a small pat on the head, a smile, and a thank you, to fill the emotional tank which is drained protecting the sheep. And, when our number is called by The Almighty, and day retreats into night, a small prayer before the heavens just may be in order to say thanks for letting you continue to be a sheep. And be grateful for the millions of American sheepdogs who permit you the freedom to express even bad ideas.&lt;/p&gt;
&lt;p&gt;Charles Grennel&lt;/p&gt;</description>
      <link>http://www.nitiative.com/portal/Home/tabid/36/EntryId/12/Sheep-Wolves-and-Sheep-Dogs.aspx</link>
      <category domain="http://www.nitiative.com/portal/home/tabid/36/blogid/14/default.aspx">General :: Opinion</category>
      <author>blogs@nitiative.com</author>
      <comments>http://www.nitiative.com/portal/Home/tabid/36/EntryId/12/Sheep-Wolves-and-Sheep-Dogs.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.nitiative.com/portal/Home/tabid/36/EntryId/12/Sheep-Wolves-and-Sheep-Dogs.aspx</guid>
      <pubDate>Tue, 24 Jul 2007 20:41:09 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.nitiative.com/portal/DesktopModules/Blog/Trackback.aspx?id=12</trackback:ping>
    </item>
  </channel>
</rss>
