EXCEPTION_ACCESS_VIOLATION errors!
-
We get these errors when trying to script many of our tables using EM:
An error occurred during scripting.
Error 22272: SqlDumpExceptionHandler: Process 126 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Please note that we only get the error when trying to include the primary key (the tables do have primary keys) or full-text indexes (which we have none). If I simply script the drop and create commands for the table then I don't get this error.
And we get an error when trying to design those tables. I think this is the error we get then:
SqlDumpExceptionHandler: Process 92 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
All data is available and we seem to be able to modify it fine. We have at least 50 .dmp files. Does anyone know how to understand these files? Or do you know where there is an article that helps to understand them?
Has anyone seen problems like this before and do you know how to solve them? What can cause these problems?
We believe we are dealing with database corruption (probably on the indexes and not the tables) and/or bad (corrupt?) hard drive sectors. Any other ideas? Suggestions?
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems -
This sounds more like an install problem to me. Can you delete and reinstall EM on your workstation and clear it up? DOes everyone get the error, regardless of which workstation scripting is performed from?
-
Does this happen from multiple workstations? Try to narrow this down between the workstation and server.
If it's the server, if you can, detach dbs, uninstall, reinstall, then attach dbs.
If this isn't possible, I'd open a PSS call and then work with them to get the DMO libraries fixed. This is likely the place where you are having the problems.
Steve Jones
-
Are are you working in a mixed environment? (SQL7 and 2000)
Also, try the last SP you installed on that machine.
Finally other than scripting the DB is there anything in the dumps near that message. You can sometimes see exactly what it is referring to.
Does it occurr on specific objects or object types?
And make sure you check SQL Server Logs and Event Viewer logs for possible additional details or issues that may be related.
-
We get the same error from various workstations and from the server itself.
Also when I run this query:
SELECT f.SID,f.FID, getdate()
FROM tblDeleted d
INNER JOIN SQLServer1.dbDataBase.dbo.tblSF f ON f.FID = d.INum
WHERE Deleted = LEFT(CURRENT_TIMESTAMP,12)
I get the following error:
ODBC: Msg 0, Level 18, State 1
SqlDumpExceptionHandler: Process 53 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
[OLE/DB provider returned message: Unspecified error]
However, I can view the data in tblSF when a similar query is executed from SQLServer1.
We upgraded to SQL Server 2000 a few months ago and don't have any servers running SQL Server 7.0.
We have been and still are reviewing log entries and trying to make sense out of these .DMP files.
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems -
I've been looking at this problem and have just discovered that if I drop the primary key from a table I can't design in EM, then I can design it.
However, when I add the primary key again then I get the same error after closing the design view of the table and trying to reopen it.Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems -
If possible, can you supply the steps and table / index scripts.
Would like to try and reproduce the problem?
Thanks
-
Try DBCC CHECKDB and DBCC CHECKTABLE. Also, try a DBCC DBREINDEX on all the tables to see if may correct. Then do DBCC UPDATEUSAGE and sp_updatestats. Make sure you have a backup before you do anything. Finally, I see you are running SQL 2000, what SP level on the box and have you tried installing the latest or last SP you installed on the server?
However, when I add the primary key again then I get the same error after closing the design view of the table and trying to reopen it.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply