We are experiencing a backup problem on many of our database servers. We use one common server to store our backups. The backup of our databases is failing intermitantly. The strange thing is the backup file are partialy created, then we receive the following errors:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device ' olfesdbbackupoldrmsdbmsdb_db_200010101918.BAK'. Device error or device off-line. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operation terminating abnormally.
SQL Server error log shows:
BackupDiskFile::CreateMedia: Backup device ' olfesdbbackupoldrmsdbmsdb_db_200010101918.BAK' failed to create. Operating system error = 32(The process cannot access the file because it is being used by another process.).
The file was created with 0 KB prior to coming up with these messages.
TOLDR - 10/10/00 7:55:15 PM
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL Server Driver][SQL Server]Write on ' olfesdbbackupoldrdrvlocal1drvlocal1_db_200010101951.BAK' failed, status = 5. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operation terminating abnormally.
SQL Server error log shows:
BackupMedium::ReportIoError: write failure on backup device ' olfesdbbackupoldrdrvlocal1drvlocal1_db_200010101951.BAK'. Operating system error 5(Access is denied.).
Error 5 is 'Access Denied". It had written 24,902 KB to the file prior to coming up with this message. It was almost finished, as the normal size for this backup is in the 28,700KB range.
I created a backup plan for transaction logs only to run every 30 minutes. It works great for all databases except the Master and my main database scdb_v2.
The routine backups up the other 3 databases with no issue.
What does this error message mean ? We have SQL2000, with database FULL RECOVERY. Other databases on the server are fine. Backups stopped working a week ago. Can't remeber anything changing +++++++++++++++++++++++++++
The backup data in 'D:BackupTI backup.BAK' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Hello everyone! Looking for some insight here on database backups that fail.
We have many SQL servers that we maintain by storing Job/Maintenence Plan history on a central server, which then emails out daily reports to let us know what backed up last night and what didn't
This was easy to do in SQL 2000, not so much in SQL 2005. I have put together a query that gathers the info I need for the successes:
SELECT DISTINCT '00000000-0000-0000-0000-000000000001' AS Plan_ID, mpld.line1 as "Plan Name", bud.database_name as "Database", mpld.server_name, 'Backup Database' as Activity, mpld.succeeded, bs.backup_finish_date, DATEDIFF (MS,bs.backup_start_date,bs.backup_finish_date) as Duration, bs.backup_start_date, mpld.error_number, mpld.error_messageFROM msdb.dbo.sysmaintplan_logdetail mpld INNER JOIN msdb.dbo.backupset bs on (select convert(char(12),mpld.start_time,109))=(select convert(char(12),bs.backup_start_date,109))-- on bs.database_name=bud.database_name inner join msdb.dbo.bu_dbs bud on bs.database_name = bud.database_name WHERE mpld.succeeded = 1 and mpld.line2 like 'Backup%' and bs.type='d' and bs.backup_start_date > ( SELECT CONVERT(char(12), (GETDATE()-1), 109) ) ORDER BY bud.database_name DESC
But I am having trouble using a query to determine the databases the FAILED during backup. MSDB.BackupSet and MSDB.SYSMaintPlan_LogDetail really have nothing,because often times, even if a step in a Maint. Plan fails, the plan finishes reporting success.
Does anyone know of a good way to gather info about failed database backups?
The space allocated to the Log in question is 180 GB. During this time period I was running TLog backups every 5 minutes, yet the log continued to chew through to 80 GB used, even after the process was complete and a final TLog backup had been taken. It continued to stay very large until the Full backup was complete -- or something else that I'm unaware of completed. Like every other DBA I typically take a TLog backup to shrink the log, but what appeared to be the case here was the Full completed and it released the used log space. All said, will Transaction Log backups not free up the log during Full backups?
I've built SSIS package and made a job to execute it automatically but it always returns an error. The job returns OK but when we looked at the Log File viewer, it conatins this error log :
Key not valid for use in specified state
Failed to decrypt protected XML node "DTS Password" with error
What's wrong with the package ? Thanks in advance.
I wrote an application using Visual Studio 2005 beta 2 which uses a SQL Express .mdf file, included in the project, for the database. After installing Visual Studio 2005 RC and the SQL Express that comes with it (I followed all of the uninstall instructions first) I can no longer add a SQL Express database to any of my projects, nor can I open the SQL Express database in my original project. When I try either of these tasks, I get the "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed." I read the thread which dealt with this error, and changed the connection string for the database file that had worked before to User Instance = false. The moment I click Test Connection or OK, I get the error: "An attempt to attach an auto-named database for file C:<path to project>EngSQL.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share." (<path to project> is actually a full path, I didn't want to type the whole thing out. :) ). A search for this error turns up a solution of setting User Instance = false, which puts me in a catch 22 position.
I have log shipping set up between 2 SQL 2000 SP1 Servers on Win 2000. The db is small 10 meg, and when the restore job on the backup server fails I am getting "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." as the message, the maint paln on the primary server show no error. Anyone seen this before? The restore has worked 3 out of 5 times
Many a times see the below error in SQL Error log.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ]
Is this something to do here?
Note: If I run the below statement I know that the SQL Error log entry will go off, but wanted to know the real significance of this error?
CREATE LOGIN [NT AUTHORITYANONYMOUS LOGON] FROM WINDOWS
I am administering several SQL Servers running SQL Server 2005 SP2 Build 3042. I have a common maintenance plan that runs on each of the servers. The maintenance plan runs fine on all the servers except for one. On the one server the Database Integrity check fails with the following error:
Check Database integrity on Local server connection Databases: <list of databases> Include indexes Task start: 2008-02-21T00:05:42. Task end: 2008-02-21T00:05:46. Failed0) Alter failed for Server €˜XYZ€™
I created a test maintenance plan to just do the integrity check and selected one database only and this also failed with the same error message. I ran this test maintenance plan and configured it for each of the databases in question and it failed each time. If I run the DBCC manually against the databases they all report fine.
I read some of the post that talked about the €œAllow Updates€? being set incorrectly but that does not apply to my problem since my configured and run values are set to 0.
I have a re-indexing stored procedure,yester day night it got failed "Executed as user: CONNECTSRVmyadmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." what may be the reason..
[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
I am running the Sept CTP. I have created a SSIS package that pulls data from a text file and inserts into a database. When I run the package on the DB server it runs fine. I have moved the package the the web server (we are attempting to kick off the package from a web site) and we get connections errors. We are running the package using dtexec from the command line.
[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
when i right click and execute the package from the Management Studio, it runs fine, everytime. When i schedule a job to execute it, it fails, everytime.
"The package execution failed. The step failed."
i have made sure that the package and job ran using credentials with more than enough access to everything. Still, with no luck. PLEASE! I am at my wits ends here, and the boss is getting antsey...
Im trying to installed SQL SP1 and I get 'cancelled' status on the Database Services product.
If I open the SQL9_Hotfix_KB913090.log I see a bunch of 'Failed to read" errors. Im not very good at debugging SQL Logs, could you please assists me or tell me where to look?
02/15/2007 15:09:58.436 ================================================================================ 02/15/2007 15:09:58.436 Hotfix package launched 02/15/2007 15:09:59.405 Product discovery successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.405 SP Level check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Product language check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Product version check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Command-line instance name check completed during the install process 02/15/2007 15:09:59.421 Baseline build check completed during the install process 02/15/2007 15:10:21.892 Attempting to install instance: MSSQLSERVER 02/15/2007 15:10:21.892 Attempting to install target: DEV08 02/15/2007 15:10:21.892 Attempting to stop service: SQLSERVERAGENT 02/15/2007 15:10:25.893 Successfully stopped service: SQLSERVERAGENT 02/15/2007 15:10:25.893 Attempting to stop service: MSSQLServer 02/15/2007 15:10:27.893 Successfully stopped service: MSSQLServer 02/15/2007 15:10:27.893 Attempting to check for locked files: sqlrun_sql.msp 02/15/2007 15:10:27.909 Attempting to check for locked files: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp 02/15/2007 15:10:27.909 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 02/15/2007 15:10:39.520 MSP returned 1602: The user cancels installation. 02/15/2007 15:10:39.567 Successfully checked file: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp 02/15/2007 15:10:39.567 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 02/15/2007 15:10:39.567 Failed to read registry key: PendingFileRenameOperations 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall plhtfin.sql 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMsnapshot.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplmerg.exe 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5 C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0 C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll 02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 02/15/2007 15:10:51.256 The following exception occurred: User canceled patch install Date: 02/15/2007 15:10:51.256 File: depotsqlvaultsetupmainsetupsqlsesqlsedllfilegroup.cpp Line: 865 02/15/2007 15:10:51.256 Restarting SQL Service MSSQLServer since it was previously running 02/15/2007 15:10:51.256 Attempting to start service: MSSQLServer 02/15/2007 15:10:54.944 Successfully started service: MSSQLServer 02/15/2007 15:10:54.944 Restarting SQL Agent Service SQLSERVERAGENT since it was previously running 02/15/2007 15:10:54.959 Attempting to start service: SQLSERVERAGENT 02/15/2007 15:10:58.350 Successfully started service: SQLSERVERAGENT 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product Status Summary: 02/15/2007 15:10:58.350 Product: SQL Server Native Client 02/15/2007 15:10:58.350 SQL Server Native Client (RTM ) - Success 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Setup Support Files 02/15/2007 15:10:58.350 Setup Support Files (RTM ) - Success 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Database Services 02/15/2007 15:10:58.350 Database Services (RTM 1399 ENU) - Cancelled 02/15/2007 15:10:58.350 Reporting Services (SP1 2047 ENU) - Not Applied 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Integration Services 02/15/2007 15:10:58.350 Integration Services (SP1 2047 ENU) - Not Selected 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Client Components 02/15/2007 15:10:58.366 Client Components (SP1 2047 ENU) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: MSXML 6.0 Parser 02/15/2007 15:10:58.366 MSXML 6.0 Parser (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: SQLXML4 02/15/2007 15:10:58.366 SQLXML4 (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: Backward Compatibility 02/15/2007 15:10:58.366 Backward Compatibility (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: Microsoft SQL Server VSS Writer 02/15/2007 15:10:58.366 Microsoft SQL Server VSS Writer (RTM ) - Not Selected 02/15/2007 15:10:58.366
Hi, I'm trying to work out how to backup an ASP.NET 2.0 site which uses an SQL 2005 Express database located in the App_Data directory. It seems that the database file cannot be copied while in use so I guess that either leaves taking the site offline or maybe the database can be backed up to another location using a scheduled task? Any suggestions? Thanks, Dale
What backups options do you have if you do not have a tape drive connected to your SQL 7.0 Server ? Can you run a SQL Maintenance Plan and backup the databases to a remote server. If not, can ARCServe 2000 backup the SQL backups to another server with a tape drive ?
I've set up several backups in the past using the backup screen. I've also set up a Maintenance Plan to back up my database using MyDbName* where the * is the familiar suffix automatically generated by the system when the backup runs every night.
The trouble is that, even though I've deleted old maintenance plans and scheduled backups, they're not going away. Every morning, I see new nightly backups of old backups etc., in the backup folder. Furthermore, the maintenance plan I want to backup my database isn't creating a backup file.
How can I make the old backups stop running, and make sure the new backup runs? I've gone through everything and can't seem to find any residue of these old scheduled backups--yet they still run! Can anyone help?
We are having problems with our tape drives so we are attempting to back up our databases to disk. I have a whole server on the network I could use for this. When I use the backup that comes with SQL 7.0 it won't allow me to choose a network drive. It looks like it must be a local drive. Is there a way around this so I could back it up to this other server. I jave 32 gig available on the server which would be plenty. We don't have enough disk space on the local drives to back it up. We have been having problems with our current tape drive company Exabyte. Does anyone have any recommendations. We are thinking of switching to another company.
I currenntly backup several databases to thier own unique device. Each backup is executed as a full backup (databases are small)and they are set to expire after 7 days. I checked my devices after 7 days and they continue to grow in size - is this right? I expected the device size to hold constant once I had a rolling seven days of backup (The databases don't change in size from day to day) Any ideas?
I'm using the database maintenance plans to backup my databases. We are backing them up to tape. Is there a way within the database maintenance plan to tell it to format the tape instead of appending it to the tape.
I am trying to make sure I have my backups scheduled correctly and in the correct spot. We have a tape drive on the server which is backing up the databases each night. The logs I have them currently being backp up once an hour to disk. My question is would it better to have the logs back up to the tape drive or to disk. The server where I'm backing up the logs to has 2 drive C and D. Where D contains the data and C contains the application/program files. I'm assuming I wouldn't want it on D since if there was a crash with that drive and we lost the data we wouldn't be able to get the logs for that day so it would be better to put it on C. What are most people doing to backup there logs. At the end of the day after a full backup I clear the device that contains the log backups. It this good practice?
How do you backup to a remote drive? The book says that inorder to backup to a remote drive, you need to log on with a domain NT account with administrative privileges. I am unable to log on with a domain account and backup to a mapped drive.
For example, S1 and S2 are two servers in the domain D1. The NT domain administrative account is A1. I need to backup a database D1 on S1 to a location on S2. For this I do the following. On S1, sp_addumpdevice 'disk','dump_dev','s2sharenamefilename.bak' On executing, I get,
(1 row(s) affected) 'Disk' device added.
Then when run the command, backup database D1to dump_dev I get the following error,
Server: Msg 3201, Level 16, State 1, Line 1 Cannot open backup device 'dump_dev'. Device error or device off-line. See the SQL Server error log for more details. Server: Msg 3013, Level 16, State 1, Line 1 Backup or restore operation terminating abnormally.
The event log shows the following error message:
BackupDiskFile::CreateMedia: Backup device 's2sharenamefilename.bak' failed to create. Operating system error = 1326(Logon failure: unknown user name or bad password.).
Please let me know how to back up to a mapped drive using TSQL and Enterprise Manager.
I have a dump device configured to append the backup file each time a backup is run. This file has grown extremely large. Im looking for a way to go into the file and delete all but the last 2 or 3 backups. Is there a way to do this?
Hello, is there any backup software (archserve,ultraback) that has a sql agent for 7.0 ? I have not found one yet. Charlie Principato Dialamerica Marketing,Inc.
I have a SQL2K/SP3 database with an MDF of 4GB and an LDF of .5GB. If I do a backup using Enterprise Manager, whether manually or via a DB Maintenance Plan, I get a .BAK of approx. 2GB. If I do a backup using: USE master EXEC sp_addumpdevice 'disk', 'RAMScopyBAK', 'F:MSSQLBACKUPRAMScopyRAMScopy.BAK' GO
BACKUP DATABASE RAMScopy TO RAMScopyBAK GO
I get a .BAK of 24GB !!!
In the end I want a T-SQL step to be part of a SQA job that will back up the database, thus the use of the dumpdevice command. I could create a maintenance plan, disable the jobs it creates, and then start them via sp_start_job, but this is just an example of a systemic problem; i.e. I'd have to do individual maintenance plans for more than one database.
For a lot of smaller/medium sized systems that I administer, I tend to use SQL Server to backup to a backup device and then let the normal system backups backup the dump files to tape.
However, I am taking on a new system with approx 900Gb of data. We dont want to buy another 900Gb of disk to secure the databases ! I have found the SQL Agents in Arcserve 2000 to be unreliable to say the least. (we dont want to stop the SQL Services either)
Would anyone recommend alternative software to backup large databases.
