BREAKING NEWS WARNINGS

THIS BREAKING NEWS WARNING APPLIES ON THE GN4 SYSTEMS  2.1, 2.2 AND 2.3.

We discovered a problem affecting the gn_AuditSnapshotTable for all the builds from the version 2.1 included: due to an index change the table is always increasing in size (can contain hundreds of thousands records) while it should not.

To fix the problem on your current version, stop all the processes that access the database, e.g. Back4, and then execute the following query that deletes the useless content and creates the correct index. Note: the following script assumes that the GN4 database name is "GN4". If that's not your case, then replace "GN4" with your GN4 database name.

Run SQL Management Studio, and then in the File menu, point to New, and then click Query with current connection. In the query window, paste the following query, and then click Execute in the toolbar:

use GN4

delete gn_AuditSnapshotTable

from gn_AuditSnapshotTable sel

where gn_objectid=sel.gn_ObjectId and gn_ModifiedDate != (select max (gn_modifieddate) from gn_AuditSnapshotTable where gn_ObjectId=sel.gn_ObjectId)

go

drop index [dbo].[gn_AuditSnapshotTable].[iTPCVAKVV1FR0TEBOFKHMEUV9M5]

go

CREATE UNIQUE NONCLUSTERED INDEX [iJKDTAQ9FDRD9OE18M3GLUAMF75] ON [dbo].[gn_AuditSnapshotTable] ([gn_ObjectId] ASC)

go

Should you execute the query again in the same session, the following error will be displayed:

(0 row(s) affected)

Msg 3701, Level 11, State 7, Line 9

Cannot drop the index 'dbo.gn_AuditSnapshotTable.iTPCVAKVV1FR0TEBOFKHMEUV9M5', because it does not exist or you do not have permission.

Msg 1913, Level 16, State 1, Line 14

The operation failed because an index or statistics with name 'iJKDTAQ9FDRD9OE18M3GLUAMF75' already exists on table 'dbo.gn_AuditSnapshotTable'.

This is normal, as the index was already created.

On every database upgrade in versions 2.1 through 2.3 you need to re-execute the same query, .

This is fixed in the version 2.4 (GN4-4557).

THIS BREAKING NEWS WARNING APPLIES ONLY ON THE GN4 SYSTEMS  USING THE KASPERSKY ANTIVIRUS AND THE CLICKONCE 32-BIT.

We discovered a problem with the Kaspersky antivirus and the GN4 clickonce applications (32bit only). Fred4.exe and Admin4.exe are recognized as trojans hence blocked and placed in quarantine. The problem may occur on both server and client. On the server some files in the ClickOnce folder are quarantined, making the Clickonce application unusable. On the client the downloaded ClickOnce application is blocked by the AV.

The only possible solution is to configure Kaspersky not to scan the GN4 folders. If you are using Kaspersky, please, do the proper folder scan exclusion before upgrading Kaspersky.

THIS BREAKING NEWS WARNING APPLIES ONLY ON THE GN4 SYSTEMS WITH BUILD OLDER THAN 2608 (AVAILABLE ON July, 23 2015).

The Windows Updates installed around Feb, 16 2016 may break the GN4 in builds older than 2608 (updated before July, 23 2015). #

If your current build is 2608 or newer, you won't have problems.

The system stops to work and nobody can login. The errors and solutions are described in !Cannot login: 'Strong name signed assemblies...' or 'The type initializer...'.