[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 147
  • Last Modified:

Connecting to SSIS and SSAS from Management studio - Access denied

I installed a new version (2008 to 2012) of SQL Server and have been having issues since the beginning. Its on Windows 212 Server VM and it has been causing problems with my permissions since day 1. I configured Mixed mode for authentication and when I open the Database Engine with 'sa' everything is fine. When I try to open SSIS from management studio it doesnt give me the option of opening in SQL auth just windows auth and it gives me an error saying "Access is denied". The same thing happens with SSAS. I wanted to import some of the SSIS packages over to the upgraded server but it seems like I dont have any pernmissions, even though my login is an Admin on the server. Can some let me know what to do cause this has been causing a big problem for me.

Thanks everyone
0
jknj72
Asked:
jknj72
  • 5
  • 4
1 Solution
 
Aaron ShiloCommented:
hi

try to RIGHT click the ssdt and choose RUN AS ADMINISTRATOR
0
 
jknj72Author Commented:
ok I was able to figure out how to get SSIS to run but there is something definitely wrong with my userid login because I created a package and tried to kick it off from a SQL job and I am getting an access denied message. I use sa when I login to SQL management studio and when I do anything else with my logon I get an Accesss Denied? I need to get my user login squared away. Ive never had this issue before with permissions and Im worried that I did something wrong? How can I get my logon permissions fixed on this server for SQL , SSIS, SSAS etc...
0
 
Aaron ShiloCommented:
follow this : https://msdn.microsoft.com/en-us/library/aa337562.aspx
maybe all you need is to fix permissions you have all he info in the same page
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
jknj72Author Commented:
I think I have narrowed it down to the service accounts needing access to the file system. I would just need to know which service accounts are for what processes. I know Ill have to add SQLSERVERAGENT to the folders that have the SSIS packages but are there other service ccounts like MSOLAP(?) or the Integrations services logon?
0
 
jknj72Author Commented:
I added my service accounts to these folders and I still cant run a package from the file system in a SQL job? I know there is still a problem and I want to fix these permission issues. Can anyone help me with this? When I first started I couldnt run anything on any drive other than C and it ended up being a Windows Server 2012 VM issue. My network guy fixed it but its still not fixed. Does anyone have any suggestions on where I can start and get this straightened out? Please help me!!!
0
 
Aaron ShiloCommented:
hi

i had the same issues in VM under drive c: so i moved everything to drive D.
why wouldn't you move the package to a different drive?
0
 
jknj72Author Commented:
And you were able to run a SQL job poitning to the file system and not have to store the packages in SQL(MSDB?) and run those from there?
0
 
Aaron ShiloCommented:
yes.
but lets test this and make sure this is the only issue you have.
:-)
0
 
jknj72Author Commented:
Thanks
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now