So I was starting to see this error after installing a new DotNetNuke 4.6.2 web application.  Here is the order I did things.

 When using .netTiers (2.0, 2.1, or 2.2), on a database that has replication enabled, the following is required to prevent the "Updating Columns with the rowguidcol property is not allowed." exception. 

I found that the default behavior for updating a entity using SQL will try to update the RowGuid colomns, causing bugs for those of us using replication.  I found a fix in part of an email by Taylor Durden (http://community.codesmithtools.com/forums/thread/23074.aspx) that goes like this:

 Add this to the TemplateLib\CommonSqlCode.cs

/// <summary>
        /// Check if a column is a rowguid column for replication
        /// </summary>
        /// <param name="column">DB table column to be checked</param>
        /// <returns>Identity?</returns>
        public bool IsRowGuidColumn(ColumnSchema column)
        {
            if (column.ExtendedProperties["CS_IsRowGuidCol"] != null)
                return (bool)column.ExtendedProperties["CS_IsRowGuidCol"].Value;

            return false;
        }

and change this block in code around line 84 in \DataAccessLayer.SqlClient\StoredProceduresXml.cst

 foreach (ColumnSchema column in cols)
  {
   if ( ! IsIdentityColumn(column) && ! IsComputed(column) && ! IsRowGuidColumn(column) )
    colsUpdatable.Add(column);
    
   if (column.NativeType.ToLower() == "timestamp")
    RowVersion = column;
  }

 And this fixed this issue for me.  I wanted to break this issue out into a seperate thread then Mr. Durden issue, but the credit belongs with him.

 Jason R. Shaver 

 Let me just say that the Quickbooks SDK when used as the 'web service' method or the Quickbooks Web Connector (qbwc), is like hitting yourself in the face with a dead trout.  A large one. 

How it works (in breif) is they have a program on the client's machine that contacts your web service and asks it what work needs to be done, and then you tell a single bit of information you need.  Then it calls in again returning that bit of information and if you return a int < 100 then it will call in again asking for a bit of work that needs to be done. 

The issue with this is that it requires you to build what ends up being a complex finite state machine (FSM).  I have a simple program that integrates items, customers, and invoices with Quickbooks and I have 14 states so far. 

I also can't think of a good way to do the without requiring the web service to use sessions, another risk I wish to avoid.

Anyway, on the good side, this being done this way (the client making the calls to the webservice) means that you don't have to worry about NAT issues or creating SSL connections (SSL is required) or transport security issues, and that is good.  Just requires a mind-set change.  (Last FSM I worked on was a robots project that I really enjoyed).

 This has worked for me on 4 computers running vista ultimate or home premium.

http://mvolo.com/blogs/serverside/archive/2006/12/28/Fix-problems-with-Visual-Studio-F5-debugging-of-ASP.NET-applications-on-IIS7-Vista.aspx