Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

I am not able to login to SSIS in SSMS but from visual studio am able to do manage ssisdb

Posted on 2016-11-20
6
Medium Priority
?
77 Views
Last Modified: 2016-11-24
I am a novice in ssis. i installed sqlserver 2016 and visual studio 2015 and ssdt for visual studion 2015 in my machine.  but when i log in to ssms choosing ssis it gives errors. i gave machine name and instance name and windows authenication. then it said multi instance is not supported. so i removed instance name and gave machine name only as the server name.  then it says it can happen when you try to connect to sql server 2005. i tried giving instance name of ssis. then it said RPC call failed. but you see i have installed sql server 2016 only. I am totally at a lose. but when i deploy project thru visual studio am able to do manage ssisdb and successfully deploy. but i want to create folders and manage ssis though ssms how to do it? am i missing something? last one week I am struggling with this probleem . please help
0
Comment
Question by:Gopakumar Pandarikkal
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 30

Assisted Solution

by:Pawan Kumar
Pawan Kumar earned 1000 total points
ID: 41895382
Then you must be using different users .. from which user you are login in SSIS via SSMS or which login is used in VS?
0
 

Author Comment

by:Gopakumar Pandarikkal
ID: 41896505
@pawan  thanks pawan for responding. but there is only one user. it is windows authentication. pleasec see the error message attached. thanks in advance
ssis.png
0
 
LVL 13

Accepted Solution

by:
Arifhusen Ansari earned 1000 total points
ID: 41900120
Hi GopalKumar,

Based on explanation. I will guess some points.

1) You are using SQL server 2016 and as you have mentioned that you are using ssisdb for deployment. It means that you are using Project Deployment method and not package deployment method.

2)  For SQL2012 and later version. They introduced Project deployment method, this doesn't require you to connect Integration Service.

3) Just connect SQL server database engine, on which you have deployed your ssis project. You donot even need to connect Integration  services for Project Deployment method. If you have already deployed the package, you will see "SSISDB" folder created in "Integration Service Catalog"

You can create folders,Projects,Environments whatever you want to do.

Please refer the screenshot below.

2016-11-24_11-43-47.png
Regarding why you can not connect Integration service. I have to look into it.
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 

Author Comment

by:Gopakumar Pandarikkal
ID: 41901049
Thank you Ansari for the prompt response and willingness to help me.
Yes it is version mismatch issue
I got this table from MSDN
PFA
installation of sqlserver,Visual studio and SSDT, and ssms works perfectly for particular combinations of versions

I chose this
sql server 2014   , visual studio 2015,  SQL Server Data Tools for Visual Studio 2015, SSMS 2014(installed in this order only )
It worked fine. Now i am able to login to integration services from SSMS. I shouldn't give instance name along with server name.
I installed sql server with Mixed authentication.

Again thanking you. thanking expert exchange
0
 
LVL 13

Expert Comment

by:Arifhusen Ansari
ID: 41901144
Accept an answer as a solution.
Which ever helped you.

Thanks,
Arif
0
 

Author Closing Comment

by:Gopakumar Pandarikkal
ID: 41901152
Thank you Ansari,Thank you pawan
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question