Symantec Endpoint Encryption Device Control: 'Automatic Maintenance in Progress' message when trying to access Client Logs in Management Console

Article:TECH184197  |  Created: 2012-03-19  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH184197
Article Type
Technical Solution


Issue



 Symantec Endpoint Encryption Device Control: 'Automatic Maintenance in Progress' message when trying to access Client Logs in Management Console


Error



  'Automatic Maintenance in Progress' message when trying to access Client Logs in Management Console

 


Cause



 We suspect this happens during certain upgrade scenarios, although we don't know for sure.


Solution



****************** This solution includes sample outputs from an actual problem scenario for reference. Procedure was extracted from SQL 2003 Management Studio Express. Please modify as needed for other SQL versions ********************

 

Step 1: Have the customer run the following SQL query on their SymantecEndpointEncryptionDeviceControl database. One way to do this is by using SQL Management Studio -> Databases -> Right-click 'SymantecEndpointEncryptionDeviceControl' and select 'New Query'. This will open up a new query window on the right-hand side pane. Type in the command below and click on the '!Execute' button on the toolbar.

SELECT name, xtype FROM dbo.sysobjects WHERE LEFT(name, 12)='ClientEvents'

A sample output for this may look something like this:

name                                                                                                                             xtype

 -------------------------------------------------------------------------------------------------------------------------------- -----

 ClientEvents_2011-12-24 00-02-11_7                                                                                               U

 clientevents                                                                                                                     U

 ClientEvents_2011-12-31 00-02-12_7                                                                                               U 

ClientEvents_2012-01-07 00-02-18_7                                                                                               U 

ClientEvents_2012-01-14 00-02-16_7                                                                                               U 

ClientEvents_2012-01-21 00-02-21_7                                                                                               U 

ClientEvents_2012-01-28 00-02-11_7                                                                                               U 

ClientEvents_2012-02-04 00-02-17_7                                                                                               U 

ClientEvents_2012-02-11 00-02-13_7                                                                                               U 

ClientEvents_2011-12-03 00-02-12_7                                                                                               U 

ClientEvents_2012-02-18 00-02-28_7                                                                                               U 

ClientEvents_2011-12-10 00-16-50_7                                                                                               U 

clientevents_2012-02-25 00-02-24_7                                                                                               U 

ClientEvents_2011-12-17 00-02-10_7                                                                                               U 

(14 row(s) affected)

 

 

 Step 2:

Here's a breakdown of the information you're looking at:


ClientEvents                                                              U                                                ß This is the current Client Logs table in our database

ClientEvents_2011-12-24 00-02-12_7                  U                                                ]

ClientEvents_2011-12-31 00-02-12_7                  U                                                ]

.                                                                                                                                      ]

.                                                                                                                                      ] ß These are ‘archived’ Server Logs tables

.                                                                                                                                      ]      (As you can see we archive them every 7 days)

.                                                                                                                                      ]

ClientEvents_2011-12-17 00-02-10_7                  U                                                ]

 clienteventsview                                                       V                                               ß  This is the ‘View’ that combines data from all the tables above (this view is missing in the output above, and is what is causing the error message. we just need to recreate it using info from all the tables above)

 

 Alright, so first thing is to check (in SQL management studio) to ensure that the ClientEvents archived tables all have the same format (if 2 of them match up, then you can probably assume the remaining will match up, but always good to check up):

 

In SQL Mgmt Studio:

 

1.       Go to Databases -> SymantecEndpointEncryptionDeviceControl -> Tables -> dbo.clientevents

2.       Right-click dbo.clientevents, select ‘Script Table as’ -> ‘CREATE TO’ -> New Query Editor Window

 

You’ll see something like this:

************************************************************************************************

USE [SymantecEndpointEncryptionDeviceControl]

GO

/****** Object:  Table [dbo].[clientevents_2012-02-28 14-45-29_7]    Script Date: 03/19/2012 03:14:45 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

CREATE TABLE [dbo].[clientevents_2012-02-28 14-45-29_7](

      [Id] [int] IDENTITY(0,1) NOT NULL,

      [Sequence] [int] NOT NULL,

      [EventId] [bigint] NOT NULL,

      [EventType] [int] NOT NULL,

      [EventScope] [int] NOT NULL,

      [User] [nvarchar](400) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [ClientId] [nvarchar](400) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,

      [ClientHost] [nvarchar](400) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,

      [EventTimeGMT] [datetime] NOT NULL,

      [EventTimeLocal] [datetime] NOT NULL,

      [ServerTimeGMT] [datetime] NOT NULL,

      [CustomGroup] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [PolicyId] [int] NULL,

      [PolicyRevision] [int] NULL,

      [PolicyName] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [PolicyType] [smallint] NULL,

      [DeviceDescription] [nvarchar](1000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [DeviceInfo] [nvarchar](1000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [Port] [int] NULL,

      [BuiltinGroup] [int] NULL,

      [HostClass] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [DeviceVendor] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [DeviceModel] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [DeviceDistinctId] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [DevicePort] [int] NULL,

      [LongMediaFingerprint] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [DiskSize] [int] NULL,

      [NetworkEncryption] [smallint] NULL,

      [NetworkAuthentication] [smallint] NULL,

      [Details] [ntext] COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [MissedEventsFirstGMT] [datetime] NULL,

      [MissedEventsCount] [int] NULL,

      [SearchBuffer] [ntext] COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [ClientVersion] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

      [ClientBuildNumber] [nvarchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

CONSTRAINT [PK_clientevents] PRIMARY KEY NONCLUSTERED

(

      [Id] ASC

)WITH (PAD_INDEX  = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]

) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

*************************************************************************************************

 

3.       Do the same for the other ClientEvents tables and compare them. You’re looking to ensure that all the columns ([ID], [Sequence], [EventId], etc are in the same sequence and have the same descriptions / data types. An easy way to do this is to put on trial version of ‘Beyond Compare’ and it’ll let you do a text compare where you can copy/paste in content from 2 tables and it’ll tell you right away if something’s different.

4.       In this customer’s case, we’re expecting something to be different in the clientevents_2012-02-25 00-02-24_7 table

5.       If there is indeed something different in that table (either sequence of columns, or the data type) we’ll make the changes by going to that table, right-click and select ‘Modify’. This will bring up a window pane similar to the one below:

 

6.       If it just a change in sequencing, then we can simply click and drag the items in this window to rectify the sequence

7.       If we need to add/delete/modify columns, you can do that as well using this same window. Once we know that all their dbo.clientevents and dbo.ClientEvents archived tables are all the same, in terms of sequence of columns and data types, then we’re ready to run the SQL Command that will recreate their missing view:

 

USE [SymantecEndpointEncryptionDeviceControl]

GO

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

create view [dbo].[clienteventsview] as

select * from [dbo].[ ClientEvents_2011-12-24 00-02-11_7] union all

select * from [dbo].[ ClientEvents_2011-12-31 00-02-12_7] union all

select * from [dbo].[ ClientEvents_2012-01-07 00-02-18_7] union all

select * from [dbo].[ ClientEvents_2012-01-14 00-02-16_7] union all

select * from [dbo].[ ClientEvents_2012-01-21 00-02-21_7] union all

select * from [dbo].[ ClientEvents_2012-01-28 00-02-11_7] union all

select * from [dbo].[ ClientEvents_2012-02-04 00-02-17_7] union all

select * from [dbo].[ ClientEvents_2012-02-11 00-02-13_7] union all

select * from [dbo].[ ClientEvents_2011-12-03 00-02-12_7] union all

select * from [dbo].[ ClientEvents_2012-02-18 00-02-28_7] union all

select * from [dbo].[ ClientEvents_2011-12-10 00-16-50_7] union all

select * from [dbo].[ ClientEvents_2012-02-25 00-02-24_7] union all

select * from [dbo].[ ClientEvents_2011-12-17 00-02-10_7] union all

select * from [dbo].[clientevents]




Article URL http://www.symantec.com/docs/TECH184197


Terms of use for this information are found in Legal Notices