-
1. Re: Contribute cannot find the website files on the server
Krishna Prasad B V Oct 7, 2010 2:56 AM (in response to edmcgo)Hi,
Can you connect directly to the website through LAN connection, from the new machines? Also, can you try mapping the network drive first, and then using the connection key?
Hope this helps.
-
2. Re: Contribute cannot find the website files on the server
edmcgo Oct 7, 2010 6:00 AM (in response to Krishna Prasad B V)thank you for replying.
Yes and Yes. It still does not work with the connection key.
If I have the user go thru a manual connection via the wizard, they can connect successfully, but their role is not set and it is messy.
-Ed
-
3. Re: Contribute cannot find the website files on the server
Krishna Prasad B V Oct 7, 2010 6:28 AM (in response to edmcgo)Hi,
Is the folder mapping done based on drive letter? That is, does the connection information for the website look like Z:\<website_folder>. The 'Z' can be any drive letter.
-
4. Re: Contribute cannot find the website files on the server
edmcgo Oct 7, 2010 7:03 AM (in response to Krishna Prasad B V)yes, we use the O: drive.
-
5. Re: Contribute cannot find the website files on the server
Krishna Prasad B V Oct 7, 2010 7:21 AM (in response to edmcgo)Hi,
Then in the new machines, can you map the network drive to O: once and then in Contribute try creating connection using the connection key?
-
6. Re: Contribute cannot find the website files on the server
edmcgo Oct 7, 2010 8:39 AM (in response to Krishna Prasad B V)Hi
Their O: drive is mapped, then they open the key sent via email, then Contribute CS4 launches, goes into the Wizard, then they fill out everything, type the 1-time password, and then they get the error message "Contribute cannot find the website files on the server".
The O: drive is still connected. The files in their web folder are accessible read/write. The _mm folder is accessible in read/write.
thanks for helping,
Ed
-
7. Re: Contribute cannot find the website files on the server
edmcgo Oct 18, 2010 1:40 PM (in response to edmcgo)PROBLEM SOLVED:
We removed their ROLE from the site and re-created it (using the same settings), sent them a brand new connection key and it worked. So, there was something corrupt or wrong in the role. Part of the problem is that two of us create roles and connection keys and there could be something different with our systems or settings. Not sure, but the removal/creating of the role did the trick.
-Ed

