Posted by Robert G Laurin on December 01, 2011 at 09:46:27:
Here are some questions/things I noticed:
Comet Services (Server Products):
- There's no path for the log files. Seems to always go to ./Logs
- Comet Database Server Consoleas an option to View | CFAM Log, but it displays only only the first megabyte or so of the log (actual log file is over 700MB)
- Comet Database Server Console as an option to Clear Log. It only clears the tiny display windows in the Console. Does not clear the physical Log File nor does it change the View | CFAM Log.
- Comet Database Server Console: No option to view the CFAM Users currently connected.
CometAsService:
- CometAsService.INI does have a configuration for LOG file. That is good.
- CometAsService.log does not have any TimeStamps.
- By Default CometNTServices.ini loads all with a PauseStart=1000, but CometAsService.ini has a PauseStart=0. Why? Brian put a post in here recommending not to change that.
- According to Brian's post Using a CometAsService with 'CommandLine=\\MyServer\CometPath\Comet.exe /PN=COMETANY /SERVICE' ensures that the proper executables are updated and properly registered. However I found that once it is started, it is impossible to start a new session using a shortcut to '\\MyServer\CometPath\Comet.exe'. It always yields a 'Access Denied'. Tried with and without /PN= also tried cosw.exe to no avail.
- Since we cannot fire-up new sessions using shortcut, we have to resolve to use the 'New Session' button. Unfortunately, that does not get screen size & position from the cosw.ini but always cascade a new screen (where with a shortcut it remembers where I want my new screen).
- CASMonitor is not running. So I browse and double click the CASMonitor in the CometServices folder. It Fails: 'The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.'. So I don't have my tray Icon (it was there sometime ago) and I have no way of getting it to go (without killing everyone on CometAnywhere).
- CASMonitor is lacking the option to launch a new session.
- if Comet.exe is copying and registering all required dll, why is it that CometLib.dll is pointing to the TEMP folder of an old domain user profile that should be deleted ? All other Comet files are copied in the current user profile but are actually executed from 'Default User\Local Settings\Temp'...
This was tested on a Windows 2003 Domain Controller running Comet Server 11.4 and Comet 2008.398
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.