AdisconMonitorWareAg Event ID:114

Support, Questions and Discussions on MonitorWare Agent

Moderator: alorbach

AdisconMonitorWareAg Event ID:114

Postby Cindy Rittenhouse on Wed Jan 07, 2004 10:36 pm

One of our programmers was attempting to delete records based on certain criteria using Access 2000, but got an invalid argument. She deleted the query. Ever since, my log server application event viewer is filled with :
AdisconMonitoreWareAg Event ID:114
Error while applying an action-skipping this action. Error is "ODBC Error Code:'S1093"
ODBC Error Descriptor [Microsoft] [ODBC Microsoft Access Driver] Invalid argument...

after several of these errors, I then get an
AdisconMonitorWareAg Event ID: 151
Numerous runtime errors were encountered
This is usually caused by configuration or network problems.
From now, there will be no more events logged for this hour

Since these errors started, no records are being created the the system events table. We are running on a Windows 2003 Server, and we have rebooted the system.

How do I correct this problem?

Thanks
Cindy Rittenhouse
 

Postby alorbach on Thu Jan 08, 2004 9:17 am

Hi,

it looks like that the systemevents table was altered (if it worked before).
Maybe the type of one existing field was changed.

In order to correct that problem, I would need to know how the table defintion of SystemEvents looks now.
You can also compare the table defintion with that teh sample Database (hich is installed by MWAgent).
User avatar
alorbach
Site Admin
 
Posts: 900
Joined: Thu Feb 13, 2003 11:55 am

Postby Cindy Rittnhouse on Thu Jan 08, 2004 3:39 pm

Here is the table definition. We are using the sample.mdb that came with the MonitorWare. I was trying to keep everything as simple as possible, and everything was working fine until we tried to delete some entries. In only 2 months we had a 2GB database with over 3 million records. Using Access 2002, we were trying to delete all records where thre NT Severity = 2 0r 8 where the Event Source or Event Log Type did not = Security, but received and invalid argument when we tried to run it.


D:\Program Files\MonitorWare\Console\sample.mdb Thursday, January 08, 2004
Table: SystemEvents Page: 1
Properties
DateCreated: 1/31/2003 11:52:35 AM DefaultView: Datasheet
LastUpdated: 9/17/2003 5:21:54 PM OrderByOn: True
Orientation: Left-to-Right RecordCount: 3142784
Updatable: True
Columns
Name Type Size
ID Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size, Auto-Increment
CollatingOrder: General
ColumnHidden: False
ColumnOrder: Default
ColumnWidth: Default
DataUpdatable: False
OrdinalPosition: 0
Required: False
SourceField: ID
SourceTable: SystemEvents
CustomerID Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 1
Required: False
SourceField: CustomerID
SourceTable: SystemEvents
ReceivedAt Date/Time 8
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 2
Required: False
SourceField: ReceivedAt
SourceTable: SystemEvents
DeviceReportedTime Date/Time 8
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 3
Required: False
SourceField: DeviceReportedTime
SourceTable: SystemEvents
Facility Integer 2
AllowZeroLength: False
Attributes: Fixed Size

D:\Program Files\MonitorWare\Console\sample.mdb Thursday, January 08, 2004
Table: SystemEvents Page: 2
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 4
Required: False
SourceField: Facility
SourceTable: SystemEvents
Priority Integer 2
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 5
Required: False
SourceField: Priority
SourceTable: SystemEvents
FromHost Text 60
AllowZeroLength: False
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 6
Required: False
SourceField: FromHost
SourceTable: SystemEvents
Message Memo -
AllowZeroLength: False
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 7
Required: False
SourceField: Message
SourceTable: SystemEvents
NTSeverity Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 8
Required: False
SourceField: NTSeverity
SourceTable: SystemEvents
Importance Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 9
Required: False
SourceField: Importance
SourceTable: SystemEvents
EventSource Text 60
AllowZeroLength: False

D:\Program Files\MonitorWare\Console\sample.mdb Thursday, January 08, 2004
Table: SystemEvents Page: 3
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 10
Required: False
SourceField: EventSource
SourceTable: SystemEvents
EventUser Text 60
AllowZeroLength: False
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 11
Required: False
SourceField: EventUser
SourceTable: SystemEvents
EventCategory Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 12
Required: False
SourceField: EventCategory
SourceTable: SystemEvents
EventID Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 13
Required: False
SourceField: EventID
SourceTable: SystemEvents
EventBinaryData Memo -
AllowZeroLength: False
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 14
Required: False
SourceField: EventBinaryData
SourceTable: SystemEvents
MaxAvailable Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 15
Required: False
SourceField: MaxAvailable
SourceTable: SystemEvents
CurrUsage Long Integer 4

D:\Program Files\MonitorWare\Console\sample.mdb Thursday, January 08, 2004
Table: SystemEvents Page: 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 16
Required: False
SourceField: CurrUsage
SourceTable: SystemEvents
MinUsage Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 17
Required: False
SourceField: MinUsage
SourceTable: SystemEvents
MaxUsage Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 18
Required: False
SourceField: MaxUsage
SourceTable: SystemEvents
InfoUnitID Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 19
Required: False
SourceField: InfoUnitID
SourceTable: SystemEvents
SysLogTag Text 60
AllowZeroLength: False
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 20
Required: False
SourceField: SysLogTag
SourceTable: SystemEvents
EventLogType Text 60
AllowZeroLength: False
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 21
Required: False
SourceField: EventLogType
SourceTable: SystemEvents

D:\Program Files\MonitorWare\Console\sample.mdb Thursday, January 08, 2004
Table: SystemEvents Page: 5
GenericFileName Text 60
AllowZeroLength: False
Attributes: Variable Length
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 22
Required: False
SourceField: GenericFileName
SourceTable: SystemEvents
SystemID Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 23
Required: False
SourceField: SystemID
SourceTable: SystemEvents
Checksum Long Integer 4
AllowZeroLength: False
Attributes: Fixed Size
CollatingOrder: General
DataUpdatable: False
OrdinalPosition: 24
Required: False
SourceField: Checksum
SourceTable: SystemEvents
Table Indexes
Name Number of Fields
PrimaryKey 1
Clustered: False
DistinctCount: 3142784
Foreign: False
IgnoreNulls: False
Name: PrimaryKey
Primary: True
Required: True
Unique: True
Fields:
ID Ascending
User Permissions
admin Delete, Read Permissions, Set Permissions, Change Owner, Read Definition,
Write Definition, Read Data, Insert Data, Update Data, Delete Data
Group Permissions
Admins Delete, Read Permissions, Set Permissions, Change Owner, Read Definition,
Write Definition, Read Data, Insert Data, Update Data, Delete Data

D:\Program Files\MonitorWare\Console\sample.mdb Thursday, January 08, 2004
Table: SystemEvents Page: 6
Users Delete, Read Permissions, Set Permissions, Change Owner, Read Definition,
Write Definition, Read Data, Insert Data, Update Data, Delete Data
Cindy Rittnhouse
 

Postby alorbach on Thu Jan 08, 2004 4:22 pm

You are kidding, you have a 2 Gb large MS Access database? :shock: :shock: :shock:
I never thought that MS Access database could reach that size ;)

And thats also the problem, MS Access does not support more then 2 GB as database file size, so you need to delete data.

There is a delete records option in MWConsole which you can use, see Tools->Database Maintenance.
User avatar
alorbach
Site Admin
 
Posts: 900
Joined: Thu Feb 13, 2003 11:55 am

Postby rgerhards on Thu Jan 08, 2004 4:26 pm

Actually, I would recommend to move to either Microsoft SQL Server (or the free MSDE, which has a 4 GB limit) OR MySQL. Both of these solutions provide you with far better response time.

Let me explain: I am the one responsible for the Access database in the default install set. Access is far easier to set up and a good choice for small installations. However, it can easily be outgrown. So while access is good for starters, it is not a good option for medium to high volume or in the long term.

Personally, I would recommend moving to MySQL.

Best regards,
Rainer Gerhards
Adiscon
User avatar
rgerhards
Site Admin
 
Posts: 1695
Joined: Thu Feb 13, 2003 11:57 am

Postby Cindy Rittenhouse on Thu Jan 08, 2004 9:04 pm

thanks, I will look into the MySQL option. I do have several licensed copies of Microsoft SQL 2000, if that is another option.
Cindy Rittenhouse
 

Postby Guest on Thu Jan 08, 2004 9:25 pm

Microsoft SQL 2000 is absolutely an option. It is the primary development platform. So if you have it at hand, don't waste time thinking about MySQL and use your existing infrastructure!

Rainer
Guest
 

Google Ads



Return to MonitorWare Agent

Who is online

Users browsing this forum: No registered users and 0 guests

cron