If you're using SQL Server log and session data you will need delete the Log and Session tables and then run the Console SQL Wizard to recreate them or manually update the tables.

wwRequestLog Changes
The wwRequestLog has been updated to hold a unique Request Id that is passed from the ISAPI extension.

CREATE TABLE (THIS.cLogFile) FREE ;
     (    ;
     TIME        T ,;
     REQID       C(20),;
     Script      c(50) ,;
     QueryStr     M ,;
     REMOTEADDR  C(16) ,;
     Duration    N (5,2),;
     MemUsed    C (8) ,;
     ERROR        L ,;
     REQDATA     M,;
     Browser     M,;
     Respone    M )

For SQL Server:

CREATE TABLE [dbo].[wwrequestlog] (
   [time] [datetime] NOT NULL ,
   [reqid] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [script] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [querystr] [varchar] (254) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [duration] [numeric](7, 3) NOT NULL ,
   [memused] [char] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [error] [bit] NOT NULL ,
   [reqdata] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [browser] [varchar] (156) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL 
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

wwSession Updates
The wwSession class has changed the way the Session table is created by widening the SessionID to 14 characters. The widening is to ensure unique session ids that create SYS(2015) plus the current ThreadID.

If you use FoxPro Table Session (wwSession) then you can simply delete your wwSession table. Web Connection will automatically recreate the file as needed. The update structure is:

CREATE TABLE ( THIS.cDataPath+THIS.cTableName ) FREE;
  (SESSIONID    C (14),;
   USERID      C (15),;
   FIRSTON     T ,;
   LASTON      T ,;
   VARS        M ,;
   BROWSER     M ,;
   IP          M ,;
   HITS         I )

If you forget to update your FoxPro table the code will still work but the new ThreadID is stripped. This is not really an issue - you get essentially the old behavior. This change really only affects high volume applications where many instances are running simultaneously.

For SQL Server you will need to modify the database and change the

CREATE TABLE [dbo].[wwsession] (
   [SessionID] [char] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [UserId] [char] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [firston] [datetime] NOT NULL ,
   [laston] [datetime] NOT NULL ,
   [vars] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [browser] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
   [ip] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
   [hits] [int] NOT NULL 
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO

If you forget to update the SQL Session table you will get errors when trying to write a new session record.