VB.Net 2005 Setup Creation Gets Error Using Microsoft.SqlServer.Dts.Runtime
Feb 3, 2007
I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.
I migrated a SLQ 2000 DTS package using the SQL 2005 Legacy tools and saved the package as a local .DTSx package on our file server.
I need to run the package from a clients PC.
I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:
Dim oApp As New Application
Dim oPkg As New Package
oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing)
Dim oResults As DTSExecResult
oResults = oPkg.Execute
Ok. That works fine and is basically the entire app. It executes without a hitch in debug and as a compiled exe on my PC, but I have all the tools. So now I try and create a setup project for this and I use the setup wizard.
During the creation of the setup project I get a message that states:
The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project.
C:windowssystem32msxml6.dll
OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.
How do I find this out?
Has anyone else created a project like this and experenced the same?
I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.
I am executing an SSIS package from VB.NET code. Works great in design mode. When I publish it (using Click-Once), it works great on development computer but fails on a customer computer:
Microsoft.SqlServer.Dts.Runtime.DtsPipelineException: Retrieving the COM class factory for component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following error: 80040154. ---> System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} failed due to the following error: 80040154. at Microsoft.SqlServer.Dts.Runtime.Package..ctor() --- End of inner exception stack trace --- at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
My project references Microsoft.SQLServer.ManagedDTS.
The error occurs on the following line:
Dim objPackage As New Microsoft.SqlServer.Dts.Runtime.Package
Looking at various forum threads, it would appear that it's because either (1) DLL(s) are not registered on the customer machine, or (2) DLL(s) are missing from the customer machine. The first explanation doesn't seem right -- even though Microsoft.SQLServer.ManagedDTS is a COM dll, doesn't .NET provide a wrapper when it references it? I downloaded Process Explorer from Sysinternals.com to compare loaded DLLs on my dev box to those on the customer's box and while several dlls are loaded when the line is successfully loaded, all of them exist on the customer box.
I am trying to launch a SSIS package remotely, and found this article http://technet.microsoft.com/en-us/library/ms403355.aspx#agent
however, i cannot add a reference to Microsoft.SqlServer.DTS.Runtime ? My Visual Studio 2005 interface does not show that as a possible reference when using "Add Reference"
I'm trying to run a piece of code in BOL and it imports the dts.runtime class. The problem is when I do the import statement in my form, I get the green line. It can't find the class. The only class found inside SqlServer is Server.
Can anyone tell me why the DTS class isn't there. The box I'm working on has visual studio 2005, and Yukon sp2. And I think I'm running v.3 of the framework, so I should be good all the way around.
It states pretty clearly in the documentation for the Microsoft.SqlServer.Dts.Runtime.Wrapper namespace that "This assembly is a Primary Interop Assembly (PIA) for the namespace Microsoft.SqlServer.Dts.Runtime, which is the assembly Microsoft.SqlServer.ManagedDTS (in microsoft.sqlserver.manageddts.dll). The classes in this namespace should not be instantiated. Instead, use the classes found in the Microsoft.SqlServer.Dts.Runtime. "
And yet as I have found out earlier today and talked about here, sometimes it is absolutely necassary to use Microsoft.SqlServer.Dts.Runtime.Wrapper. Why is this? Why is there no class in Microsoft.SqlServer.Dts.Runtime that allows me to access the specific connection managers rather than using the generic ConnectionManager class?
I have an ASP.NET web form that calls out to a component which includes the following code which leverages the Application and Package classes in the Microsoft.SqlServer.Dts.Runtime namespace:
Microsoft.SqlServer.Dts.Runtime.DTSExecResult result = package.Execute();
I am logged in to the app as DomainMe.
I have Windows Integrated Authentication configured in IIS and am using Windows Authentication in ASP.NET. I am using impersonation to impersonate a fixed identity, say DomainBob. This has the following effect:
WindowIdentity.GetCurrent() returns DomainBob as expected since the process is being impersonated by DomainBob.
Thread.CurrentPrincipal.Identity.Name returns DomainMe as expected since the ASP.NET application is using Windows Authentication.
The id variable successfuly is initialized to the GUID of the package, proving that the package name is resolving, however, from the ASP.NET application, the package fails.
Issuing the ? package.Errors[0] command at the command window provides the following information:
{Microsoft.SqlServer.Dts.Runtime.DtsError} base {Microsoft.SqlServer.Dts.Runtime.DtsObject}: {Microsoft.SqlServer.Dts.Runtime.DtsError} Description: "An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Shared Memory Provider: I/O Error detected in read/write operation [4]. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'MyMachine\ASPNET'.". " ErrorCode: -1071636471 HelpContext: 0 HelpFile: null IDOfInterfaceWithError: "{8BDFE898-E9D8-4D23-9739-DA807BCDC2AC}" Source: "Packages MyPackage" SubComponent: "Connection manager "DataMart"" TimeStamp: {12/21/2006 2:18:55 PM}
For some reason, the ASPNET process account is being passed to the package!
This makes no sense, because clearly, DomainBob is impersonating the worker process and all downstream resources should be accessed via DomainBob. This includes SQL Server Database Engine and I would imagine SSIS as well. ASPNET should not come into play at all since I am impersonating.
I also tried using regular (non-fixed identity) impersonation (<identity impersonate="true" />), but again, SSIS is trying to authenticate ASPNET, instead of DomainMe as would be expected.
This is definetely isolated to ASP.NET applications, because making the same call from within a unit test succeeds. It would seem that this is a definete issue because the behavior is inconsistent with ASP.NET security principles.
Has anyone else seen this problem?
Any direction or suggestions very much appreciated.
I am struggling in calling an SSIS package programatically using the Microsoft.SqlServer.Dts.Runtime namespace.
I am succesfuly connecting to the package insofar as I am able to retrieve the package ID (GUID), but when I call package.Execute I get a 'login failed for user' error, which indicates a security problem.
My ASP.NET app is running as a domain user which has temporary 'SA' rights on the server where the package is hosted. In addition, I have set the protection level on the package to 'DontSaveSensitive'.
What am I missing to be able to execute the package remotely?
I´m wondering how to make a connection to a file in differents machines, FTP, excel file, HTTP, WebService instead of OLDDB, where can I find a reference for the constants that must be used in each case.
"SQL Server is unable to run. Either the owning node or all nodes that currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online."
Can someone tell me what's the cause of this error? How can this be corrected?
I was in the process of installing Microsof Project 2003 when we suddenly decided to move up to Microsoft Project 2007. We removed SharePoint 3.0 and SQL Server 2K so all that is installed on the box is Windows Server 2003 with all Service Packs. During the install of SQL Server 2005, here is the error message we get.
Microsoft SQL Server 2005 Setup
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot alter the login €˜sa€™, because it does not exist or you do not have permission.. Refer to the server error logs and Setup logs for detailed error information.
Hello, I got an exception when I try to load/run a SSIS Package programmatically on the server using remoting. The client machine has no SQL Server 2005 component installed..
This is the error I get from my exe application:
Microsoft.SqlServer.Dts.Runtime.DtsPipelineException: Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. ---> System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. at Microsoft.SqlServer.Dts.Runtime.Application..ctor()
And this the Remote component:
<Serializable()> Public Class SSISComponent
Inherits MarshalByRefObject
Public Function LaunchPackage(ByVal sourceLocation As String, ByVal serverName As String, ByVal packageName As String, ByVal packageVariables As SortedList) As Microsoft.SqlServer.Dts.Runtime.DTSExecResult
Dim packagePath As String Dim myPackage As Package Dim integrationServices As New Application ' Combine path and filename. packagePath = Path.Combine(sourceLocation, packageName) Try If integrationServices.ExistsOnDtsServer(packagePath, serverName) Then myPackage = integrationServices.LoadFromDtsServer(packagePath, serverName, Nothing) Else Throw New ApplicationException( "Invalid package name or location: " & packagePath) End If If Not packageVariables Is Nothing Then For Each de As DictionaryEntry In packageVariables myPackage.Variables(de.Key).Value = de.Value Next End If LaunchPackage = myPackage.Execute() Catch ex As Exception Throw End Try End Function End Class
This is the code that call the remote component to run the package on the Server: Public Class Test Private Function LoadAndRunPackageRemotly(ByVal PackageName As String, ByVal PackageVariables As SortedList) As Boolean
Dim launchPackageService As New SSISComponent Dim packageResult As Microsoft.SqlServer.Dts.Runtime.DTSExecResult Try packageResult = launchPackageService.LaunchPackage(Me.SSISPackageLocation, Me.SSISServerName, PackageName, PackageVariables) If packageResult = DTSExecResult.Success Then LoadAndRunPackageRemotly = True Else LoadAndRunPackageRemotly = False End If Catch ex As Exception Throw End Try End Function End Class
I would like to inform that everything run inside a thread because the Package do a lot of things... When I build up the setup for the exe inside the Detected Dependencies there are several DLL related to SQL Server (Microsoft.SQLServer.DTSRuntimeWrap.dll etc..etc..) that I don't register .. Tis could be the problem? If yes, somebody can tell me which one I have to register ? as COM or COMRelativePath? Some other hints?
This error could be also caused by wrong permissions on the ssis? Thank you very much for any help... p.s. To use sql server agent will be my last option!! Marina b.
This is when i try to submit a new database item in Dreamweaver. The DB I am using is SQL Server 2005.
My code is as follows:
Dim equipspec__urlid equipspec__urlid = "1" If (QueryString("ID") <> "") Then equipspec__urlid = QueryString("ID") End If %> <% Dim equipspec Dim equipspec_numRows
When I'm trying to create a database diagram for my tables., First it prompts me saying that - "This database does not have one or more of the supported objects... Do you wish to create them? I know this is normal when you don't have any diagrams. But after clicking "Yes", I get the following error which is attached.
I tried changing the database Owner to "sa". But, still the same error. Interestingly, other databases that are already having the database diagrams (created by others), are allowing me to create new diagrams in those databases. The only difference is, I created this database where I'm trying to create diagrams on. How do I get this working.
I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.
I took a SQL Server 2000 dts package and using the SQL Server 3005 legacy tools migrated it so I could still use the package withing SQL 2005 until I can build one using BI/SSIS.
Anyway,I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:
Dim oApp As New Application Dim oPkg As New Package oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing) Dim oResults As DTSExecResult oResults = oPkg.Execute
Ok. That works fine. Executes without a hitch. So now I try and create a setup project for this and I use the setup wizard.
During the creation of the setup project I get a message that states: The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project. C:windowssystem32msxml6.dll
OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.
How do I find this out?
Has anyone else created a project like this and experenced the same?
I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.
Hello All,I am getting the following error when attemping to open a table inSQL2kSP3a.________________________________________SQL Server Enterprise ManagerDatabase Server: Microsoft SQL ServerVersion: 08.00.0760Runtime Error: [Microsoft][ODBC SQL Server Driver]Invalid time format_________________________________________I cannot find it in sysmessages, or on the web.Any ideas about how to resolve this? And how it occured...Thanks,TGru*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
i keep getting this message whenever i double click the setup for sql server 2005. i previously installed the sql server 2005 beta 2 and have since deleted it. i've followed the readme on uninstalling some of the beta components and tried running some program i got from microsoft.com which would uninstal the pre release- the program doesn't detect any pre-release component. i however continue to get this message and need help resolving it.
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=50000&EvtType=setup%5csqlsetupactions.cpp%40PerformSCCAction2%40sqls%3a%3aPerformSCCAction%3a%3aperform%400x11190
I can't seem to set up SQL server authentication for SQLserver 2005 Express edition..
I simply can't find the settings for that. I have Management Studio Express installed and I can see the SA user but I can't login using that user.. I know that there's supposed to be a setting for turning on SQL auth. but it's not like it used to be in Enterprise manager :) so I can't find it.. ;/ I couldn't find any documentation on how to do this so I thought I'll try here..
(I need SQL auth for my project :) - it must be done with that..)
I'have this error during install of Microsoft SQL Server 2005 Express Edition (x86). I'm Using Windows XP Professional with SP2 Build 2600. Does anyone knows how to solve this?
****
Microsoft SQL Server 2005 Setup was unable to install on your computer.
I am using VB.NET 2002 and we have set up a test environment running SQL Server 2005.
I am trying to add a reference to Microsoft.SQLServer.ManagedDTS.dll which is required to run a DTS/SSIS package from VB.NET.
However the dll does not show in my add reference listing so when I select BROWSE and select the actual DLL I get a rather long error message telling me that only 'dll' and COM components can be referenced.
The exact message is:
A reference to 'C:Programs FilesMicrosoft SQL Server90SDKAssembliesMicrosoft.SQLServer.ManagedDTS.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.
I have tried to install Outlook 2007 with BCM and recieve the error listed above. I have also included a copy of my log file. Any suggestions?
Microsoft SQL Server 2005 9.00.2047.00 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Thu Aug 23 14:22:59 2007
Machine : MACBOOK Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.2047.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : MACBOOK Product : Microsoft SQL Server Native Client Product Version : 9.00.2047.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : MACBOOK Product : Microsoft SQL Server VSS Writer Product Version : 9.00.2047.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : MACBOOK Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_MSXML6_1.log Error Number : 1603 -------------------------------------------------------------------------------- SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
The SQL SERver 2005 Standard Edidtion install CD and the MSDN CD distributedat the SQLServer Launch in Chicago are blank. Has anyone else had thisproblem and or requested replacements? If so, how.thanks muchMo
