I think I've found a bug. I'm trying out Storage Monitor v5.0.2.49. I added two file system analyzer monitors to a server and let it run overnight. Within 24 hours I've received four emails saying that there was a database error. The logs show entries like the following:

11-02-2012, 17:24:31.035, TID:03708, PID:02524, ERROR: #### sqlite_step failed with 19 (column Name is not unique  ExtErr=19) for SQL=[begin immediate;INSERT INTO Owner (Name) VALUES ('MYDOMAIN\MYUSER');;
end;]
11-02-2012, 17:24:31.035, TID:03708, PID:02524, ERROR: begin immediate;INSERT INTO Owner (Name) VALUES ('MYDOMAIN\MYUSER');;
end;
11-02-2012, 17:24:31.035, TID:03708, PID:02524, ERROR: SQL_PRIMARY = C:\Program Files\PA Storage Monitor\Databases\FileSystem_Owner.db
11-02-2012, 17:24:31.035, TID:03708, PID:02524, SetCoreStatus: 2, id=
11-02-2012, 17:24:31.035, TID:03708, PID:02524, ERROR: #### sqlite_exec failed with 19 (column Name is not unique  ExtErr=19) for SQL=[begin immediate;INSERT INTO Owner (Name) VALUES ('MYDOMAIN\MYUSER');;
end;].  Will re-open
11-02-2012, 17:24:31.035, TID:03708, PID:02524, ERROR: begin immediate;INSERT INTO Owner (Name) VALUES ('MYDOMAIN\MYUSER');;
end;
11-02-2012, 17:24:31.035, TID:03708, PID:02524, ERROR: SQL_PRIMARY = C:\Program Files\PA Storage Monitor\Databases\FileSystem_Owner.db
11-02-2012, 17:24:31.128, TID:02732, PID:02524, ThreadProc -> GSAlrt
11-02-2012, 17:24:31.128, TID:02732, PID:02524, BROADCAST: System Error Detected: Database errors.  See service log.
Ver 5.0.2 (Build 49)

11-02-2012, 17:24:31.128, TID:02732, PID:02524, EVENTLOG: System Error Detected: Database errors.  See service log.

Is there a workaround?

asked 02 Nov '12, 20:57

matt's gravatar image

matt
10222
accept rate: 0%


Hi Matt. If you restart the PA Storage Monitor service, I would expect this will go away (it will refresh the in-memory username cache). But if it ever happens again after one restart, please contact Support so we can investigate it further.

link

answered 03 Nov '12, 10:15

Doug's gravatar image

Doug ♦♦
10.1k112037
accept rate: 21%

We've investigated the logs you sent. This error turns out to be harmless and is caused by two scans running simultaneously both entering the same usernames into the database. Once both scans complete, you probably won't see it happen again. We are making a change in the program to catch this case and not alert on it since everything is actually working fine. The update will be out within a week.

link

answered 05 Nov '12, 09:20

Doug's gravatar image

Doug ♦♦
10.1k112037
accept rate: 21%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×3
×2

Asked: 02 Nov '12, 20:57

Seen: 13,657 times

Last updated: 05 Nov '12, 09:20