CopyExceptionFailedException: Copy exception failed for Microsoft.SqlServer.Management.Smo.FailedOperationException

Question

4.00/5 (1 vote)

See more:

Hi Coders,

We have two servers like development(windows server 2008 R2 and SQL server 2005 and visual studio 2010) and deployment(windows server 2008 R2 and SQL server 2005)server.

in the deployment server we have deployed asp.net application from development server 2 years back.

in that asp.net application we have referenced dlls are following,

VB

Microsoft.SqlServer.ConnectionInfo.dll-> version:10.0
Microsoft.SqlServer.Management.Sdk.Sfc.dllversion:10.0
Microsoft.SqlServer.Smo.dll-> version:10.0
Microsoft.SqlServer.SmoExtended.dll-> version:10.0
Microsoft.SqlServer.SqlClrProvider.dll-> version:10.0
Microsoft.SqlServer.SqlEnum.dll-> version:10.0

it was working fine with this dlls.

Later in the development server we have added the following latest references to the project,

VB

Microsoft.SqlServer.ConnectionInfo.dll-> version:11.0
Microsoft.SqlServer.Management.Sdk.Sfc.dllversion:11.0
Microsoft.SqlServer.Smo.dll-> version:11.0
Microsoft.SqlServer.SmoExtended.dll-> version:11.0
Microsoft.SqlServer.SqlClrProvider.dll-> version:11.0
Microsoft.SqlServer.SqlEnum.dll-> version:11.0

In the development server it is working fine without any issues.

After testing done we deployed this to the deployment server, when we running the application, it was throwing the following error,

Error:
"CopyExceptionFailedException: Copy exception failed for Microsoft.SqlServer.Management.Smo.FailedOperationException: Exception has been thrown by the target of an invocation. See the inner exception for the original error. ---> Microsoft.SqlServer.Management.Smo.FailedOperationException: Prefetch objects failed for Database 'Test_Newsetup_RDM'. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array. at Microsoft.SqlServer.Management.Smo.SqlPropertyMetadataProvider.PropertyNameToIDLookupWithException(String propertyName, PropertyAccessPurpose pap) at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName, Boolean throwOnNullValue) at Microsoft.SqlServer.Management.Smo.Database.CheckDbCompatibilityLevel() at Microsoft.SqlServer.Management.Smo.Database.PrefetchObjectsImpl(Type objectType, ScriptingOptions scriptingOptions) --- End of inner exception stack trace --- at Microsoft.SqlServer.Management.Smo.Database.PrefetchObjectsImpl(Type objectType, ScriptingOptions scriptingOptions) at DbTools.DbaTasks_CatModelling.Workflow.CopyDatabaseObjectsCmd.GenerateScripts()"

I am unable to figure out the issue, after deployment is done on the deployment server is this restart required for the deployment server.

Regards
KishoreD

Posted 21-May-15 18:30pm

D-Kishore

Updated 22-May-15 3:05am

v3

Add a Solution

Comments

krish2013 22-May-15 0:45am

Hi all,
i have also faced same issue.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ganesan Senthilvel · Answer 1 · 2015-05-21T23:24:00

Solution 1

Got it. It is highly recommended to remove the references to SMO dlls in older versions of SQL Server. And references to the new SMO dlls that are provided with new SQL Server version must be included.

Minimally, you would reference the following:

C#

Microsoft.SqlServer.ConnectionInfo
Microsoft.SqlServer.Smo
Microsoft.SqlServer.Management.Sdk.Sfc

Posted 21-May-15 23:24pm

Ganesan Senthilvel

Comments

D-Kishore 22-May-15 9:03am

Yes you are correct, but i have replaced all the files then only i deployed to the server, no luck

Ganesan Senthilvel · Answer 2 · 2015-05-21T23:28:00

Solution 2

A good reference is available at Microsoft's official site about forward compatibility (not going to fix) and backward compatibility (Denali SSMS will be able to manage 2000, 2005, 2008, 2008 R2): http://connect.microsoft.com/SQLServer/feedback/details/622441

Posted 21-May-15 23:28pm

Ganesan Senthilvel