Posted by Barbara Brazil on March 24, 2004 at 10:55:59:
In Reply to: Re: Comet server posted by Tom Gomez on March 23, 2004 at 15:35:50:
Tom:
Yes, Server = N02,SC; is correct for your situation.
To troubleshoot the CFAMNetServe problem we have to do a couple of things. First, look in the folder where the Comet server products are located. Open a file called CometNTService.ini with a text editor. This is the file that drives the installation of the services. Verify that CFamNetServe.exe is included in the list of products that will be installed. If it is not included, this could be the problem.
If it is included, then it probably got installed but may not have registered properly. I don't know why this would happen, but we can register it manually. Here's how to do that:
Stop the CometServices by using Services.exe. Create a shortcut to CFAMNetServe.exe in the same folder where CFAMNetServe.exe is located. Call the shortcut "Register CNS". Then right-click on it to bring up its properties. Add "-RegServer" to the end of the command line for the target. It should look something like this with your pathname in place of mine:
C:\CometServers\CFAMNetServe.exe -RegServer
Then save the properties, and double-click on your new shortcut. This should register CFAMNetServe. Now restart the CometServices and see if you can load Comet.
bb