Database backup failure:Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Database backup failure:Possible failure...

Database backup failure:Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection...

Rate Topic

Display Mode

Topic Options

Author

Message

jeet_personal

Posted Saturday, May 30, 2009 11:56 AM

Grasshopper

Group: General Forum Members
Last Login: Wednesday, December 21, 2011 11:20 AM
Points: 17, Visits: 96

The backup job in the MP is failing due to the following reason:

Executing the query "BACKUP DATABASE [RestoreAdminData_Forest] TO DISK = N'I:\\backup\\RestoreAdminData_Forest\\RestoreAdminData_Forest_backup_200905272100.bak' WITH NOFORMAT, NOINIT, NAME = N'RestoreAdminData_Forest_backup_20090527210006', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Any iDea why this is happening? the databases are in SIMPLE recovery mode

Post #726231

Jeffrey Williams 3188

Posted Saturday, May 30, 2009 1:55 PM

SSCarpal Tunnel

Group: General Forum Members
Last Login: Friday, May 17, 2013 11:21 AM
Points: 4,317, Visits: 9,216

This is happening because you are backing up across the network and there is a blip on the network. The ideal solution is to backup locally and copy to the network storage instead.

However, that may not be an option - so you need to identify the OS error (64, 995, etc...) and search the support site at Microsoft for possible fixes.

Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

Post #726244

Shawn Melton

Posted Sunday, May 31, 2009 11:37 PM

Right there with Babe

Group: General Forum Members
Last Login: Saturday, May 11, 2013 8:56 PM
Points: 754, Visits: 1,891

N'I:\\backup\\RestoreAdminData_Forest\\RestoreAdminData_Forest_backup_200905272100.bak'

Are you trying to run this job on the SQL server or through SSMS on your client machine? Have you tried going straight to it with using the UNC path, just "\\\backup..." instead of the drive letter? Do you have other jobs pointing to this network share?

--------------------------------------------------------------
Shawn Melton
@wshawnmelton

Post #726418

john_1726

Posted Tuesday, September 15, 2009 4:03 PM

Forum Newbie

Group: General Forum Members
Last Login: Friday, May 04, 2012 10:18 AM
Points: 1, Visits: 13

When I attempt to run an SSIS stored procedure, I am receiving the following error:

[Execute SQL Task] Error: Executing the query "INSERT INTO tmpSQLXTABSOURCE
..." failed with the following error: "Error converting data type nvarchar to float.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Here is the the particular query that is causing a problem:

SELECT AnalysisSetID, LegalEntityID, FieldID, PeerGroupID, FieldDataSetID, DataSetYear, BCTypeID, BCMnemonic, SUM(CAST(DataValue AS float)) AS DataValue,
DataTable, SystemDataTypeID
FROM dbo.qryXTABData
GROUP BY AnalysisSetID, LegalEntityID, FieldID, PeerGroupID, BCTypeID, DataSetYear, BCMnemonic, DataTable, FieldDataSetID, SystemDataTypeID, DataValue
HAVING (SystemDataTypeID = '{7FD263E9-E684-4C0B-A095-D4273182F295}') AND (AnalysisSetID = '6bac995b-b776-4bf3-bfeb-4264270450f1')

Then when I change it to the following, this particular query works!

SELECT AnalysisSetID, LegalEntityID, FieldID, PeerGroupID, FieldDataSetID, DataSetYear, BCTypeID, BCMnemonic, SUM(CAST(DataValue AS decimal)) AS DataValue,
DataTable, SystemDataTypeID
FROM dbo.qryXTABData
GROUP BY AnalysisSetID, LegalEntityID, FieldID, PeerGroupID, BCTypeID, DataSetYear, BCMnemonic, DataTable, FieldDataSetID, SystemDataTypeID, DataValue
HAVING (SystemDataTypeID = '{7FD263E9-E684-4C0B-A095-D4273182F295}') AND (AnalysisSetID = '6bac995b-b776-4bf3-bfeb-4264270450f1')

Does anyone have any idea as to why using the cast to float would fail but the cast to decimal succeeds?

Then I try to update the appropriate view in SQL Server, but when I attempt to run the entire code from the stored procedure, I receive the following error:

Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK__tmpSQLXT__2C3AA4296EAEBD9A'. Cannot insert duplicate key in object 'dbo.tmpSQLXTABSOURCE'.
The statement has been terminated.

Does anyone have any suggestions?

TIA.

Post #788600

« Prev Topic | Next Topic »

Permissions