ClientServer app worked under XP but not Windows 7
-
Using .NET 3.5, SQL Server 2005 and C# 2008 Express. Server creates instances of the server-side code. Worked fine under XP. Upgraded to Windows 7 and the remote calls hang. If I add code to my client which accesses the database directly (inserted before it does the remote call, it works. But not remotely through the server. Is there something I should know about SQL Server/.NET/Windows 7?
-
Using .NET 3.5, SQL Server 2005 and C# 2008 Express. Server creates instances of the server-side code. Worked fine under XP. Upgraded to Windows 7 and the remote calls hang. If I add code to my client which accesses the database directly (inserted before it does the remote call, it works. But not remotely through the server. Is there something I should know about SQL Server/.NET/Windows 7?
-
The information you provided is not enough. What is your app doing and where does it hang ? And what does remote call mean, WCF, Web Service or a remoting component ?
Not clued up on terminology, so will give examples. The first step that the app does is collect the username and logon, and then check if they are in the database. I am using interfaces to the server-side code, and the server creates instances of the code like this
UserList insUserList = UserList.Instance;
ObjRef refUserList = RemotingServices.Marshal(insUserList, "UserList");The client does a call like this
private IUserList rmUserList;
rmUserList = (IUserList)Activator.GetObject
(typeof(IUserList),
System.Configuration.ConfigurationManager.AppSettings["UserListUrl"]);
logonReturnValue = rmAllUserList.Logon(PasswordString);UserListUrl is tcp://localhost:50050/UserList On the server side it does (through calls to a pool of common routines, also on the server.
cnStr = "Data Source='NIGEL-PC\\SQLEXPRESS';" +
"Trusted_Connection=true;" +
"Database=timesheet";
cn = new SqlConnection(cnStr);
cmd = new SqlCommand("", cn);
da = new SqlDataAdapter();
cmd.CommandText = "SELECT Password " +
"FROM UserList " +
"WHERE UserID = 12 ";
da.SelectCommand = cmd;
tmpDS = new DataSet();
da.Fill(tmpDS, "Data");If I run the above code snippet in ClientLogon it works. If I allow it to do the remote call, it hangs.
-
The information you provided is not enough. What is your app doing and where does it hang ? And what does remote call mean, WCF, Web Service or a remoting component ?
More info: On the server side, I created a routine that only returns a string "OK", with no data access. Still hangs, so it is definitely the remoting bit, not the data access.
-
More info: On the server side, I created a routine that only returns a string "OK", with no data access. Still hangs, so it is definitely the remoting bit, not the data access.
If anyone is interested, the problem was with Comodo Internet Security, even when diasabled.