4rg
asked on
SQLDump files filling up hard drive
Hello Experts,
Just want to say that I am no SQL expert by any means so any help is most appreciated. I have a 2003 R2 Standard Server running SQL. It has an instance for Webroot and It had another database in it that is no longer used so there are two instances. In the MSSQL.2 Log folder (the one no longer used) It is filling up with mdmp, log and txt dump files every 2 minutes and filling the hard drive.
I have done all the windows automatic updates as I saw that in another question but I did not see any sql updates occur (and it is still happening). I do not know the version or how to determine it so I can download the proper file to update if that is even the issue. I am attaching the log file and txt files.
SQLDump10007.txt
SQLDump10007.log
Just want to say that I am no SQL expert by any means so any help is most appreciated. I have a 2003 R2 Standard Server running SQL. It has an instance for Webroot and It had another database in it that is no longer used so there are two instances. In the MSSQL.2 Log folder (the one no longer used) It is filling up with mdmp, log and txt dump files every 2 minutes and filling the hard drive.
I have done all the windows automatic updates as I saw that in another question but I did not see any sql updates occur (and it is still happening). I do not know the version or how to determine it so I can download the proper file to update if that is even the issue. I am attaching the log file and txt files.
SQLDump10007.txt
SQLDump10007.log
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
angellll,
oops, meant to mention that Backup Exec is working fine.
oops, meant to mention that Backup Exec is working fine.
ASKER
rrjegan17,
I found this site but I must be missing something because it just says sql server 2005 SP1. That still does not tell me whether it is a retail version or express. How do I determine that? http://www.sqlteam.com/article/sql-server-versions
I found this site but I must be missing something because it just says sql server 2005 SP1. That still does not tell me whether it is a retail version or express. How do I determine that? http://www.sqlteam.com/article/sql-server-versions
ASKER
not that I would install on an assumption but looking at the sp3 downloads available for 2005 express, there are two choices.
SQLEXPR.EXE and SQLEXPR32.EXE and the page says to "Download the files most appropriate for you." That's a world of help.
SQLEXPR.EXE and SQLEXPR32.EXE and the page says to "Download the files most appropriate for you." That's a world of help.
>> SQLEXPR.EXE and SQLEXPR32.EXE and the page says to "Download the files most appropriate for you."
SQLEXPR32.EXE is a smaller package that can be used to install SQL Server Express on 32-bit operating systems only. The larger SQLEXPR.EXE package supports installing onto both 32-bit and 64-bit (WOW install) operating systems. There is no other difference between these packages.
Hope this helps in identifying your version and edition:
SELECT serverproperty('edition'), SERVERPROPERTY('productlev el')
Kindly revert if any thing needs to be clarified
SQLEXPR32.EXE is a smaller package that can be used to install SQL Server Express on 32-bit operating systems only. The larger SQLEXPR.EXE package supports installing onto both 32-bit and 64-bit (WOW install) operating systems. There is no other difference between these packages.
Hope this helps in identifying your version and edition:
SELECT serverproperty('edition'),
Kindly revert if any thing needs to be clarified
ASKER
Dear Experts,
I updated SQL, it was express version. No help. DMP files kept accumulating. It appears it was the Backup Exec instance that was having the issue. I had to uninstall SQL completely then repair Backup Exec to get it fixed. I am awarding points anyways for all the help given.
Thank you to all experts.
I updated SQL, it was express version. No help. DMP files kept accumulating. It appears it was the Backup Exec instance that was having the issue. I had to uninstall SQL completely then repair Backup Exec to get it fixed. I am awarding points anyways for all the help given.
Thank you to all experts.
ASKER
I thought I had closed this question and awarded points, but I must have done something wrong.
Just as well as the problem started again about an hour after I left.
Here is more information I have gathered since then. I believe it is a Backup Exec 11D issue now.
First of two Application Events. ID 57345
Database Exception Context:m_QueryTimeoutInSe conds=300 sql={CALL dbo.[AutoClearAlert](?,?,? )} Error:-536837662: :: -2147217900:Internal Query Processor Error: The query processor encountered an unexpected error during execution. :: DB Error Set 0: native=0x21b6 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Internal Query Processor Error: The query processor encountered an unexpected error during execution.
Second event, both have ID 57345.
Database Exception Context:AutoClearAlerts: sp ClearAutoAlert Error:-536837662: :: -2147217900:Internal Query Processor Error: The query processor encountered an unexpected error during execution. :: DB Error Set 0: native=0x21b6 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Internal Query Processor Error: The query processor encountered an unexpected error during execution.
They are occuring every 2 minutes and I also have a .mdmp, .log and .txt file being created in the
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG"
folder every two minutes. The mdmp and .txt files range from 1,262 MB to 3,045 MB generally but occasionally there is one that is 15,878 MB or so. As you can imagine it amounts to 1-2 GB every day or so.
My client is running Backup Exec 11D Rev. 7170 for Windows Server and the remote agent on another server. Service Pack 4 was installed by LiveUpdate on 7-29-09. The backup is working just fine. There are no Alerts within Backup Exec indicating any problems.
I have Windows Server 2003 R2 Std Edition SP2. 47.5 GB free when the log file is clean. Just using the SQL database that is installed with Backup Exec.
I have uninstalled SQL and all instances and then repaired Backup Exec and the only thing that happened was that the logs used to be under an MSSQL.2 folder and now as indicated above are under an MSSQL.1 folder
I checked in eventid.net and the Symantec Forums and found nothing close enough to count.
If you think I should start a new question and award the points from this one, please advise.
Thanks to all,
4RG
Just as well as the problem started again about an hour after I left.
Here is more information I have gathered since then. I believe it is a Backup Exec 11D issue now.
First of two Application Events. ID 57345
Database Exception Context:m_QueryTimeoutInSe
Second event, both have ID 57345.
Database Exception Context:AutoClearAlerts: sp ClearAutoAlert Error:-536837662: :: -2147217900:Internal Query Processor Error: The query processor encountered an unexpected error during execution. :: DB Error Set 0: native=0x21b6 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Internal Query Processor Error: The query processor encountered an unexpected error during execution.
They are occuring every 2 minutes and I also have a .mdmp, .log and .txt file being created in the
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG"
folder every two minutes. The mdmp and .txt files range from 1,262 MB to 3,045 MB generally but occasionally there is one that is 15,878 MB or so. As you can imagine it amounts to 1-2 GB every day or so.
My client is running Backup Exec 11D Rev. 7170 for Windows Server and the remote agent on another server. Service Pack 4 was installed by LiveUpdate on 7-29-09. The backup is working just fine. There are no Alerts within Backup Exec indicating any problems.
I have Windows Server 2003 R2 Std Edition SP2. 47.5 GB free when the log file is clean. Just using the SQL database that is installed with Backup Exec.
I have uninstalled SQL and all instances and then repaired Backup Exec and the only thing that happened was that the logs used to be under an MSSQL.2 folder and now as indicated above are under an MSSQL.1 folder
I checked in eventid.net and the Symantec Forums and found nothing close enough to count.
If you think I should start a new question and award the points from this one, please advise.
Thanks to all,
4RG
ASKER
I found the answer in a Symantec Forum.
Following the below link and the instructions therein solved the problem.
http://entsupport.symantec.com/docs/318243
Thanks to all the experts who tried to help.
I am awarding points (split), just because.
Following the below link and the instructions therein solved the problem.
http://entsupport.symantec.com/docs/318243
Thanks to all the experts who tried to help.
I am awarding points (split), just because.
ASKER
See my last entry for solution, solved myself. I am sure it was because I was not clear or sure of why it was happening. If I had a clue what was going originally, I am sure they could have helped me fix it.
ASKER
angellll:
I have a lot of Backup Exec "Information" entries, (Maybe it is being used)
Source: Backup Exec Category: (65535) Event ID: 57345
Database Exception Context:AutoClearAlerts: sp ClearAutoAlert Error:-536837662: :: -2147217900:Internal Query Processor Error: The query processor encountered an unexpected error during execution. :: DB Error Set 0: native=0x21b6 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Internal Query Processor Error: The query processor encountered an unexpected error during execution"
I have been looking for this on Symantecs site but am having a hard time finding anything that looks right.