Are you getting the same autostart macro failed error message if you try to launch an offline session of the instrument vs an online session? Sometimes these types of errors can be caused by a corruption in one or multiple configuration files for the instrument, some of which are specific to online and offline sessions.
1) You can send us your instrument log and we can see if we can determine a cause of the error from the log. This log can be found at the following path: C:\Chem32\#\TEMP\ where the # would be the instrument number (1,2,3, or 4). The log will be named INSTR#.log.
2) You can try configuring a new instrument as a proof of concept that this is an instrument specific configuration issue. If the new instrument launches without error, then we can narrow the troubleshooting focus.
3) If this is a time sensitive issue we can try a "shotgun approach" and just rename (change the file extension to .old or .bak for example) or delete some instrument configuration files which will force the software to recreate them the next time you launch an online session. If you want to go this route, then the files to rename/delete would be:
ChemStationPerInstrumentSettings.config
CONFIG.reg
instrument.config
RapidControl.InstrumentConfig.xml
These are all located in the C:\Chem32\#\ path I mentioned in option 1. If you rename/delete these files, the next time you launch an online session of your instrument the software will prompt you to reconfigure the instrument and you will need to provide the instrument's IP address. If the software launches successfully, you will need to reset your preferences as they were stored in some of these files.
1) You can send us your instrument log and we can see if we can determine a cause of the error from the log. This log can be found at the following path: C:\Chem32\#\TEMP\ where the # would be the instrument number (1,2,3, or 4). The log will be named INSTR#.log.
2) You can try configuring a new instrument as a proof of concept that this is an instrument specific configuration issue. If the new instrument launches without error, then we can narrow the troubleshooting focus.
3) If this is a time sensitive issue we can try a "shotgun approach" and just rename (change the file extension to .old or .bak for example) or delete some instrument configuration files which will force the software to recreate them the next time you launch an online session. If you want to go this route, then the files to rename/delete would be:
ChemStationPerInstrumentSettings.config
CONFIG.reg
instrument.config
RapidControl.InstrumentConfig.xml
These are all located in the C:\Chem32\#\ path I mentioned in option 1. If you rename/delete these files, the next time you launch an online session of your instrument the software will prompt you to reconfigure the instrument and you will need to provide the instrument's IP address. If the software launches successfully, you will need to reset your preferences as they were stored in some of these files.
When you tried ryoboyle's option #3, did the software in fact prompt you to configure your instrument? If not, something was likely not reset properly.
Ok, in that case I think the log would help to see if any other steps can be attempted. A repair or uninstallation followed by reinstallation would be the ultimate fix, but you would probably want to avoid that if there's another option. Even thought this does seem like it was an instrument configuration problem, it's very strange that configuring a new instrument didn't get rid of the problem for you. Below are some relevant questions that might help point to the problem?
Was there anything that happened to the computer (including a power outage), operating system, or computer prior to this error coming up?
Did you or any other user change the location of methods, sequences, data, or report templates?
Is the Windows user a new one from what was used before?
Was a Windows Update done?
Was the PC previously not on a company network but now is?
We are glad this was helpful! We are sorry this was not helpful. If you still need assistance please create a community post or contact support. To help us improve, please provide any additional feedback.
For full details of how we will treat your information, please view our privacy policy.
