I administer contibute for my organization. We only have about a dozen users - most of them are working fine. Everything is done on our local LAN - there is no FTP involved. I have one user who was connected and things were working fine until her connection suddenly stopped working. I tried sending a connection key (which had always worked before) and she got a message saying Contribute was unable to connect to the server.
I tried uninstalling and re-installing contribute, and resending a connection key. I got the same response of unable to connect to the server. In the meantime, I re-installed contribute on a different user's machine and sent a connection key - no problem with her.
The problem user's desktop machine had become notoriously slow and unstable, so the operating system was reloaded. I again loaded the client Contribute CS3 on the reformatted machine and sent a connection key. Again I got the same response of unable to connect to the server.
I deleted the user's group on contribute and created a new one for her and sent a new connection key. Again I got the same response of unable to connect to the server. One last time I used remove programs to remove Contribute so I could try another re-install (since a lot of software (including outlook) had been installed between the time I installed Contribute on the rebuilt machine and when I sent the connection key.
Even though the Contribute program removal went to a normal completion and I restarted the machine, when I tried to re-install Contribute for the umpteenth time, it didn't ask me for a serial number. There appears to be some memory of contribute remaining in the machine. Can anyone give me a suggestion on where to look for this problem or what to try next (short of dynamiting this machine)?
Thanks for any suggestions you can give.
We figured out here that windows active directory permissions for this particular user had been accidentally deleted for one of the 3 directories that she normally updates. The Contribute permissions were still intact. In my past experience, Contribute normally gives a message that you don't have permissions to open the file once you are in the contribute application. This is the first time I have seen contribute give you the finger on the connection key when this was a problem. It may have been related to the directory path we were using (Local LAN, not FTP). At any rate, restoring the windows permissions for the one directory made the connection key work.