Page 1 of 1

LC Chemstation Fatal Error

Posted: Sun Aug 01, 2010 2:13 am
by bisnettrj2
Has anyone experienced this error in Chemstation A.10.02?

Image

It happens when I click on the box that allows you to zoom in on the online signals, and manipulate the signals being displayed in the "Method and Run Control" view.

The dialog boxes pop up in the order that I crudely labeled them, then the Chemstation shuts down and I need to restart the computer to regain control of the LC.

If you've seen this error, is there a way to prevent it?

Posted: Mon Aug 09, 2010 5:25 pm
by HPLCCONSULT
We have seen it many times.

It is often caused by file corruption in the core or code files running ChemStation. A bad installation can also create it too. Solution. Back up all data, Methods and Sequences and remove the ChemStation software (* including registration entries) from the computer, re-pack/defragment the drive, re-boot and then re-install the software.

As for the cause... well, anything that corrupts the files. Some examples would include application or system crashes, NOT defragmenting and maintaining your hard drive on a regular basis or running the program in too small of a disk volume (or partition).

Posted: Mon Aug 09, 2010 6:03 pm
by bisnettrj2
Aha! Thank you for the info, I had a feeling that might be the case. Now for finding down time on the instruments to remedy the situation...

Fatal Error

Posted: Mon Aug 23, 2010 4:02 pm
by nimbi63
The online signals display is controlled in the Configuration register file. Close ChemStation, browse to HPChem\1 (if it's instrument 1) and rename the Config.REG file to Config.BAK. (if there is a config.bak, delete it first) Keep in mind the extentions may be hidden, if so, look for Config.

Now browse to the HPChem\1\Temp folder, keep the INSTR1.LOG and INSTR1-2.log, and delete all other files.

Restart ChemStation online, select View, Full Menu. On the command line at the bottom, enter: RestoreColumns

The last is a macro to copy any column information you had in Config.bak to the new config.reg. This should repair your problem.