Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

iFolder on Windows 7 will not connect

25 views
Skip to first unread message

Mike Gerst

unread,
Jan 28, 2010, 4:59:36 PM1/28/10
to
We have a working ifolder 3.8 server.
Windows XP workstations can login and iFolder syncs.
No Windows 7 users (same users as have working XP workstations) can sync.
 
Error on client is:
 
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.ArgumentNullException: Key cannot be null.
Parameter name: key
   at System.Collections.Hashtable.ContainsKey(Object key)
   at Simias.WebState..ctor(String DomainID)
   at Simias.DomainServices.DomainAgent.Login(Uri host, String domainID, NetworkCredential networkCredential, Boolean calledRecursive)
   at Simias.DomainServices.DomainAgent.Attach(String host, String user, String password)
   at Simias.Web.SimiasService.ConnectToDomain(String UserName, String Password, String Host)
   --- End of inner exception stack trace ---
 
Any ideas on a solution?
 
Mike
 
 
 

Robert H Jenson

unread,
Feb 2, 2010, 5:54:10 PM2/2/10
to
Since no one has replied to Mike, let me add some additional information to his post.
 
We installed iFolder 3.7 on the server and installed the client on three Windows 7 (32 bit) machines that we had just acquired and it worked great. A couple weeks later when we were just about ready to roll it out to our users, it quit working on all three machines. It continued to work great on Windows XP machines we have it installed on.
 
We upgraded to 3.8 partially in the hope that it had better support for Windows 7, but nothing changed. At the same time, our department has been rolling out a new anti-virus that includes a firewall and they have been making some adjustments to the firewall settings. All three of our Windows 7 computers have the new anti-virus and there is a possibility that a change in the firewall policy has caused out problem. We have not tried it on another Windows 7 computer, because we don't have one, but we may find one of our users that does and is not running the firewall if that could be the problem.  
 
We are still delaying our roll out trying to resolve this issue and would appreciate any feedback you may have.
0 new messages