Opened 9 years ago

Closed 9 years ago

#250 closed defect (fixed)

Database error when attempting to Convert Legacy Data

Reported by: rcarney Owned by: dzollars
Priority: critical Milestone: future
Component: ultrascan3 Version:
Keywords: Cc: randy.carney@…

Description

After editing run information, managing solutions, etc., and attempting to 'Save,' an 'Unspecified database error: Error processing file:' occurred. I've attached a screenshot of the complete error notification to this ticket.

It happened on separate computers and multiple times.

Attachments (2)

save legacy data error.tiff (22.5 KB) - added by rcarney 9 years ago.
screenshot of error message
save legacy data error.png (22.5 KB) - added by rcarney 9 years ago.
screenshot of error message

Download all attachments as: .zip

Change History (10)

Changed 9 years ago by rcarney

screenshot of error message

comment:1 follow-up: Changed 9 years ago by rcarney

  • Cc randy.carney@… added

comment:2 in reply to: ↑ 1 Changed 9 years ago by demeler

Replying to rcarney:
Hmm, is it just me or can others also not view the attachment? I wonder if we can establish that the network connection isn't failing. There are probably a lot of hops in between and who knows what kind of firewall settings. Bruce: Is there a way to make sure? If the testing you can do in the "Edit Preferences" module sufficient to make sure it can send data over ssl? How would be notice a time out? To me this sounds like a network issue.

Changed 9 years ago by rcarney

screenshot of error message

comment:3 Changed 9 years ago by rcarney

Actually, it happened when I was setting up UltraScan? for the first time on a new computer (windows). I had to set up the database in 'edit preferences' and it worked successfully.

I can scan data in 'manage data,' create new projects, analytes, buffers, etc., all on the database, it's just not saving the data itself after converting.

comment:4 follow-up: Changed 9 years ago by dzollars

  • Owner changed from bdubbs to dzollars
  • Status changed from new to assigned

This sounds like it's in us_convert. Looking at the code it looks like the most likely place this error message would occur is when the program is trying to upload the auc data itself as a binary blob into the database. This code changed yesterday, and now the database stored routine requires a checksum to be sent along with the data. There are other improvements in error handling while uploading in us_db2 and us_convert as well.

We need to have people install a later version of the software.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 9 years ago by demeler

Replying to dzollars:

This sounds like it's in us_convert. Looking at the code it looks like the most likely place this error message would occur is when the program is trying to upload the auc data itself as a binary blob into the database. This code changed yesterday, and now the database stored routine requires a checksum to be sent along with the data. There are other improvements in error handling while uploading in us_db2 and us_convert as well.

We need to have people install a later version of the software.

The checksum business explains the problem. I will post new linux versions online, Bruce, can you package and upload the Windows versions, and Gary, can you try to make a new Mac release for PPC, then Jeremy can make one for Intel Macs? Is release 1007 a good one to use?

comment:6 in reply to: ↑ 5 ; follow-up: Changed 9 years ago by dzollars

Replying to demeler:

Is release 1007 a good one to use?

Yes, 1006 or later should work.

comment:7 in reply to: ↑ 6 Changed 9 years ago by dzollars

Replying to dzollars:

Yes, 1006 or later should work.

Version 1106; sorry.

comment:8 Changed 9 years ago by rcarney

  • Resolution set to fixed
  • Status changed from assigned to closed

ok, in the version 1107 (for Linux) the problem does not exist anymore...

thanks!

Note: See TracTickets for help on using tickets.