I have Windows server 2008 R2 and SQL Server 2008 R2 and want to change remote access of SSIS. In windows xp I can use ControlPanel\Administrative Tools\Component Service\My Computer\DCOM Config\Microsoft SQL Server Integration Service 11.0(Security Tab) for config remote access to SSIS. but in windows server 2008 R2 I don't know how can active remote access.
Thanks in advance.
You can go to run - type dcomcnfg.exe - this will launch the component manager and you can use the following steps:
++++
Open Control Panel, double-click Administrative Tools, and then double-click Component Services to start the Component Services MMC snap-in.
Expand the Component Services node in the left pane of the console. Expand the Computers node, expand My Computer, and then click the DCOM Config node.
Select the DCOM Config node, and then select SQL Server Integration Services 11.0 in the list of applications that can be configured.
Right-click on Microsoft SQL Server Integration Services 11.0 and select Properties.
In the Microsoft SQL Server Integration Services 11.0 Properties dialog box, select the Security tab.
Under Launch and Activation Permissions, select Customize, then click Edit to open the Launch Permission dialog box.
In the Launch Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Launch, Remote Launch, Local Activation, and Remote Activation. The Launch rights grant or deny permission to start and stop the service; the Activation rights grant or deny permission to connect to the service.
Click OK to close the dialog box.
Under Access Permissions, repeat steps 7 and 8 to assign the appropriate permissions to the appropriate users and groups.
Close the MMC snap-in.
Restart the Integration Services service.
+++++++++++++++++++
Reference: http://msdn.microsoft.com/en-us/library/aa337083.aspx
You can search on dcomcnfg.exe SSIS 2008 R2 for additional hits.
Here you go:
How to configure DTC on Windows 2008 (web.archive.org mirror)
Related
Some background:
I am running SQL Server 2012
Let's call the service account running SQL Server Agent: myserv-sa-sqlagent
Right now I have it set up so that I CAN: 1) log onto the server as myserv-sa-sqlagent, and 2) connect to the SSIS server via SSMS, and 3) SUCCESSFULLY RUN the package, let's call it myssispack.dtsx from Stored Packages -> MSDB -> [Folder] => myssispack.dtsx
In short then, if I wanted to log into the server as the service account (myserv-sa-sqlagent) and manually right click on each package in the SSIS server and "Run Package" -- I could successfully do that.
I cannot though call the package from SQL Server Agent job via a SSIS Package type step. Temporarily, I have made myserv-sa-sqlagent an administrator on the server.
Error message when trying to run the package from SQL Server Agent:
Connecting to the Integration Services service on the computer "[my server]" failed with the following error: "Access is denied." By default, only administrators have access to the Integration Services service. On Windows Vista and later, the process must be running with administrative privileges in order to connect to the Integration Services service. See the help topic for information on how to configure access to the service.
By default when you installed SQL Server all users in the Users group had access to the Integration Services service. When you install the current release of SQL Server, users do not have access to the Integration Services service. The service is secure by default. After SQL Server is installed, the administrator must grant access to the service.
To grant access to the Integration Services service:
Source MSDN
Run Dcomcnfg.exe. Dcomcnfg.exe provides a user interface for modifying certain settings in the registry.
In the Component Services dialog, expand the Component Services > Computers > My Computer > DCOM Config node.
Right-click Microsoft SQL Server Integration Services 11.0, and then click Properties.
On the Security tab, click Edit in the Launch and Activation Permissions area.
Add users and assign appropriate permissions, and then click Ok.
Repeat steps 4 - 5 for Access Permissions.
Restart SQL Server Management Studio.
Restart the Integration Services Service.
I had recently installed SQL server 2012 and I used mostly the default settings. Database works fine and I can happily connect using SSMS (SQL Server Management Studio) but when I connect to the Integration Services Server I get this message
Connecting to the Integration Services service on the computer
"localhost" failed with the following error: "Access is denied."
By default, only administrators have access to the Integration
Services service. On Windows Vista and later, the process must be
running with administrative privileges in order to connect to the
Integration Services service. See the help topic for information on
how to configure access to the service.
here is the screenshot
I am not sure why but I am the domain admin and have full rights over the server. Also why when I connect from my Desktop it can successfully connect, only if I connect from the server itself which gives me this issues. How do I fix this so that I can make SSMS on the server connect to its Integration Services instance.
As I understand it, User Access Control, or UAC, can basically intercept requests for your group membership so in this case, it appears it was preventing your membership getting passed to SQL Server.
Others have noted in their comments that you may still need to right click and run SSMS as an Administrator.
As noted by an astute observer "This is a quick-fix, not a real solution. People shouldn't just be running stuff as administrator. These security walls are in place for a reason" And I agree. UAC is designed to get Windows users into a Principle of least privilege mindset - only escalate to a powerful account when required. The issue is that SSMS is known to not "play well" with UAC. As I see it, this leaves you with three options
You can turn off UAC and get your work done
Leave UAC on and tell your boss you are unable to work
Write your own query tool that is not affected by UAC
Go to all programs Click on Microsoft SQL Server 2012 folder Right click on SQL Server Management Studio Click on Run as Administrator
This should take care of problem for now. (With this you need to always repeat the same process). To avoid this every time and for a more persistent solution you need to get permission(s). Please do the following process and you should be good.
In previous versions of SQL Server, by default when you installed SQL Server all users in the Users group had access to the Integration Services service. When you install the current release of SQL Server, users do not have access to the Integration Services service. The service is secure by default. After SQL Server is installed, the administrator must grant access to the service.
To grant access to the Integration Services service
Run Dcomcnfg.exe. Dcomcnfg.exe provides a user interface for modifying certain settings in the registry.
In the Component Services dialog, expand the Component Services > Computers > My Computer > DCOM Config node.
Right-click Microsoft SQL Server Integration Services 11.0, and then click Properties.
On the Security tab, click Edit in the Launch and Activation Permissions area.
Add users and assign appropriate permissions, and then click Ok.
Repeat steps 4 - 5 for Access Permissions.
Restart SQL Server Management Studio.
Restart the Integration Services Service.
(Source MSDN)
I hope this will help
Right Click on the Sql Server Management Studio and select Run as Administrator and try to connect
if it is installed on the local instance
You should check to see what user the SSIS Service is running under. Go to Start > Run > Type "services.msc" and scroll down to the SQL Server Integration Services 11.0 entry. Right click and check the properties to find out what user it's running under. The second tab should be the LogOn tab. Since you're just running on a local instance, you can set your user as the LogOn User account and SSIS will have the same permissions that you do.
Lost a day of work on that problem. My package has a .NET script task to copy file from a shared network folder to a local folder and I was stuck with the "access denied" exception every time I tried to execute the package from the server (Through SQL Studio). The package works fine when running locally.
Tried many things picked up here and there and at the end of the day what worked is to create a Job (owner is sa) which execute the package as SSISExecutor.
I have to mention that the file on the network has read access for everyone, and that I still don't understand what was wrong.
My problem is I cannot login into SQL Server after I've created a user. The user creation is successful, since the new user is listed under security/logins.
How to solve this issue ???
Login failed for user 'sims'. The user is not associated with a
trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)
SQL Server was not configured to allow mixed authentication. Here are steps to fix:
Right-click on SQL Server instance at root of Object Explorer,
click on Properties.
Select Security from the left pane.
Select the SQL Server and Windows Authentication mode radio button, and
click OK.
Open up Services and restart the SQL Service (SQLEXPRESS) Windows service.
Try setting your authentication mode to mixed mode. Your server does probably not accept logins using sql server accounts.
Open properties
Go to "Security"
Select "SQL Server and Windows Authentication mode"
Right click Server for properties...
properties
What's the permission required to stop/start an SQL Server service?
I just created a login (SQL Authentication, public server role, no special permission, no database mapping) and found I can stop/restart the SQL instance through SSMS with this login. This is not what I want.
SSMS does not restart the service with the login you ue to perform queries with it, it uses the desktop/rdp user.
If you are logged into your desktop as a domain admin or local admin of the server your are connected to, and run SSMS from that desktop, you will be able to restart the SQL service. You can also restart the sql service as that user from the services.msc MMC.
I have some database problems.
I have SQL Server Developer installed on my local machine. When I open SQL Server Management Studio and log in with windows authentication there is no problem. I have created a new database there and added a new user. The new user is owner of the database.
When I disconnect from my windows session and try to log in with the newly created user in SQL Server authentication mode I get the 'cannot connect to (local)'
Please help!
Have you enabled SQL Server authentication? (During installation and/or afterwards)
If not, connect using windows authentication, right-click on the server instance, go to properties and change auth mode...