| Author |
Topic |
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
 Posted - 2002-04-01 : 19:41:54
|
| I just returned to see my live snitz forums return this message. Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler: Process 74 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. The line of code that errors is when I open the recordset. I suddenly can not return any data from a specifc table --> FORUM_REPLY. I can not select data from the table FORUM_REPLY at all, not through QA both locally and remotely. I have no idea where to go with this. Can anybody help me???? I've gotta fix this ASAP as it is live!! Thanks alot Mike |
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-04-01 : 23:55:56
|
| you can check the table thru DBCC CHECKTABLE , if there are problems claim it thru dbcc cleantable.i would suggest you to do a DBCC CHECKDB too.If there are any indexes on the table , drop and recreated them. you never know the indexes might be damaged .HTH-------------------------------------------------------------- |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-04-02 : 00:41:15
|
| http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=13961Call MS Support ASAP-Chad |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2002-04-02 : 02:24:32
|
| DBCC CHECKTABLE and DBCC CHECKDB returned no errorsI have 1 clustered index on TOPIC_ID in the table FORUM_REPLY, I indexed the database using the wizard. Is there an easy way to drop and recreate with QA?? The customer I am doing this for does not have a license he is on a shared SQL server, can I still call MS?Thanks alot! mike |
|
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-04-02 : 03:06:54
|
| i remember Chad repeatedly telling about Excess_Access_violation errors are actually bugs. he had even suggested it to be listed in FAQ.newayz you can ask the provider to report the matter to MS.for time being query sysindexes table and get the name of the index .select name from sysindexes where id=object_id('tablename')Drop all the index and recreate it.you can even try dbcc reindexThough this is just a try . ultimately you might have to contact MS.HTH-------------------------------------------------------------- |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2002-04-02 : 04:03:16
|
thanks guys.. if anyone else has anythign to add i'd die to hear it as contacting microsoft on this one doesnt look possible right now at leastpleasepleaseplease make this problem go away  |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2002-04-03 : 00:12:32
|
If anybody thinks they can fix this I am willing to pay. I'm not a SQL guy I'm learning this as I go.Im in a major jam, any help is greatly appreciated. I'm racking my brains here. |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-04-03 : 00:25:35
|
| Couple things:-Reboot the SQL Server. If you can't reboot, at least restart the MSSQLServer service.-Download and install the latest MDAC components on both the SQL Server and client machines that are accessing it. Do this even if you already have the latest drivers, reinstalling them might help. You can get them here:http://www.microsoft.com/data/download.htmGet either MDAC 2.6 SP1 or MDAC 2.6 RTM, or get MDAC 2.7 if you're using WinXP. REBOOT THE MACHINE AFTER INSTALL, WHETHER IT FORCES YOU TO OR NOT-Apply the latest service pack if you haven't already; SP3 for SQL 7.0, SP2 for SQL 2000 |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2002-04-03 : 00:52:21
|
| robvolk first off thanks.. you've instilled some hope in my eyes I just downloaded and re-installed the drivers to no prevail ( with a reboot) .. It is SP2 SQL 2000any idea what the next step may be?Thanks,Mike |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-04-03 : 01:10:31
|
| I really think you should take Chad's advice and call MS. None of us can get to your server so it is probably your best option.Here is a thought, if it is only happening on one database, try making a duplicate of the database and DTS ing all the data into it. See if you can query the new copy.Damian |
|
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-04-03 : 01:17:44
|
| I fully agree with Merkin, all the solutions we are trying to give are shot in the dark. -------------------------------------------------------------- |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2002-04-03 : 01:22:40
|
| thanks guys .. merkin: I am trying this as I write this message. I will post how it goesthe real problem here is that I do not have the required information to contact microsoft..nazim: I still appreciate your help and everyone elses.. thanks again |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-04-03 : 01:43:24
|
| The required information, is a valid product ID, and a Credit Card. (The Credit Card charge will be refunded).Other than that you will have to just send the stack dump.The only other way to "fix" the problem is to determine exactly what causes it. Get it down to the smallest reproducable example, and find a "workaround" for that small piece. Figure out another way to do the same thing.Like I have repeatedly said, AVs are bugs in the product. There is no way that reinstalling, moving to a different server, etc... is going to help, unless there is something weird about the original installation.If this has worked in the past, you might try going back an SP, as it may be a regression bug.Your best bet though is to call MS Support. If the problem is known, they will be able to give you the best work around or even a fix. If not, you can help improve the product, by alerting them to the issue, so they can write a fix.-Chad |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2002-04-03 : 03:52:45
|
| Thanks for all the help guys!!I got it going!.. Here's what I had to doI restored a copy of the backup database, which happend 5 hours before the table crashed, to my local machine. I then DTS'ed the data into the old corrupt database. Everything works fine now it appears! phew... I thought I was doomed..... actually, am I doomed to face this problem again?cheersmike |
|
|
|
|
EXCEPTION_ACCESS_VIOLATION