SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL


Incoming Email 2007 to 2013 Upgrade – Errors occurred processing message

After upgrading from SharePoint 2007 to 2013, I experienced a problem with receiving incoming emails on migrated sites from SP 2007.    ULS logs showed incoming email attempting to process EML files but then quickly failing with “Message ID:” but not the EML file name or alias.   After extensive testing we found that SPSite objects were “locked” for exceeding Sandbox Resource Points.   Toggling the “BitFlags” value allowed us to clear the “Resource Exceeded” and allow incoming email to process.

Also, we disabled a few Timer Jobs which calculate Sandbox Resource points (and were re-establishing the SPSite lock).    With both BitFlags cleared to “0” and timer jobs disabled everything ran smoothly.


ULS Failure

02/17/2015 16:46:12.69    OWSTIMER.EXE (0x0C54)    0x1C4C    SharePoint Foundation    E-Mail    6871    Information    The Incoming E-Mail service has completed a batch.  The elapsed time was 00:00:00.  The service processed 2 message(s) in total.  Errors occurred processing 2 message(s): Message ID:  Message ID:   




[AllSites].[dbo].[BitFlags]  Composition

Table   [AllSites]
Column  [BitFlags]

Failed Site have Decimal Value:      12582912
Failed Site have Hexadecimal Value:  0xC00000


                      V_SF_WRITELOCK  0000000000000001    00000000000000000001     no
                       V_SF_READLOCK  0000000000000002    00000000000000000002     no
                 V_SF_FOUNDATIONLOCK  0000000000000004    00000000000000000004     no
                       V_SF_DISKLOCK  0000000000000008    00000000000000000008     no
                         V_SF_BWLOCK  0000000000000010    00000000000000000016     no
                 V_SF_NONPAYMENTLOCK  0000000000000020    00000000000000000032     no
                  V_SF_VIOLATIONLOCK  0000000000000040    00000000000000000064     no
                V_SF_DISKLOCKMSGSENT  0000000000000080    00000000000000000128     no
                  V_SF_BWLOCKMSGSENT  0000000000000100    00000000000000000256     no
                V_SF_USERLOCKMSGSENT  0000000000000200    00000000000000000512     no
                V_SF_DISKWARNINGSENT  0000000000000400    00000000000000001024     no
                  V_SF_BWWARNINGSENT  0000000000000800    00000000000000002048     no
                      V_SF_LARGESITE  0000000000001000    00000000000000004096     no
              V_SF_MAYHAVESITEALERTS  0000000000008000    00000000000000032768     no
                   V_SF_TRIMAUDITLOG  0000000000010000    00000000000000065536     no
                   V_SF_READONLYLOCK  0000000000020000    00000000000000131072     no
                     V_SF_PRESCANNED  0000000000040000    00000000000000262144     no
         V_SF_USERACCOUNTRESTRICTION  0000000000080000    00000000000000524288     no
          V_SF_USERSOLUTIONACTIVATED  0000000000100000    00000000000001048576     no
               V_SF_RESOURCEWARNSENT  0000000000200000    00000000000002097152     no
                V_SF_RESOURCEMAXSENT  0000000000400000    00000000000004194304    yes
                V_SF_RESOURCEMAXLOCK  0000000000800000    00000000000008388608    yes

V_SF_HASSITESCOPEDUSERCUSTOMACTIONS  0000000001000000    00000000000016777216     no
  V_SF_UIVERSIONCONFIGURATIONENABLED  0000000002000000    00000000000033554432     no
             V_SF_SHAREBYLINKENABLED  0000000004000000    00000000000067108864     no
   V_SF_USERDEFINEDWORKFLOWSDISABLED  0000000010000000    00000000000268435456     no
   V_SF_HTTPSHOSTHEADERSITEURLSCHEME  0000000020000000    00000000000536870912     no
                         V_SF_UNUSED  0000000040000000    00000000001073741824     no
            V_SF_SHAREBYEMAILENABLED  0000000080000000    00000000002147483648     no


Disabled Timer Jobs

  • Solution Daily Resource Usage Update
  • Solution Resource Usage Log Processing
  • Solution Resource Usage Update

NOTE – All 3 timer job definitions above repeat per web application.   In our case, we disabled 6 = 3 jobs X 2 web apps.


How to point to a custom 404 error Web page

Recently I was working on a custom 404 page with JavaScript logic for retiring an old SharePoint farm.   Replacing the “oldportal” DNS name with “newportal” helped avoid any end user 404 message by automatically handling all redirects.   Microsoft has a great KB article with implementation steps.   However, I had two important changes and wanted to blog about it in case this might help others.

  1. Custom JavaScript redirect logic.   A simple replace statement helps change “oldportal” to “newportal” and seamlessly transition user traffic to the new system.
  2. PowerShell instead of Visual Studio EXE.   Not everyone has Visual Studio or the developer skills needed for compiling a command line EXE.   PowerShell is a simple text command you can run on MOSS2007/SP2010/SP2013 because it references the “Microsoft.SharePoint” assembly and works on older SharePoint server versions.




PowerShell Code – apply web application setting


HTML Code – Custom404.htm

Drag and drop .XML files to Excel 2007

Working with SharePoint daily I see a great deal of XML data.   System configuration, user data, feature definition, list schema, usage, etc.     SharePoint is a product that lives and breathes in XML format for nearly everything.

I personally find Excel 2007 very handy here.

If you didn’t know it is possible to drag a plain XML file onto a blank workbook and follow the Excel 2007 defaults to view in a grid layout (sample below).   From there it’s …

  1. Easier to read
  2. Simple to filter and sort
  3. Possible to create PivotTables or Charts to identify patterns

Try it out!    Please leave a comment of any XML tricks you find helpful.    Anybody work a lot with XML in SQL 2005 or InfoPath forms?






Import XML data (Excel – Import XML as Table)



Event Error 5553 – failure trying to synch site”??” for ContentDB “??” WebApp “??”. Exception message was Cannot insert duplicate key row in object ‘dbo.UserMemberships’ with unique index

I ran into this problem this week after doing several site collection moves.     The resolution is simple, effective, and only take a few minutes.

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲