Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Connect to SSIS Service on machine "DAVINCI" failed:
The specified service does not exist as an installed service.
***
I see a ton of people having the same problem, but as for now I still haven't found a solution.
We have SP1 installed and have installed cumulative fix from http://support.microsoft.com/kb/918644, and been by the DCOM settings regarding local/remote access.
The SSIS service is not running. It is not shown in the list of services.
I wanted to add Reports Service to my sql express. I downloaded the SQLEXPR_ADV.EXE and also Edition Toolkit SP1. But can't see the option to install Report service.
I'm using SQL Server Express on Vista. I can't remember whether or not I installed the service packs for SSEE. Is there a quick and easy way to find out?
The white paper Using SQL Server 2005 reporting Services with SAP NetWeaver Business Intelligence refers to "Microsoft SQL Server 2005 Reporting Services Service Pack 1"
I can not find this service pack.
Is it part of some other package by a differnet name?
I am running Win XP SP2 and MSDE 2000 SP3a. The user is logging on asa POWERUSER. When the user logs on the MSSQLSERVER service starts butthe SQL Server Service Manager, that runs in the system tray, showsthat the instance has not started. The field that displays theinstance name is blank and it is not listed in the drop down list.The MSSQLSERVER service is set to start with a Windows domainadministrator account. The SQL server can be accessed by a remotecomputer through Enterprise Manager. The local programs cannontinteract with the server though.Does anyone know if I could grant some user access rights to allow MSDEto work under a POWERUSER login?
I have troublesome problem with service broker. I move a lot of databases from one server to another servers (by backup and restore) but always have problem with databases where service broker is enabled. Bellow is my scenario:
1. backup database db1 (srv1) 2. restore db1 (srv2, srv3, srv4.....) 3. drop manually Services and Queues, only green filed (http://img122.imageshack.us/img122/549/clipqk5.jpg) (srv2, srv3, srv4.....) 4. alter database db1 set enable_broker (srv2, srv3, srv4.....)
After that SQL Server log on each server is full bellow errors, nobody so far can help me
Could you help, please
############ SRV2 03/03/2008 18:54:41,spid21s,Unknown,The query notification dialog on conversation handle '{E6BF547B-0AE6-DC11-A4BD-00E08127B819}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-53c1dc9b-7d22-4310-a5b6-18ac97ae4bf3' because it does not exist.</Description></Error>'. 03/03/2008 18:54:41,spid27s,Unknown,The query notification dialog on conversation handle '{AA68F7D8-F7E5-DC11-A4BD-00E08127B819}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service
SERV3 03/02/2008 00:32:25,spid21s,Unknown,The query notification dialog on conversation handle '{2BC70B27-F1E3-DC11-AB50-0017085CAA29}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-abc6a7ce-53f1-411e-85a7-50c09e2699e1' because it does not exist.</Description></Error>'. 03/02/2008 00:29:20,spid22s,Unknown,The query notification dialog on conversation handle '{DF112861-F9E3-DC11-AB50-0017085CAA29}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service
SRV4 03/02/2008 16:15:07,spid25s,Unknown,The query notification dialog on conversation handle '{4179E578-7DE4-DC11-9A69-00145E1B71FC}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-01e16746-e114-4e8c-b587-91e93768a9a8' because it does not exist.</Description></Error>'. 03/02/2008 16:15:07,spid20s,Unknown,The query notification dialog on conversation handle '{5079E578-7DE4-DC11-9A69-00145E1B71FC}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service ############
Hey all I tried to use the SQL Server 2005 setup file to try and locate the Integrated Services but it's not on there. Where else can I find SSIS?? Help!!!
I have VS2005 and have been using SQL 2000. I installed SQL 2005 Developer but I can't find SSIS anywhere. It is hard to start even the first tutorial if I can't find the program. Was it supposed to be installed with 2005 Developer? Help!
I have installed SQL Server 2005 and the SSIS service is running. However I cannot find the package to use it.
I am evaluating SQL Server 2005 so I currently have a trial copy - is this the problem? I want to recommend a purchase but I do not want to end up with the same issue with the organisation having bought a copy.
I'm getting an error when running my SSIS package in a SQLAgent job....
Message Executed as user: DOITLHHQSQLT01SYSTEM. The process could not be created for step 1 of job 0x35D6B42101FB6646B20036599D407110 (reason: The system cannot find the file specified). The step failed.
This is the command line executing the SSIS package....
I'm assuming the file it cannot find is the SSIS package..."ES PackagesES DEDUCTIONS".
The step is running under the SQL Agent Service Account.
Anyone have any hints for me? The file is there when I look in integration services.
PS. I looked at the Configuration Manager and Integration Services in running under the Network Service account while the SQL Agent service is running under the Local System account. Could this make a difference? Should all the services be running under the same account? (I don't install this stuff so excuse my ignorance.)
I am using the SSIS Import & Export Wizard to make packages importing data from Access 2003 into SQL Server2005.
In the Access database I am using, there are about 100 tables and 4 select queries.
When I ran the SSIS wizard, it found the first query fine, and the package was made successfully.
Now, I need to make a package to import data using one of the other select queries (it has two subqueries.)
When I run the wizard, the "Select Source Tables and Views" dialog opens and shows all 100 tables, plus only two of the queries, not all 4. Two are missing, including the one I need to do the import.
I cannot see why these two queries would be excluded. One is a compound query (the one I need) the other is not. Is there a limit to the number of objects the dialog can show?
If anybody has had this problem please let me know. For now it's a real show stopper.
I bought a new HP server with Windows 2003 SBS Premium. I also was told buy the company how installed the server, that they installed all the components of SQL. When another company came to install a new business software for us, they told me that the Integration services is not installed. We tried together to install the SSIS with no luck. When we run the Setup(or used Add/Remove software) we couldn't find the Integration services check box in the list of the setup.
I also asked assistans from the company that i bought the server fromk, and they also couldn't understand where is it.
We have an HP Proliant server, Windows server 2003 small business preminum SP1, SQL server 2005.
I was told that without the SSIS we can't start working with our new software, so this is very urgent for us.
I have both VSTS 2005 for Developers and VSTS 2005 for Database Professionals installed on my PC. I can't find any BI or SSIS projects in File->New Projects. The only database-related projects are to write Stored Procedures, Views, etc. Where is it? Did they break it when they added the Database version on top of the Developers version?
We have a sql job type SSIS package that is not populating a database table as expected and I'm trying to figure what why not but I'm not sure where the "code" is. The person that created it said they copied a legacy package (sql 2000) and made modifications to it, then migrated it to the new version. When a legacy package is migrated is there a SSIS solution built? I see you can edit SSIS packages only in BI Development Studio but I'm not sure where to find package.
This post may answer my question but if you have any additional or updated information I'd like to hear it. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=393634&SiteID=1
So, to view or edit the package you have to export it? Package location
Select the type of storage location to export the package to. The following options are available:
SQL Server
File System
SSIS Package Storage
So do you pick "File System" in order to view it in BI?
I have a webservice, which I am using in the Web service Task. The XML response, is fed to the XML source and I want to write the data from this XML to flat file. I am using the below attached schema definition for XML (.XSD). When I use this as XSD in the XML source task, in the column definition I see only three columns and they are
ZoneCode ZoneName AggregatedCZ_Id
My question is what is AggregatedCZ_Id and why I do not see the PostCode in the columns? Any help is appreciated.
I've been completely unsuccessful so far in getting the SSIS service to start under normal circumstances.
I've got the SQL 2005 RTM DVD and a clean, brand-new installation of Windows 2000 Server (Service Pack 4). All system requirements have been met according to the SQL installer. I choose to install just the Database Engine, SSIS and the Workstation components, all other installation options are defaults except Services, which are set to use a Domain User account.
The install completes without problems and the SQL Server & SS Agent services start suceessfully, but the SSIS service refuses to start (timeout). If I change the service to use LocalSystem, the same happens. If I make the Domain User (DOMAINMisterSQL) account a member of Local Admins on the server, the service still won't start.
If, however, I use a Domain Admin account, the service does start, so it appears to be a security issue, but how can I configure the service to start with fewer privileges?
This problem has appeared on each machine I've tried this on, four to date, so it's not related to the particular setup of this server. I've searched the web for weeks for a solution with no success; any help would be greatly appreciated.
I understand Sql Server Integration Services by default uses"NT AuthorityNetwork Service" account as service account. Is running SSIS using "NT AuthorityNetwork Service" account is good or should we create a domain account to run the SSIS service.
I am trying to use SSI Sto receive messages from a Service Broker Queue and continue to have difficulty doing so.
I have come to the point where I need to get the messages that share a conversation with this BatchEnd message type before I get any other messages, as this message type tells me information about how many others there are.
I built this script and ran it in management studio with success and felt it should work for me running as the sql for an OLE DB source.
But SSIS constantly complains about it. I finally profiled SSIS to catch the sql that it is executing. It is below and this fails with an error about a missing conversation_handle.
Now I'm not sure which team may own this, but shouldn't this sp_prepare work. If I change this to use a table variable then the prepare seems to work just fine, but then I never actually get any data back into SSIS. It is almost like it calls it twice; although, I could not confirm that with profiler.
I'll cross post this in the Service Broker forum too.
I want to use Service Broker and SSIS in a integration project where the queue contains Xml data and the SSIS package processes and sends it to a destination. What is a good way to do this? Is it possible for the queue to execute the package with the data as a parameter, or what is good practise when combining this techniques? I am not familiar with Service Broker so i donīt know what you can do with it when data are loaded in it.
Would be grateful for some hints to put me in a good direction..
I want to use Service Broker to drop some SQL from a loop in SSIS task into a Service Broker queue. Can anyone point me in the right direction, examples, samples?
I have an ExecuteSQL task which returns a set of tablenames, which will be iterated to, and I want to send an EXEC mySP 'myTable' to Service Broker, to asynchronously execute. I have created a queue and a service, but I'm not sure what the next step is to join the two together.
I've seen examples of creating a Web Service that executes an SSIS package through code. But that involves developing the web service, configuring IIS on the same server as SSIS to expose the web service. I was wondering if it is easy to use the HTTP endpoints within SQL Server 2005 to create a web service interface that calls an SSIS package, supplying any parameters the package needs to run. Also, this would be called from within Excel VBA that uses a web-reference via the Web Reference Toolkit.
I have been struggling with a problem with the Web Service Task. I have a package that uses this and has to authenticate to the web service. This works fine on my development server but if I export the package to file and run from another computer / user, the package fails as it doesn't log in to the web service. I have found the problem to be the package was set to default of EncryptSensitiveWithUserKey and I understand why this is. If I change to use EncryptSensitiveWithPassword, it prompts for creds and works fine. My question is how do I use a package configuration file to use different creds (there is not password option for the http connection) so I can standardize on use of config files for this operation. Thanks.
I have three databases and 40 tables within each database on my server, for each of the tables I want to know which SSIS package generates that table. Is there a script that can do this?
If the SSIS package does not create or populate a table on the server I then want to check if there is a stored procedure that populates this.
Greetings, Ever since our sql2005 A/P failover cluster failed over to the 'B-passive node', I have a failing SSIS scheduled job with a 'missing component' error. While verifying services in computer management and sql surface area config, It appears that the SSIS service is not available because its not listed therefore cant be started. I have examined both nodes and the primary "A-active node' shows the SSIS service but the passive node unlisted. The server has failed over before during normal scheduled updates and sevice pack installs however this is the first occation we have not failed back to the primary node for normal operation. Any ideas or clues would be appreciated.
In the SP1 update of SSIS there was a call from the SSIS service that would attempt to validate itself against the http://crl.microsoft.com web site. If the SSIS service didn't have access to the internet then it would timeout and not start the service. In our company we have our development systems behind a firewall which only allows for limited internet access due to it being a development system.
Does the installation of SP2 remove this authentication restriction?
I just learned I can deploy and schedule jobs to run SSIS packages (via job/sqlagent) without the Integration Service (agent) itself actually running alongside (or on) the server. (Double-click on manifest, deploy IS package to server, create job/job step to run IS package, watch it run even when integration service is completely disabled)
Other than convenient viewing, configuring, and RMC running w/in SQL Server Mgmt Studio 2005, why then do I need the integration service running on a production box at all? When do I really need the IS service itself?
In our (finance) world only (a) an act of God or (b) a DBA can touch production databases/servers. Allowing anyone to connect to yet another service - in this case, an integration service - to meddle w/ a package would be a no no, so...
1) Could I trouble someone for a concrete, critical reason why the DBA should enable it on a production server. Speed? Caching? Peace of mind knowing everything is piled onto and neatly running on the server?
2) On a more minor note, if I'm deploying a package to be housed solely w/in MSDB, is there anyway to prevent the prompt of a file location during deployment, i.e. the creation of an empty directory that would otherwise hold package dependencies if I were running it as a file?
We'd like to deploy only to MSDB (I know all the pros/cons w/r/t saving dtsxs to files v. msdb) and keep deployments clean (read: all in one place). DR is via SAN-to-SAN replication with, among other things, msdb cleanly getting replicated. We would very much like to avoid having to worry about (more) file/directories sitting out on a server share to be replicated to DR (it seems the default is to allow deployments to directories on the SQL server instance itself..ugh) Any architectural insights on this would be appreciated.
