| Author |
Topic |
|
csolis
Starting Member
10 Posts |
 Posted - 2007-07-20 : 11:12:20
|
| Hello,Recently an old server was migrated from SQL 2000 to SQL 2005. Intallation was fresh on a brand new server as well but the data converted to SQL 2005. Running on a Dell PE 2950 with Dual Core Xeon 5130 processors. Installation seemed to have gone well, but since the installation, Clients accessing the application running on the SQL server have been getting random errors stating "TagRead I/O Error" (1337) and then they get kicked out of the application. Immediately the vendor mentioned that it was a Network issue and that I needed to verify that. I have disabled TCP TOE on the server, loaded the latest drivers. The errors appeared to be more frequent prior to loading SQL 2005 SP2, but still continue to see the errors sporadically. I have done a ful check on the network and everything appears to be normal, no packet loses of ay kind. I cannot seem to find anything pertaining that Specific error message. I hoping someone here can give me a hand because it has been happening for quite sometime.Thanks. |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-20 : 11:21:55
|
| Checked with Dell for new driver? |
 |
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-20 : 11:46:37
|
| At first I had loaded a new driver from Dell but the problems continued to happen. Then after disabling TCP TOE I was able to load a newer driver from the Broadcom site. The date on the driver was from May 27th 2007 so I figured it would fix the problem all together if it was a network issue. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-22 : 16:56:39
|
| Did you see any error in sql server log? I'll set trace with profiler to see if app request reaches sql server at all. |
|
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-23 : 02:06:30
|
| The SQL server log does not really show any errors. The only error I did notice and only for a couple of clients was the 14856 - 8 which is related to login failure. The weird thing about those clients is that they are actually logged on with no issues when the error is generated. One thing I did forgot to mention is that the old server's IP address was assigned to the new server with a different host name. The old SQL 2000 box is still operational except that the IP address was changed. At first I also thought it might have been a conflict with the old server but I have checked everything and there are no traces of the old IP address on the old server. Everyone keeps telling me it is a Network issue but I can't seem to find anything wrong with the network. All the other servers are running just fine which is why it does not make sense that I would be having problems just the new SQL 2005 server. What do I need to look for in the profiler? I have never used it for.Thanks. |
|
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-23 : 02:10:19
|
| Oh and additionally, all users are able launch the application and able to login to it. But after being logged on users get the "TagRead" error or when the application is minimized for a while the error also comes up and they kicked out and they have to re-launch app and log back in. |
|
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-23 : 13:02:20
|
| Hello RMIAO,I ran the SQL Profiler and I noticed a lot of the messages below:- <Event id="14" name="Audit Login"> <Column id="1" name="TextData">-- network protocol: TCP/IP set quoted_identifier on set arithabort off set numeric_roundabort off set ansi_warnings on set ansi_padding on set ansi_nulls on set concat_null_yields_null on set cursor_close_on_commit off set implicit_transactions off set language us_english set dateformat mdy set datefirst 7 set transaction isolation level read committed</Column> <Column id="9" name="ClientProcessID">2552</Column> <Column id="11" name="LoginName">NI_USER</Column> <Column id="10" name="ApplicationName">Delegator Service</Column> <Column id="12" name="SPID">79</Column> <Column id="14" name="StartTime">2007-07-23T09:48:00.39-07:00</Column> </Event>- <Event id="13" name="SQL:BatchStarting"> <Column id="1" name="TextData">exec PROC_IS_BKG_FULLOVERLAY 30061,7706,7706</Column> <Column id="9" name="ClientProcessID">2552</Column> <Column id="11" name="LoginName">NI_USER</Column> <Column id="10" name="ApplicationName">Delegator Service</Column> <Column id="12" name="SPID">79</Column> <Column id="14" name="StartTime">2007-07-23T09:48:00.39-07:00</Column> And Also the following "exec_sp_Reset"- <Event id="10" name="RPC:Completed"> <Column id="11" name="LoginName">NI_USER</Column> <Column id="15" name="EndTime">2007-07-23T09:48:02.297-07:00</Column> <Column id="2" name="BinaryData">00000000000000002600730070005F00720065007300650074005F0063006F006E006E0065006300740069006F006E00</Column> <Column id="10" name="ApplicationName">Newmarket Delphi</Column> <Column id="12" name="SPID">76</Column> <Column id="14" name="StartTime">2007-07-23T09:48:02.297-07:00</Column> <Column id="16" name="Reads">0</Column> <Column id="18" name="CPU">0</Column> <Column id="1" name="TextData">exec sp_reset_connection</Column> <Column id="9" name="ClientProcessID">2976</Column> <Column id="13" name="Duration">18</Column> <Column id="17" name="Writes">0</Column> Not sure if it means anything but I am hoping it does to you.Thanks. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-23 : 13:50:06
|
| Only tell that user is connected. Regarding ip address, did you chech all dns and/or wins servers on your network? Are they clean? Tried connect to sql server with ip address instead of host name? |
|
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-23 : 15:10:39
|
| Hello,I am able to ping the server by FQDN from any workstation with no problems. I have tried entering the IP address and Host name and still no luck. I have also tried named pipes last week. Today I tried the Fully qualified domain name for the first time and currently awaiting if it works out or not. Today it just happened to randomely to at least 4 users. These errors are not consistent at all. |
|
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-23 : 15:14:12
|
| One more thing,I just checked the SQL server log and saw the following message for one user. Checked with the user and he mnetioned that he's logged and has not had any issues today but yet the log says that he failed to logon....It is the right SQL login user and password. MessageLogin failed for user 'ni_report'. [CLIENT: 10.111.52.97] |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-23 : 16:37:16
|
| Is it sql authentication? |
|
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-25 : 15:24:22
|
| We are using Mixed authentication. Both SQL and Windows. I replaced the NIC with an intel Pro 1000 server adapter and the issues continue to happen. So I guess it is safe to say that it is not a network issue since it is happening to with either network adapter. It is weird because of how inconsistent it is. The vendor keeps saying that it is a network issue because the client is dropping the connections. Could it be something related to connection Pooling? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-25 : 15:41:43
|
| Did you check mdac version on sql server and client machines? |
|
|
|
csolis
Starting Member
10 Posts |
Posted - 2007-07-26 : 01:44:12
|
| The MDAC version on the workstations is 2.8. The one that came with Windows XP SP2 which I thing is actually 2.8 SP1? The Server is running Windows 2003 Server R2. Not sure which version the server is running. How would I know if the application is not very friendly with a Multi-Processor environment? I know SQL 2005 is supposed to be but the application I don't know. it is a very colorful application, lots os color and bright screens. Also I am currently on SQL 2K5 SP2 (Build 3152). How important are the new post SP2 hotfixes? I know there is a new hotfix that came out sometime in June 2007 I think. The vendor has had me going on circles, diabling the firewall service, disabling power management for client Net Adapters, trying IP address and host name on ODBC data sources, etc. I told them those same clients never had an issue with the previous server running SQL 2000. Any advise is greatly appreciated.Thanks RMIAO. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-26 : 23:08:54
|
| Have no idea now. By the way, did you have same issue with sql tools? |
|
|
|
|
TagRead I/O errors