FROM THE IGLOO

We have had some customers reporting an issue upgrading to a point release of Faronics Core 3.2. The issue has been replicated by development at this time and we have been given the following workaround to get customers up and running until a fix is released:

QA Team has replicated and confirmed FCC issue  #1249 “Upgrade of Core Console 3.2 from 3.1 rolling back [DBUpgrad]ERROR:”

This problem will appear for customers using remote database with SQL Authentication. When upgrade process is started, FC is trying to connect to SQL Server using local system account instead of SQL account from ServerConfig.xml file.  Currently FC developers are working on fix for this issue, meantime we found there is workaround for customer who affected by it:

1. In SQL Server Managment Studio under Security -> Logins customer will need to create an account for local system for machine with FC installed “<DOMAIN_NAME>\<MACHINE_NAME>$”.

2. In the Poperties for this account “User Mapping” should be enabled for FaronicsCore and FCCMembership.

3. Both FaronicsCore and FCCMembership should have db_owner and db_securityadmin roles enabled.

Please notice, this account is necessary only for upgrade process.

Once upgrade process is finished, this account can be removed and FC will continue using SQL account set up during original FC 3.1 installation.

As more information comes up we will keep you posted.