Skip to main content

A problem has occured: SharePoint / TRIM integration

I came across this problem when configuring the TRIM TCSI Components for SharePoint 2007. Specifically, the project was installing the "TCSI SharePoint 2007 Components 2.1 SP3.exe" components.

Installation of the components went OK. We were specifying the TRIM Context server during the MSI install, but with no ICE server (left blank). Once the MSI install was complete, and the Site Collection features were activated, the usual TcsiSettings.aspx link appears under the site collections Settings.aspx page.

However, once clicking on the page, the following two errors were displayed (on /_layouts/TcsiSettings.aspx).

A problem has occured: An unexpected and unknown problem has occurred in the Unique World Software framework exception handling class. No details are available for this problem. Problem ID: 1001003001


and

A problem has occured: An unexpected and unknown problem has occurred in the TCSI CommonServices. No details are available for this problem Problem ID: 1100004001


Looking at the Security Event Log on the SharePoint server, there are numerous failed Security audit events. All relating to an account local to the SharePoint server - UWSPrivilegedUser.

Sure enough, when looking at the account under the Local Users section on the SharePoint server, it is indeed locked out. I tried unlocking it and re-loaded the TcsiSettings.aspx in a web browser. The same two errors above were displayed, and looking at the Local User properties for UWSPrivilegedUser, the account was again locked.

The following registry keys seem to contain the username and password of the account being used to perform certain internal functions:

HKEY_LOCAL_MACHINE\SOFTWARE\Unique World Software\Framework

with three String Values:
  • Encrypted
  • PrivilegedAccount
  • Version
I attempted to re-install the TRIM SharePoint components by removing them first (from Add/Remove programs). While the registry entries mentioned above were removed, as well as the local UWSPrivilegedUser account, re-installing via the MSI came up with the same results.

I eventually found a solution. After reading the documentation provided by HP, I found there's a setting you can give the installer to tell it what the minimum and maximum size of the password for the UWSPrivilegedAccount.

The setting is a registry String value, under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Unique World Software\Framework

The String value is named "PasswordLength", and specifies the minimum and maximum size by entering two integer values, with a dot in between, e.g. "8.8" (without quotes).

By specifying the minimum and maximum password lenth values as 8 and 8 respectively, and removing and adding the components again, the Security event log no longer contained any Audit failure messages against the UWSPrivilegedAccount user, nor did any errors display on the /_layouts/TcsiSettings.aspx page.

Comments

Popular posts from this blog

Thoughts, shortcomings, gotchas on SPFx Dynamic Data capabilities

It's the festive break, and I thought I'd try the new Dynamic Data capabilities that recently went to General Availability in SharePoint Framework 1.7.

I've been building a lot of React components lately, and all the SPFx web parts and application customisers with visual elements we create at Engage Squared, are built on React.  Dynamic Data in SPFx introduces a whole new world of modularity that we haven't had before. We can now split up the page elements into multiple web parts that, in the past, have been combined as one web part so state can be passed between them.  Doing this gives control back to the page author, with the ability to position components how they wish.

Breaking components up in to individual web parts also changes the way the components are designed, and forces the developer to leverage the responsive capabilities of modern pages.  Modern pages are designed from the ground up to work on many different screen sizes, and as long as each individual co…

Apps for SharePoint 2013 - Client and Server-side code

It's about time I blew the dust off this blog. Tonight I did a presentation at the Melbourne SharePoint User Group entitled Apps For SharePoint (2013). It included two demos based on the App For SharePoint 2013 solution template in Visual Studio 2012.

The two demos illustrated how you can create a separate ASP.Net Web Application. Demo 1 showed how easy it is to hook in to SharePoint to obtain List properties via server-side code (populating an ASP.Net Repeater Control). Demo 2 showed what you can do with SharePoint 2013's Javascript hooks. Specifically, using SP.UI.Controls.js from the /_layouts/15/ SharePoint folder to pull chrome elements out of SharePoint, and render them in your ASP.Net web app.

No animals were harmed in the making of these demos, but a few articles kindly provided on the Microsoft MSDN site helped put it together:
How to: Set up an on-premises development environment for apps for SharePointHow to: Create high-trust apps for SharePoint 2013 using the se…

SharePoint User Profiles and Properties error

I recently encountered an issue with the Shared Services Administration page for User Profile and Properties (the page where you schedule an Active Directory profile import).

The page in question is in the Shared Services Provider site, e.g. http://server:port/ssp/admin/_layouts/ProfMain.aspx

The error that gets displayed is:
An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.

The error was odd, because I knew SharePoint Search was functioning (search crawls were running as normal, and search queries were being filled in the web front end). After a bit of investigation, I found the following table to be missing some records that were required.

So in actual fact, the error being referred to when accessing the SQL Server database was that some expected records weren't in the table being looked up, not that …