Converting to SQL2000 Database does not work either

Support, Questions and Discussions on MonitorWare Agent

Moderator: alorbach

Converting to SQL2000 Database does not work either

Postby Cindy Rittenhouse on Mon Jan 26, 2004 8:07 pm

In my previous entry, I was having Event ID Error 114, and it was suggested that I convert my Access database to SQL 2000, which I did. I am still getting Event ID 114, Source: AdisconMonitoreWareAg in my Windows 2003 server application log.

Error while applying an action - skipping this action. Error is 'ODBC Error Code: '37000'
ODBC Error Description: '[Microsoft][ODBC SQL Server Driver][SQL Server]Disallowed implicit conversion from data type text to data type nvarchar, table 'Syslog.dbo.SystemEvents', column 'EventLogType'. Use the CONVERT function to run this query.'.'.

No event log data is being entered into the System Events table.
There are no errors in the sending servers application logs, the MonitorWare clients. They are configured with Event Log Monitor 1 and SETP server services. I can send you screen shots off line if that will help.

I am a network administrator, not a database administrator, so I have a limited understanding of SQL.

What do I need to do to get the client data into the SystemEvents table?
Cindy Rittenhouse
 

Postby wrehman on Tue Jan 27, 2004 6:11 am

Dear Cindy,

I dont know how you created the systemevents table in the database but the error that you gave us, is clearly telling that at least one of the fields dont have the correct datatype. There could be some other fields with wrong datatypes so i am suggesting the following solution. Please follow these steps to correct your problem:

1. Open your database and delete your old systemevents table (Dont delete the database) (Open Enterprise Manager, Click on Databases, Click on your database, right click on SystemEvents table and click delete)
2. Create a DSN that points to this database (if you already have a DSN that points to this database, then you can skip this step)
3. Open MonitorWare Agent. Right click on Actions and then click on Database Logging Action
4. In Database Logging Action, click on "Create Database" button
5. Enter the DSN that you made in step 2 and login and password to your database. Also select MS SQL below.
6. Click "Create" Button.

Once you have gone through these steps, your old systemevents table that contains incorrect datatypes will be removed and a new SystemEvents table will be created with correct datatypes. I am positive that it will solve your problems. Still if you find any difficulty or any problems, please dont hesitate to contact us. We would be more than happy to help you out.

Best Regards
Wajih-ur-Rehman
Adiscon
User avatar
wrehman
Adiscon Support
 
Posts: 75
Joined: Tue Mar 18, 2003 9:30 am

Postby Guest on Thu Jan 29, 2004 9:17 pm

Thank you very much. Everything seems to be functioning properly now.
Guest
 

Google Ads



Return to MonitorWare Agent

Who is online

Users browsing this forum: No registered users and 0 guests

cron