Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cgourlay
Starting Member
4 Posts |
 Posted - 2007-10-08 : 13:19:52
|
| Hi.Intermittently, the following error has been displayed when a SQL job on our box (SQL Server 2000 Service Pack 4 running on Windows 2000) runs.'A floating point exception occurred in the user process. Current transaction is canceled.' The error number given is 3628 though I've also seen a 4xxx number (not at machine at the moment so cant be precise for the latter).The intermittent problem over the last two days has become more regular and now does not appear to be related solely to the SQL job. For example, when connecting to the box using my local copy of SQL 2005 Management Studio and I attempt to browse the database objects I get this problem.To the best of my knowledge, this server has not had any software installed on it and/or nothing has changed on it recently.It has now got to the point that this particular job no longer runs. The job in question, in case this is significant, is a vanilla stored proc that returns data using OPEN ROWSET to communicate with an Access database (this connectivity has been verified to be okay, in that other similar jobs all run just fine)If anybody can shed some light and/or point me in the right direction I would be extremely grateful.CheersCG |
|
|
Kristen
Test
22859 Posts |
|
|
cgourlay
Starting Member
4 Posts |
Posted - 2007-10-09 : 05:12:22
|
| Hi.I tried as you suggested and DBCC confirms there are no issues with each of the databases in the server.The other article you referred to - does not resolve my problem either.Can you offer any further advice?If there is anymore information I can provide then please do not hesitate to ask. |
 |
|
|
cgourlay
Starting Member
4 Posts |
Posted - 2007-10-09 : 06:10:13
|
| Hello again.To answer my own question. I have applied a hotfix that should have been applied after service pack was installed and it _seems_ to have resolved the problem.Thanks for the help received - it is very much appreciated.CG |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-09 : 06:11:23
|
| Try this search in Google (exactly as presented here)3628 "A floating point exception occurred in the user process" "Current transaction is canceled"The things I would try are:Turn of parallelism for the query, or the server if you cannot easily provide a HINTTry the query with different bits of the WHERE clause / JOINs commented In/Out. See if any work.Try reducing the data processed. e.g. if you are looking for "A-Z" then try "A-N". If not error try "N-Z". If error split that block in half and try again. You may be able to isolate it to a specific record, which might lead you to the solution. or isolate to a "volume" of data, in which case you may be able to UNION ALL two halves of the data where a single query of all data fails.Kristen |
|
|
|
|
|
|
Floating Point Exception