Day one bug report

First up, a big thanks to MS for making a preview release of SP2016 available for us on-prem type people...

Secondly, was't sure if I should be bug-reporting here or on the SP UserVoice forums, though the later seems more oriented around feature requests, than bugs.  So yell at me if this is the wrong place :)

My environment:

SP VM: 2xCPU, 10Gig RAM, 60Gig HD, Win2012R2 (patched up to yesterday, and .Net 4.5.2 pre-installed)
SQL VM: 2xCPU, 8Gig RAM, multiple HDs (splitting app, data, log, backup), Win2012R2 (patched up to yesterday, and .Net 4.5.2 pre-installed), SQL2014Dev SP1 CU1
Note: we're behind an authenticating proxy for ALL internet access, but I have a workaround that allows me to make unauthenticated requests, but I must have a proxy configured (I set it in IE for all accounts and using NETSH WINHTTP SET PROXY for the underlying system)
Note2: I'm being a bit naughty and used the same FarmAdmin account for everything.  Until scripted install/configure (<cough>autospinstaller<cough>) catches up, setting up accounts (and DB names) is a pain... :)

Install process: Essentially a next, next (single server), next and I ran the Wizard to set up the services.

Things I hit (in no particular order).

  1. Application Event Log:
    SharePoint Foundation - 6398 - Timer
    The Execute method of job definition Microsoft.SharePoint.Administration.SPAppStateQueryJobDefinition (ID a4b6e489-f9d3-4061-9d8e-4d60b99d51cf) threw an exception. More information is included below.
    Sorry, we can't seem to connect to the SharePoint Store. Try again in a bit.. (Correlation=9da0279d-5fd0-b054-6c29-3eb59ec6febd)

    This was before I had configured the proxy on the FarmAdmin account and I haven't seen it since, so "fixed", but is possibly a pain for installs that will never have internet access. If you don't install the App Management Service, will it still try to connect to MS?
  2. Application Event Log:
    SharePoint Foundation - 6398 - Timer
    The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 68ae63eb-8946-41d7-989b-b16444e4ff63) threw an exception. More information is included below
    Unexpected exception in FeedCacheService.BulkLMTUpdate: Region not found... (Correlation=649d279d-cf5c-b054-6c29-3bf69b8f1e9b)

    This was before I had attempted to configured the User Profile Service, but after I've configured it I still get:

    Application Event Log:
    SharePoint Foundation - 6389 - Timer
    The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 68ae63eb-8946-41d7-989b-b16444e4ff63) threw an exception. More information is included below.
    An update conflict has occurred, and you must re-try this action. The object LMTRepopulationJob Name=User Profile Service Application_LMTRepopulationJob was updated by CTSYNZ\SPS16CAPoolD, in the w3wp (7184) process, on machine CTASPS16A01D.  View the tracing log for more information about the conflict.. (Correlation=8aa2279d-8f9f-b054-6c29-3adf7a5fb6e4)

    It appears to be syncing AD accounts OK, only I need to go back to my SP2007 days and configure the LDAP query filters (is it an include filter or an exclude filter?)
  3. Application Event Log:
    SharePoint Foundation - 7043 - Web Controls
    Load control template file /_controltemplates/15/KpiListFormTemplates.ascx failed: Could not load file or assembly 'Microsoft.Office.Excel.WebUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.

    This seems to happen twice on site access (once as IUSR and then again as the authenticated user). But I've also noticed that it happens after a reboot, as IUSR, without any site access.
  4. Application Event Log:
    VSS - 8193 - None
    Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,...).  hr = 0x80070005, Access is denied.
    .
    Operation:
       Initializing Writer
    Context:
       Writer Class Id: {0ff1ce15-0201-0000-0000-000000000000}
       Writer Name: OSearch15 VSS Writer
       Writer Instance Name: OSearch15 Replication Service
       Writer Instance ID: {a36d7eb7-8716-4999-9e04-81d1f50d0230}

    Looks like the user behind the Search Service (in this case the Farm Admin account) doesn't have write access to the VSS Diag registry key.  This was a bug in SP2013 as well.
  5. After creating an Enterprise Search site collection, the first time I hit the search page I got an error:
    Display Error: The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types.
    Template '~sitecollection/_catalogs/masterpage/Display Templates/Search/Control_SearchBox.js' not found or has syntax errors.
    (LoadTemplate: )

    Refreshing the page made the error go away.
  6. Immediately after installing, I noticed the AdminContent DB was reporting "Database is in compatibility range and upgrade is reccomended".  Which is somewhat odd for a fresh install.
    Digging deeper revealed the following possible discrepency:
    MicrosoftOffice.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: 4.0.0.0, Maximum Schema Version: 16.1.237.0

    So I ran the classic:
    psconfig -cmd upgrade -inplace b2b -wait

    Which resolved it.
  7. I had selected "Microsoft SharePoint Insights" to be installed as part of the Wizard, but at the end of the process, got the following error:
    The following errors were encounered while provisioning services:
    The service instance "Microsoft SharePoint Insights" could not be provisioned because of the following error: Authentication information for SPInsights service has not been set yet.
    Correlation ID: ....

    I wasn't prompted for extra credentials for the Insight service and I just assumed that it, like all the other services that are installed by the Wizard, would adopt the single account specified at the start of the Wizard (in my case, the Farm Admin account).

    I went on to notice that in the Services on Server page that the Microsoft SharePoint Insights service was stopped, and the compliance column said it was out-of-compliance, but there was a link to "fix" it.
    Clicking the "fix" (or "start") link just brings up an error, again pointing out that there is no Authentication information for SPInsights.

    There are also repeated events in the Application event log, showing the service trying to start, but having no credentials.

    There doesn't appear to be any UI to create/configure this service, so I'm guessing it's tucked away in STSADM and/or PowerShell...
  8. There are lots of Perflib and PerfNet related errors, but I don't know if they are SP2016 specific.
    They seem to revolve around WmiApRpl
    C:\Windows\system32\wbem\wmiaprpl.dll
  9. Application Event Log:
    SharePoint Foundation - 5586 - Database
    Unknown SQL Exception 15023 occurred. Additional error information from SQL Server is included below.
    User, group, or role 'WSS_Content_Application_Pools' already exists in the current database.

    This might have been from when I ran the stsadm -cmd upgrade
  10. And what SP install wouldn't be completed without at least one DCOM errr:

    System Event Log:
    DistributedCOM - 10016 - None
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
    {A9E69610-B80D-11D0-B9B9-00A0C922E750}
     and APPID
    {A9E69610-B80D-11D0-B9B9-00A0C922E750}
     to the user DAMAIN\FarmAdmin SID (S-1-5-21-XXXXXXX) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    Changing the owernship of the regkey HKEY_CLASSES_ROOT\AppID\{A9E69610-B80D-11D0-B9B9-00A0C922E750}, giving local admins full control, then giving WSS_WPG local lauch of IIS Admin in Component services, should clean that up.
    Nice to see it's not IIS WAMREG for a change.

And that's it for today.  My first look at SP2016.  Looking forward to digging deeper and trying a few more things out. And seeing what classic SP2013 bugs are still there :)

Thanks
Craig

August 26th, 2015 12:54am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics