Posted by Tom Fulton on May 30, 2014 at 08:31:11:
In Reply to: Re: Strange Comet startup...> posted by Barbara Brazil on May 29, 2014 at 12:32:58:
Additional information from this morning:
User 1 - Has had the issue all week. I connected after PC was started and nothing else was run except LogMeIn so that I could connect. Same symptoms as the attachments in the previous post. I restarted the PC and it connected with no problem
User 2 - Has had the issue all week. I connected up and nothing had been started. I inspected Windows Explorer and saw red X on the mapped network drives. I clicked on the drives to "wake them up". I ran Comet and it started without issue.
User 3 - Has had the issue all week. I connected up and nothing had been started. Windows Explorer showed the network drives properly. I launched the Comet icon and got the list of files not found. On this machine I installed a Comet with REL and UTL on the C: drive. I then went into Comet with /c /d and configured the ini file to point rel and utl to the C: drive, all other UNC paths to the server stayed the same. I then modified the shortcut to point to C: for target and start in and Comet started right up!
It gets more interesting. The behavior I'm about to describe takes place on all the PCs having this issue. When I launch the shortcut with a target of Comet.exe, the list of object programs not found comes up. The Security Server running on the Comet server does not show that a request to connect has been made. When I change the shortcut to point to CosW, the security server does show a request to connect. On the user PC I get the following message "The Comet Net Server N01 located at 10.0.188.203 could not be connected."
So I do have a method of getting around the issue - I can put a Comet on each local drive where the problem is occurring. But the questions are:
1) Why does the user fail with an error 3 when trying to copy those object programs to their Temp folder?
2) Why does the launch of CosW.exe report that the Comet Net Server cannot be located when a ping to the server is good?
3) Why is this happening on a half dozen workstations when 25 other ones connect and run fine? By the way, almost all of the user workstations are identically configured Win7 32-bit PCs.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.