This is my first time starting from scratch with the "new" SSIS Integration Services Catalogs introduced in SQL 2012. I've developed packages with this new model for years but never set up my own environment.
I have packages that work in Visual Studio 2019 just fine and have project connection managers that will span across all of the packages in this project. When I deploy the packages the connection managers are empty in the package configuration.
Here's my project with the connections setup.
And here's what it looks like when I deploy the packages using the Project connections
If I change the connections to "Package Connections", the connections deploy as expected.
When I do this, the connection managers is populated
What am I missing?
Notice the Scope - GetWorkerData.dtsx That's showing you what is configurable at the scope of the package. Since the connection managers at that point are Project level, you need to change the Scope to something different (I don't have a project level CM handy). Alternatively, right click on the project "Pull Data from ADP" and select configure from there. Then it will pop open that wizard with the correct scope selected.
Related
After using Team Foundation Server (TFS) for years, we suddenly lost the ability to connect either through Visual Studio (VS) or via URL. To the best of my knowledge, no changes were made to the virtual server that supports TFS.
In VS the error is:
TF400324: TF services are not available from server... Unable to connect to the remote server...
If I use the {server}:8080/tfs or localhost:8080/tfs url in a browser it tells me the connection was refused.
In the SQL Management Studio both the Tfs_Configuration and Tfs_DefaultCollection databases appear to be connected, and show a "Ready" status. In the TFS Administration Console the DefaultCollection state is "Online".
Perhaps the best clue is that if I use netstat to see which ports are in use on the server, port 8080 is not listed at all. Is there a listener service that needs to be started?
I see that the following services are currently disabled: UPnP Device Host, SSDP Discovery, Internet Connection Sharing, SSDP Discovery, Internet Connection Sharing, Smart Card, Routing and Remote Access, Net.Tcp Port Sharing Service, and Computer Browser.
Of course, we have tried a reboot to no avail.
Any troubleshooting suggestions will be much appreciated, as this has begun to impact our productivity. Thanks in advance!
Edition: TFS 2015
Version: 14.114.28805.0 (Update 4.2)
Update:
I should mention that the firewall has been disabled in attempting to diagnose the issue.
Also, there are errors associated with TFS in the Even Viewer, but they are not at all clear. Here are is a snippet:
VssRequestContext.HostManagement.Microsoft.TeamFoundation.JobService.Extensions.Core.IdentitySyncJobExtension.Run:1
Registry.TeamFoundationRegistryService.Write:1
Default.SqlResourceComponent.Execute prc_UpdateRegistry ds:LT-TFS2
db:Tfs_Configuration:2 Default.SqlResourceComponent.Execute:-3
Registry.TeamFoundationRegistryService.Write:-3
GroupComponent.SqlResourceComponent.GetGroupsToSync:3
GroupComponent.SqlResourceComponent.Execute prc_GetGroupsToSync
ds:LT-TFS2 db:Tfs_Configuration:3
GroupComponent.SqlResourceComponent.Execute:-4
GroupComponent.SqlResourceComponent.GetGroupsToSync:-4
GroupComponent.SqlResourceComponent.ReadGroups:4
GroupComponent.SqlResourceComponent.Execute prc_ReadGroups ds:LT-TFS2
db:Tfs_Configuration:4 GroupComponent.SqlResourceComponent.Execute:-5
SOLVED!
I found that the TFS site was disabled within the IIS Manager. When I tried to enable it, it reported that the World Wide Web Publishing Service was disabled. Enabling both resolved the issue.
This error is usually related to TFS cache. You could give a try following below steps:
Close all instances of Visual Studio
Open the Task Manager and check if any TFS Services are running. Select each of them and click on End Process Tree
Browse to the folder %LocalAppData%\Microsoft\Team Foundation\ and then select the folder with your TFS version and go inside
the Cache folder. for example, the path was
%LocalAppData%\Microsoft\Team Foundation\x.0\Cache and it should be
the same on your machine with the difference of the TFS version folder
name.
Delete everything in that Cache folder.
Start Visual Studio and run it with Admin mode.
Besides, in case of your TFS is configured with self-signed TLS/SSL certificate.
If this is the case, you need install that certificate to the Trusted Root Certification Authorities store on the client machine, where you have VS.
For this scenario, you could refer this answer.
Moreover, please also check if there are any errors in the event viewer in your TFS server. This may help to narrow down the issue.
I have a new solution in SSDT where I am mapping data moving from one SQL Server to another. I will have several SSIS packages in the project, and so want to share the connections to both servers across all packages.
Here are the project level connections I have created:
When I create a new task in a Data Flow I am having trouble explicitly using the project version of my connections. I am in the prompt to add a new source, but not all my project level connections appear. I am able to add a connection, but it seems to only be scoped to the package level, which is not what I want. See conn1 is missing from the list:
How do I explicitly use project level Connection Managers in my sources? Why don't the ones I created appear in my options as an existing source?
it seems the connection (conn1) is not SQL Server Native Client 11.0
this source assistant Dialog retrieves only all the connections of type (SQL Server Native Client 11.0) which Microsoft recommends to use.
Regards
I have a problem while trying to deploy a ssis package from a job. I have created the ssidb folder of the package, and I have not problems to execute it successfully. But when I use a job, by choosing the package from the ssisdb folder, I always get the same error message:
Failed to acquire connection "database". Connection may not be
configured correctly or you may not have the right permissions on this
connection.
The ProtectionLevel of the project and the package is "DontSaveSensitive", but apart of this I do not know what else can I do.
I would appreciate any advice you could give me.
Using SQL Server 2014.
Regards.
It sound's like you have almost worked this out yourself :-) The connection string will most likely not be valid because, when you deployed the package, the password would not have been carried across.
Easiest option if running via SSDB:
On the deployed server right click on the package.
Click configure
Amend your connection manager accordingly.
Easiest option if running via SQL Agent Job:
Right click job and select properties
Click Steps
Edit your step.
Click on configuration tab.
click on connection managers tab.
Amend accordingly.
There are, of course, other ways - have a look up Environments.
FWIW We store all our packages with sensitive data secured by a password.
I am using Package Deployment Model for one of my project in SSIS.
When I am importing the package on SSISDB under Integration Service Catalogs.
It imports successfully.
Then, I want to create a Job under SQL Job Agents to Run this Package periodically. But there I am not getting any Connection managers which I have used in my package.
My SSIS package has 2 connections :
Connection to the Sharepoint Site (Which is the source of the data)
Connection to the SQL Server ( Which is the destination of the data)
If I am not getting the connection manager while creating the job, then How can I change the connection Servers from local to Production ones from here?
Am I missing something on configuration part to include Connection Managers in the Deployment Package?
Please help here.
Thank you,
Mittal.
In SSMS open the Integration Services Catalogs -> SSISDB -> CatalogName -> Projects, then right click on the project OR Find the package in the SSIS Catalog and right click on it, then select the Configure... entry in the popup menu.
You can select the package in the Scope dropdown list, then you can find the connections under the Connection Managers tab.
Also please read this thread: How to configure SSIS 2012 project to run under different environment configurations?
I have an issue where we tried to upgrade our TFS 2005 server to 2008. During the install we encountered the error that it could not configure SQL Reporting Services. The log files showed that during the creation/configuration of the virtual directories for SQL Reporting Services (the Reports directory to be exact) a FileNotFoundException was thrown. The directory was actually created. SQL Reporting services were running just fine before the install. I tried to go in and reconfigure manually with the report server configuration tool but while it will create both directories, it still fails with a FileNotFoundException. I manually configure the .config files to point to the current server and I am able to get the sql report services web site running. We tried several things: messing with permissions, application pools, reinstalling the .NET framework, aspnet_regiis, etc. but nothing has changed the error.
Any ideas?
I recently encountered a similar problem. After installing a new RS instance and applying SQL Server sp2 and the KB954606 hotfix, I attempted to configure the RS instance, but creating the virtual directory failed. As in your case, the virtual directory was created, but the RS configuration tool threw an error.
In my case, deleting the newly-created virtual directory using IIS manager and then rebooting the server fixed everything. I was able to successfully create the virtual directories using RS Configuration Tool following the reboot.