March 4, 2012 at 8:32 am
I'm trying to use SMO to programmatically backup a SQL Express database on a remote deditcated server and then send a copy to my local machine.
My code tests fine on my local server but when deployed to the remote dedicated server a problem is created by this line of code:
Dim DbServer = New Microsoft.SqlServer.Management.Smo.Server
No catchable error is produced but the code fails to execute at all.
Any ideas on why the remote dedicated server will not allow this SMO class instance to be created?
March 4, 2012 at 10:59 am
i could be wrong but i think the required .NET components are missing with the Express edition installation.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 6, 2012 at 3:19 pm
I'm using Visual Web Developer Express with SQL Express set up on my local server. The components are available and the backup routine I've developed works fine on my local machine.
When deployed to our remote dedicated server, some instances of the Microsoft.SQLServer.Management.SMO classes can be declared without a problem, such as Microsoft.SQLServer.Management.SMO.Backup and Microsoft.SQLServer.Management.SMO.Restore. However when an instance of the Microsoft.SQLServer.Management.SMO.Server class is declared, the rest of the routine will not run though no catchable error is produced.
Why does the .Server declaration execute fine on my local server using SQLExpress but not on the remote Server that also uses SQLExpress?
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply