Showing posts with label programmatically. Show all posts
Showing posts with label programmatically. Show all posts

Thursday, March 22, 2012

Can't Add Reference to Microsoft.SQLServer.RMO.dll

Hi All,
I'm trying to add a reference to this DLL in Visual Studio 2003 so I
can programmatically trigger replication. When I try and add the
reference I get the following exception:
"A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
\Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
not a valid assembly or COM component. Only assemblies with extension
'dll' and COM components can be referenced. Please make sure that the
file is accessible, and that it is a valid assembly or COM component."
As you can see it does have a .dll extension.
The file I try to reference indicates it was created on 14 October
2005, 03:43:34 and is version 9.0.1399.0
C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
\Microsoft.SqlServer.Rmo.dll
Can I doenload another version of the DLL from somewhere?
Any help appreciated!
Thanks
Rajl
On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
> Hi All,
> I'm trying to add a reference to this DLL in Visual Studio 2003 so I
> can programmatically trigger replication. When I try and add the
> reference I get the following exception:
> "A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
> \Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
> not a valid assembly or COM component. Only assemblies with extension
> 'dll' and COM components can be referenced. Please make sure that the
> file is accessible, and that it is a valid assembly or COM component."
> As you can see it does have a .dll extension.
> The file I try to reference indicates it was created on 14 October
> 2005, 03:43:34 and is version 9.0.1399.0
> C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
> \Microsoft.SqlServer.Rmo.dll
> Can I doenload another version of the DLL from somewhere?
> Any help appreciated!
> Thanks
> Rajl
Also got a newer version of the file version 9.0.242.0, created 10th
Feb 2007 but that has the same problem
|||On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
>
>
>
>
>
>
>
> Also got a newer version of the file version 9.0.242.0, created 10th
> Feb 2007 but that has the same problem- Hide quoted text -
> - Show quoted text -
OK, this is resolved now. I think the issue is to do with the fact I'm
using VS2003. I tried adding the reference to a VS2005 project and
that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
not compatible against VS2003?
|||If you want to programmatically start replication, you probably will also
need to add a reference to the "Replication Agent Library" assembly.
For more information, see
http://msdn2.microsoft.com/de-de/library/ms146869.aspx.
Cheers!
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"rajpatel50@.hotmail.com" wrote:

> On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> OK, this is resolved now. I think the issue is to do with the fact I'm
> using VS2003. I tried adding the reference to a VS2005 project and
> that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
> not compatible against VS2003?
>

Sunday, February 19, 2012

Cannot set Connection property of Backup database task if connection string is customized in con

I added a connection (ADO.NET) object by name testCon in the connection manager - I wanted to programmatically supply the connection string. So I used the "Expressions" property of the connection object and set the connectionstring to one DTS variable. The idea is to supply the connection string value to the variable - so that the connection object uses my connection string.

Then I added a "Backup Database Task" to my package with the name BkpTask. Now whenever I try to set the connection property of BkpTask to the testCon connection object, by typing testCon, it automatically gets cleared. I am not able to set the connection value.

Then after spending several hours I found that this is because I have customized the connection string in testCon. If I don't customize the connection string, I am able to enter the "testCon" value in the connection property of the BkpTask.

Is this an intrinsic issue?

Not quite sure what this issue is, but I tried this-

Created a ADO.Net connection and set an expression on the ConnectionString property. Evaluated value is a valid conn string.

Add a Backup DB Task, and set an expression on the Connection property. Evaluated value is name of connection created above.

Works fine, executes fine. If the Tasks' Connection property, the literal value is wrong at design-time, but will be correct at run-time when the expression is evaluated overriding the literal value, you may want to set the DelayValidation property to True for the task.

|||Thanks, this one - setting the DelayValidation was useful. What I tried was to customize the connectionstring in expression property of ConnectionManager. My issue is now solved, Thanks a lot.

Cannot set Connection property of Backup database task if connection string is customized in

I added a connection (ADO.NET) object by name testCon in the connection manager - I wanted to programmatically supply the connection string. So I used the "Expressions" property of the connection object and set the connectionstring to one DTS variable. The idea is to supply the connection string value to the variable - so that the connection object uses my connection string.

Then I added a "Backup Database Task" to my package with the name BkpTask. Now whenever I try to set the connection property of BkpTask to the testCon connection object, by typing testCon, it automatically gets cleared. I am not able to set the connection value.

Then after spending several hours I found that this is because I have customized the connection string in testCon. If I don't customize the connection string, I am able to enter the "testCon" value in the connection property of the BkpTask.

Is this an intrinsic issue?

Not quite sure what this issue is, but I tried this-

Created a ADO.Net connection and set an expression on the ConnectionString property. Evaluated value is a valid conn string.

Add a Backup DB Task, and set an expression on the Connection property. Evaluated value is name of connection created above.

Works fine, executes fine. If the Tasks' Connection property, the literal value is wrong at design-time, but will be correct at run-time when the expression is evaluated overriding the literal value, you may want to set the DelayValidation property to True for the task.

|||Thanks, this one - setting the DelayValidation was useful. What I tried was to customize the connectionstring in expression property of ConnectionManager. My issue is now solved, Thanks a lot.