Posted by Grant Foraker on January 12, 2006 at 11:36:13:
Customer with their own LAN manager. They've set up Comet so that the Comet executables and the CFG files are in a shared directory called Csys (\\PSR_COM\Csys). Mapped to the Q: drive. REL, UTL and the other Comet directories are in another shared folder (\\PSR_COM\Comet$). The $ apparently hides the Comet from Windows Explorer from all but the most experienced users. The INI uses UNC for path names to the directories (\\PSR_COM\Comet$\REL). This has been working file under Comet 2004. Windows 2000 server with USB dongle.
Finally got them to let me come in and upgrade them to the Comet 2005 (last Dec 2005 releases).
Installed CSP 5.10 to "C:\Comet Services" and rebooted. Sec, File, and CFAM all started as services. Previously, SEC and File were launched from "d:\Comet\Comet Server Products".
On a workstation, using the old shortcut, tried to launch q:\cosw.exe /pn=remote /c with StartIn of Q:. It failed with can't find REL and then the whole list of missing QDIR's. Tried lost of other shortcut configurations including a UNC version. Sometimes it would come to Config mode with the /C and sometimes it would default to Config mode with no /C.
Meanwhile, at the File console there were errors messages about "illegal CFAM servers" trying to connect. I didn't write the messages down, thinking wrongly, that they would be in one of the log files.
Finally, gave up and restored them to last 2004 CSP and CSW. Left updated REL and UTL intact.
Could the underscore in the server name be a problem with 2005? Is the hidden ($) share a problem?