I noticed an error in my event log today that states:
The SQL Server Integration Services 10.0 service failed to start due
to the following error: The service did not start due to a logon
failure.
The service is configured to use ./sqluser but I cannot find this login with the domain.
What exactly is this services used for? What login should I be using for this service and what rights/privileges does the user need for this service to function properly. I am using SQL 2008 under Windows Server 2008 r2.
What exactly is this services used for
Managing Integration Services
Microsoft SQL Server Integration Services includes the Integration
Services service, a Windows service for managing Integration Services
packages. The Integration Services service is available only in SQL
Server Management Studio.
Running the Integration Services service provides the following
management capabilities:
Starting remote and locally stored packages
Stopping remote and locally running packages
Monitoring remote and locally running packages
Importing and exporting packages
Managing package storage
Customizing storage folders
Stopping running packages when the service is stopped
Viewing the Windows Event log
Connecting to multiple Integration Services servers
The Integration Services service is installed when you install the
Integration Services component of SQL Server. By default, the
Integration Services service is started and the startup type of the
service is set to automatic. The service must be running to monitor
the packages that are stored in the SSIS Package Store. The SSIS
Package Store can be either the msdb database in an instance of SQL
Server or the designated folders in the file system.
The Integration Services service is not required if you only want to
design and execute Integration Services packages. However, the service
is required to list and monitor packages using SQL Server Management
Studio.
What login should I be using for this service and what rights/privileges
Managing the Integration Services Service
By default, the Integration Services service runs in the context of
the NETWORK SERVICE account.
I have not found a simplified list of what is required for the service to run correctly but this article describes how to connect to a remote SSIS service.
I'll keep browsing MSDN articles
Related
Link: https://learn.microsoft.com/en-us/sql/integration-services/install-windows/install-integration-services?view=sql-server-ver15#installing-a-dedicated-server-for-etl-processes
If the ETL server doesn't have an instance of the Database Engine, you
have to schedule or run packages from a server that does have an
instance of the Database Engine. As a result, the packages aren't
running on the ETL server, but instead on the server from which
they're started. As a result, the resources of the dedicated ETL
server aren't being used as intended.
For ssis we need integration services selected during install. Say server 1 has integration services installed and no db engines. Server 2 has db engine (and the ssis db) and agent job on which ssis package is configured to run. As per quote above, it will run on server 2 resources. So what exactly is the purpose of integration services?
And what exactly decides where the ssis etl runs?
I am trying to deploy a SSIS project from Visual Studio (VS). I can run my packages locally in VS against the SQL Server 2014 instance. I can also connect to the SQL Server 2014 instance via SQL Server Management Studio.
However, I cannot connect when I try to deploy. Maybe a port needs to be opened for the integration services catalog? Does anyone know the port?
Thanks.
This link should give you everything you need about setting up your firewall to work with SSIS and its service. The port it uses seems to be port 135
Configure a Windows Firewall for Access to the SSIS Service
I have created a Virtual machine on Azure cloud. I want to figure out a mechanism of connecting Ssis with clients on-premises (non-cloud) SAP system. Is there any ssis utility that I can install that will breathe behind clients firewall and pass the data to Azure SQL database?
There is a tool called Microsoft Data Management Gateway for connecting from Azure to on-premise:
http://www.microsoft.com/nl-nl/download/details.aspx?id=39717
I am trying to deploy my asp.net mvc application to another server but getting this error:
Error 101 Web deployment task failed. (Could not connect to the remote computer ...
I have installed the Web Management service on the server and it is running?
I have also tried to queue a build in tfs which builds fine on the buildserver however the deployment is not happening:
/p:DeployOnBuild=True
/p:DeployTarget=MSDeployPublish
/p:CreatePackageOnPublish=True
/p:MsDeployServiceUrl=https://myserver:8172/msdeploy.axd
/p:MsDeployPublishMethod=WMSVC
/p:UserName=myserver\myadmin
/p:Password=mypassword
/p:AllowUntrustedCertificate=True
/p:DeployIisAppPath="Default Web Site/myappname"
You need to install the Web Deploy package from WebPI and ensure that you have ports 443 and 8172 open on your firewall.
Web Deploy Download if you don't PI
During a fail over cluster server on the primary, the secondary server gave this error message:
Executed as user: LIVE\super_3. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 7:39:10 AM Could not load package "\File System\Package1" because of error 0xC00160AD. Description: Connecting to the Integration Services service on the computer "Cluster2" failed with the following error: "The RPC server is unavailable. ". This error occurs when the computer host name does not exist, or cannot be reached. Source: Started: 7:39:10 AM Finished: 7:39:31 AM Elapsed: 21.029 seconds. The package could not be loaded. The step failed.
This error still happen even the firewall had been disabled, and the Remote Procedure Call (RPC) Service in Control Panel's Services have been set to startup automatically and was running.
The Scheduled Job is running on SQL Server 2008 R2 on Windows Server 2008 R2 Enterprise.
The package is reading a text file into a table.
Integration services is not cluster aware as mentioned in the comment. A failover like you explained is not supported and will not work.
It is recommended to install Integration Services as standalone services on each node in the cluster.
MSDN says:
Although the Integration Services service is not a clustered service, you can manually configure the service to operate as a cluster resource after you install Integration Services separately on each node of the cluster. For those customers who conclude that the advantages of this configuration outweigh the disadvantages, this topic contains instructions for configuring the service as a cluster resource.
However, if high availability is your goal in establishing a clustered hardware environment, you can achieve this goal without configuring the Integration Services service as a cluster resource. To manage your packages on any node in the cluster from any other node in the cluster, modify the configuration file for the Integration Services service on each node in the cluster. You modify each of these configuration files to point to all available instances of SQL Server on which packages are stored. This solution provides the high availability that most customers need, without the potential problems encountered when the Integration Services service is configured as a cluster resource.
See more http://msdn.microsoft.com/en-us/library/ms345193.aspx