-
- Posts: 3477
- Joined: Mon Jan 07, 2013 8:54 pm
So, Happy Halloween. We have had more tricks here today than treats for certain.
Today I have had three systems that are running Windows 7 and MSD Chemstation that all had problems starting up. When first starting the software we got a message box simply stating "6890col.mdb" with and OK button on it.
I went to searching and could not find that file anywhere on the computer. I finally searched another system and found the file in the msdchem\driver folder so I copied it to the first system with problems and then when starting the software we got a similar error but for "catalog.mdb", so copied that file from the same place and tried again. This time it got further into the startup but died when loading the 6890 parameters. When looking into the error details it list the error in "msinsctl.exe" when it was calling "msvcr90.dll" . I tried replacing the dll file but that didn't work. I finally ended up using system restore to rollback the system a week and it started working.
The problem seems to be related to some kind of update, but according to the logs we didn't have any updates to Windows come through and they are supposed to be turned off on the computers to begin with. Doing a check when rolling back the system did show that Adobe Flash Player was the only program affected by the rollback. Not sure if that had something to do with it or not, but can't understand why the column database files would be missing on three systems because of a flash player update
This only happened after rebooting a system. Two were logged out and it happened after starting them up, the third was running all weekend and not having problems with chemstation but it did bug when uploading data into the LIMS so I rebooted it and then the problem appeared. The computer I copied the missing files from is still running and I am going to reboot it tomorrow and see what happens. This happened on one 5975 and two 5973 instruments, and all with Windows 7. We rebooted one running XP and it didn't have a problem.(Another reason I prefer XP )
Just wondering now if this problem is isolated to us, or if others are having similar problems. At least if you are I hope this will help. I have sent an email to our Agilent service tech and waiting to hear back if they have any answers.
Today I have had three systems that are running Windows 7 and MSD Chemstation that all had problems starting up. When first starting the software we got a message box simply stating "6890col.mdb" with and OK button on it.
I went to searching and could not find that file anywhere on the computer. I finally searched another system and found the file in the msdchem\driver folder so I copied it to the first system with problems and then when starting the software we got a similar error but for "catalog.mdb", so copied that file from the same place and tried again. This time it got further into the startup but died when loading the 6890 parameters. When looking into the error details it list the error in "msinsctl.exe" when it was calling "msvcr90.dll" . I tried replacing the dll file but that didn't work. I finally ended up using system restore to rollback the system a week and it started working.
The problem seems to be related to some kind of update, but according to the logs we didn't have any updates to Windows come through and they are supposed to be turned off on the computers to begin with. Doing a check when rolling back the system did show that Adobe Flash Player was the only program affected by the rollback. Not sure if that had something to do with it or not, but can't understand why the column database files would be missing on three systems because of a flash player update
This only happened after rebooting a system. Two were logged out and it happened after starting them up, the third was running all weekend and not having problems with chemstation but it did bug when uploading data into the LIMS so I rebooted it and then the problem appeared. The computer I copied the missing files from is still running and I am going to reboot it tomorrow and see what happens. This happened on one 5975 and two 5973 instruments, and all with Windows 7. We rebooted one running XP and it didn't have a problem.(Another reason I prefer XP )
Just wondering now if this problem is isolated to us, or if others are having similar problems. At least if you are I hope this will help. I have sent an email to our Agilent service tech and waiting to hear back if they have any answers.
The past is there to guide us into the future, not to dwell in.
