Visual Studio BI tool error - sql-server

Good Day!
When you download in Web Service Task a WSDLfile - error
"SSL certificate response obtained from the server was not valid.
Cannot process the request."
What could be problem?
Visual Studio version 2013

Sounds like the SSL certificate on the server is not valid. This is probably because it's a temporary certificate, or you self-signed it.
Add the signer of the temporary certificate to the trusted authorities list on the computer running the package.
Or import the temporary certificate as a trusted certificate.

This error is caused by the lack of support for Cryptographic Protocols of the SSIS Web Service Task. A better approach would be to rewrite it as an SSIS Script Task with the help of the WSDL.exe Tool and then including the generated file (.cs) into your Script Task project.
The wsdl tool is available via the Visual Studio Command prompt (under visual studio/tools in the start menu):
wsdl /language:CS /out:<>C# path file> <WSDL file path>
Then copy-paste the Generated C# class into the Solution Explorer tree for the SSIS Script Task Project while editing.
Finally, enable the TLS Protocol in the class constructor according the .NET Version as showed on https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/.

Related

Team Foundation Server suddenly failing to connect (Error: TF400324)

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.

Fix this Entity Framework migration, 00000000000000_CreateIdentitySchema, in Visual Studio?

I'm starting with the default Blazor app in Visual Studio 16.3.7 with authentication:
I go to the registration page, enter the email and password, and click the Register button and up comes the following error:
Next I go to Package Manager Console in Visual Studio, and run Update-Database, getting the following error:
CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'C:\Users\Halaspnet-BlazorAuthentication-0X0X0X0X0X0-X0X0-X0X0-X0X0-0X0X0X0X0X0.mdf'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
The message points to the culprit, a backslash is missing from the file specification. It should be C:\Users\Hal\aspnet... , not C:\Users\Halaspnet...
So, how do I fix this? I can't find the string "CREATE DATABASE" anywhere in my solution.
Also, how do I get this to Microsoft as a bug report?
Problem solved!
I created the database that the 00000000000000_CreateIdentitySchema.cs wanted using Visual Studio's SQL Server Object Explorer. Then I ran Update-Database in the Package Manager Console, and it completed successfully.
The problem seems to be that I was using the Express edition of SQL Server.
This link got me to the fix for this problem:
Creating A Step-By-Step End-To-End Database Server-Side Blazor Application

The connection "Connection" cannot be found. Verify that the connection manager has a connection with that name

I'm using an ODATA connection manager in SSIS to connect to a private Sharepoint Online, I manage to test the connection when I create the connection manager and to do a preview of my list when I'm in the designer. When I try to execute the package in VS I'm getting the following error:
The connection "Connection" cannot be found. Verify that the connection manager has a connection with that name
OData source failed validation and returned code 0xc020801A.
I already created a new package and I'm sure that there is no any other connection in logging tab, btw my other packages (which dont use an OData connection mgr. works perfectly)
My environment is configured as follows:
VS Studio 2017 Community edition
SQL Server Data Tools 15.1.61810.11040
Sharepoint Online
I installed also "SharePoint Server 2013 Client Components SDK" because with "SharePoint Online Client Components SDK" I could not even configure the connection manager in SSIS, since I was having the following error:
Could not load file or assembly 'Microsoft.SharePoint.Client.Runtime', Version=15.0.0.0
After installing the SDK 2013 I could configure correctly the connection manager.
Thank you in advance, any help is appreciated.
Please make sure the OData connection can be found in the "connection managers" panel in the package, if it does, try to create a new solution and check if this error can be reproduced in it.
For the details on creating OData Source, please check this link:
Tutorial: Using the OData Source
My sample test demo for your reference:
look this https://social.msdn.microsoft.com/Forums/en-US/d8d524f0-d373-47d1-b239-424b26ac59a7/the-connection-quotconnectionquot-cannot-be-found-verify-that-the-connection-manager-has-a?forum=sqlintegrationservices
i have same problem
becuase languafe of IDE and SQL server is different (SQL Server - english, in IDE your national language)
simple solution is change in your dtsx name to "Connection"
I had this problem but with the word "Conexión" in Spanish. I use Visual Studio 2019 in English, but I change the language to Spanish and everything worked.

JDBC URL connection to SQL Server using Windows Authentication in JIRA plugin

I am currently at my wits end. I am trying to connect a JIRA plugin (Atlassian Java SDK) to a SQL Server 2012 database. It's required that I use Windows Authentication, but JIRA is logging:
com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication.
I've read that this can be combatted by adding the sqljdbc_auth.dll file to the program's library path, but there are no references specifically for JIRA plugins on how to do this other than for the base JIRA dbconfig.xml, which I am not using. This is a connection made within the plugin using the code:
String url = String.format("jdbc:sqlserver://%s:1433;databaseName=%s;integratedSecurity=true;domain=XXXX;", server, database);
I have tried to add the dll file to the following locations, all to no avail:
C:/{JIRA INSTALL PATH}/bin
C:/{JIRA INSTALL PATH}/jre/bin
C:/{JAVA INSTALL PATH}/jre_8.x.x/bin
What gives?
UPDATE:
I have gone in and added the JDBC JAR/DLL to the classpath/library path respectively in the JIRA Windows service configuration tool. Still getting the same error.
UPDATE 2:
I have switched to using the JTDS driver to see if JIRA was just not able to use the standard JDBC driver for some reason, but getting a similar error:
java.sql.SQLException: I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property.
I have also created a new Java app to test this in a controlled environment, but do not get this error after adding the ntlmauth.dll file to the C:\Windows\System32 directory. This leads me to believe this may be a bug within JIRA or I have something configured improperly.
Here is my own conclusion after many weeks of searching:
It is (currently) impossible to do this without the use of a password (which is sometimes the entire point of using Windows/Active Directory credentials). You can however use the JTDS driver in junction with a domain, username, and password to authenticate to servers that require windows authentication. This does not solve the core issue, but from what I can tell is the only current solution close enough to it.

asp.net 4 mvc 2 error

when I run the app on server I get:
Could not load file or assembly 'Microsoft.SqlServer.Replication.DLL' or one of its dependencies. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.SqlServer.Replication.DLL' or one of its dependencies. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)
Some points:
On machines with sql server 2005 installed (from which that dll is copied) the app works. But the server does not have it, so I need to get it to work without sql server.
The file is in wwwroot/bin folder: Microsoft.SqlServer.Replication.dll
Do I need to include the file in References folder in VS? Set it to CopyLocal?
Any advice or solutions would be greatly appreciated
--MB
The Microsoft.SqlServer.Replication.DLL is part of the Replication Management Objects which in turn are part of the SMO pack. The only supported redistribution path for SMO is to use the installer that comes with the SQL Server feature pack download, see Distributing an Application That Uses SQL Server Management Objects. You must install the SMO redistributable packet on the server.

Resources