Posted by Grant Foraker on November 18, 2005 at 07:16:51:
In Reply to: Re: CFAMNetServe posted by Grant Foraker on November 16, 2005 at 09:52:31:
Out to the customer (Win2K and parallel dongle) yesterday with the idea of uninstalling CSP from "e:\comet\comet server products" and reinstalling to "c:\Comet Services" to see if the service would load without error and launch sec, file, and CFAM.
Services showed "CometServices" stopped. Terminated the consoles, uninstalled CSP and a second Comet program (didn't write down the name). That may have been the source of the problem. Installed CSP to the new location and checked Services. CometServices was still listed and the Start option was usable. Clicked start and CometSevices started without errors. However, only the file console came up. Decided to reboot.
CometServices loaded without error and sec, file and CFAM were launched. Two microseconds of joy. Launched Comet.exe from a workstation, same all "S" directory CFG that worked 30 minutes before, and all the directories failed with the 2002 error message.
Since I also upgraded CSP from 5.08 to 5.10, I decided to go back to 5.08. Opened Services and stopped CometServices. Sec, file and CFAM terminated. I should have launched sec, file and CFAM manually and tested Comet at the workstation. However, I was very pressed for time and I went ahead with the 5.08 install over the top of 5.10. I returned to Services, which I had left open, and found the Start option grayed out. I closed and reopened Services. CometServices was no longer listed. Before rebooting I decided to try launching sec, file, and CFAM manually. They loaded without error. I retried a workstation and Comet loaded correctly.
Being totally out of time and having a working system I decided to put this off until after next weeks holiday. The customer has a major production job on Monday and will be closed Thursday and Friday.
I thinks this shows that on a Win2k server with a parallel dongle you're probably going to have to reboot after a CSP upgrade.