Problem in uploading a website containing SMO Reference.
-
Hi all, If I upload a file containing SMO Reference the following error comes: Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. The references I added are Microsoft.sqlserver.connectioninfo Microsoft.sqlserver.smo Microsoft.sqlserver.smoenum Microsoft.sqlserver.sqlenum Is I have to explicitly place the SMO dll in the bin folder of the project? Please help me to rectify this problem. Thanks.
-
Hi all, If I upload a file containing SMO Reference the following error comes: Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. The references I added are Microsoft.sqlserver.connectioninfo Microsoft.sqlserver.smo Microsoft.sqlserver.smoenum Microsoft.sqlserver.sqlenum Is I have to explicitly place the SMO dll in the bin folder of the project? Please help me to rectify this problem. Thanks.
-
Hi, seems like you have to place them explicitly in the bin folder of the project (after upload). Are you sure that the Microsoft SQL Managment Objects are installed at the target server? Regards Sebastian
-
Hi, Thanks for your quick reply. I don't know whether the target server contains SMO. If we install SMO dll in the target server, will it work well?. If we do like that there is no need to add the dll in the project. Am I right?
hmmm, if you install the smo dll in the target server (for example registering in the GAC) you don't have to copy the dll to the bin folder (think this only works if it is the correct assembly version)... I think the best way is to install the SQL Server Managament (that's where the dll is coming from, am I right?). This will propably solve your problem (but you have the same problem for the next server...)
-
hmmm, if you install the smo dll in the target server (for example registering in the GAC) you don't have to copy the dll to the bin folder (think this only works if it is the correct assembly version)... I think the best way is to install the SQL Server Managament (that's where the dll is coming from, am I right?). This will propably solve your problem (but you have the same problem for the next server...)