KJB
Member
Hi
Does anyone out there have any suggestions please!
A fortnight ago we migrated our Enterprise Server and database from iSeries with DB2/400 to a clustered (active/passive) Wintel solution running Windows 2003 with SQL Server 2000 at SP3a. The database sits on a SAN with fibre connections to the servers.
Since then we have seen many instances where applications are hanging and the users have to crash out of EnterpriseOne and start again. We are also, in some instances, seeing ODBC timeouts. The problem is most evident within the Customer Service applications.
We are on EnterpriseOne 8.10 with Tools 8.93.N1. User access is through two farms of (W2K) Terminal Servers and fat clients (W2K & XP). Both terminal server and fat client users are experiencing the problem.
I've checked all the obvious things I can think of......
Thanks in advance.
Does anyone out there have any suggestions please!
A fortnight ago we migrated our Enterprise Server and database from iSeries with DB2/400 to a clustered (active/passive) Wintel solution running Windows 2003 with SQL Server 2000 at SP3a. The database sits on a SAN with fibre connections to the servers.
Since then we have seen many instances where applications are hanging and the users have to crash out of EnterpriseOne and start again. We are also, in some instances, seeing ODBC timeouts. The problem is most evident within the Customer Service applications.
We are on EnterpriseOne 8.10 with Tools 8.93.N1. User access is through two farms of (W2K) Terminal Servers and fat clients (W2K & XP). Both terminal server and fat client users are experiencing the problem.
I've checked all the obvious things I can think of......
Thanks in advance.