We have a girl here who runs a report successfully, then changes the date on her pc, then tries the report again and gets a Connection failed error.
The report is ran in MS Access 2003
The ODBC itself uses Windows Authentication
The linked table uses a UID different than her Windows login
The error when running the report: SQLState '28000' SQL Server Error: 18452 "[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection."
Error received when testing the ODBC: SQLState '08004' SQL Server Error: 4060 "Server rejected the connection; Access to selected database has been denied."
The SQL Log had this error: "SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: ##.##.##.##]"
I am able to recreate the failure on my machine.
I'm thinking it's something between the Windows Authentication/Active Directory/ODBC but I'm not very experienced in the first 2.
And yes, I know this isn't an ideal situation. This will all be converted to C#.NET at some point.
TIA for any ideas.
Related
I have installed SQL Server 2012 Express version where I have a local db instance separately. When I connect to SQL Server Express, it connected without problem, but when I try to connect to local db, I get the following error:
The attempt to attach to the database failed with the following information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error:2)
The system cannot find the file specified.
When I open SQL Server Configuration Manager, the local db service is not running but it is stopped. When I start that it shows error
The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details
When I open its properties and select log on as built in with local system after clicking apply it shows error
The process terminated unexpectedly.[0x8007042b].
I am trying to create an OLE DB connection in SSIS that I want to use for this package I am building which basically is supposed to do an ETL having it's source from Excel and the output in a SQL table. However, I am getting the error as below when trying to connect to the server and check in. I am using windows authentication and trying to connect locally using the '.' I also couldn't find the sql server configuration manager in my computer. I reinstalled my management studio 2018 version, but the didn't fix it either. Any insights would help on resolving this issue.
Thanks
Error message:
TITLE: Connection Manager
Test connection failed because of an error in initializing provider.
Login timeout expired A network-related or instance-specific error has
occurred while establishing a connection to SQL Server. Server is not
found or not accessible. Check if instance name is correct and if SQL
Server is configured to allow remote connections. For more information
see SQL Server Books Online. Named Pipes Provider: Could not open a
connection to SQL Server.
I am getting the following error when I am going to create a new data source by connecting to SQL on premises database using Tableau online.
Can’t connect to Microsoft SQL Server
Detailed Error Message
There was an unknown connection error to the database. The error message below has additional information, but you might need to ask the database administrator to review the database logs. %1
[Microsoft][ODBC Driver 17 for SQL Server]MAX_PROVS: Error Locating Server/Instance Specified [xFFFFFFFF].
[Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired
[Microsoft][ODBC Driver 17 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
Unable to connect to the Microsoft SQL Server server "my server name". Check that the server is running and that you have access privileges to the requested database.
2019-02-25 07:38:34.520, (XHObPax0w59qQPz8O0dV6QAAAIk,0:0)
Any idea to solve this issue?
You will need to use 'Tableau Bridge' to connect from online to on-prem.
https://onlinehelp.tableau.com/current/online/en-us/qs_refresh_local_data.htm
It's likely that you need to whitelist the Tableau Online IP addresses in your SQL Server instance. See the link for the addresses.
Tableau Whitelist Info
I have a very weird issue with SSAS Tabular connecting to a SQL Server source database. I've spent almost the entire day on this, and searched online in various ways to find a helpful answer, but none of the suggestions solved this mysterious problem for me.
It used to work fine, but I tried various connection settings (Windows vs SQL authentication, and different impersonation modes), but now I no longer can get it to work (even if I revert back to the previous bim file in source control).
When I process a table from the WORKSPACE database (through SSMS), it works. But when I process a table from the DEPLOYED database (still through SSMS), it does NOT work.
The connection I am using is:
-SQL Server Native Client 11.0
-Windows Authentication
-Impersonation mode of a Windows account (which has the appropriate permissions)
The source database is in a SQL Server database located on a different server (but in the same network).
I have searched everywhere online, but didn't find anything that could help me.
I have tried changing the connection driver (OLE DB Provider for SQL Server), and I have restarted the SSAS Tabular service.
The full error message I get when trying to process a table on the deployed database is:
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: Login timeout expired; HYT00; A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [5]. ; 08001.
A connection could not be made to the data source with the Name of 'DataWarehouse'.
'.
In fact, after I tried a second time to restart the SSAS Tabular service, the error message I get after attempting to process a table is slightly different:
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; SSL Provider: The requested security package does not exist
; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.
A connection could not be made to the data source with the Name of 'DataWarehouse'.
'.
According to your description, it seems to be related to connection problem. You need to check whether corresponding SQL server service and SSAS Service is running(check server which contains "DataWarehouse" is running and can be connected). You could go to "SQL Server Configuration Manager " to restart them.
In addition, you also need to make sure your current windows credential can access this database(if you use window credential). And check whether this server enable remote connect.
Zoe
I have been unable to make a successful connection to my SQL Server (2005) using Win32::SqlServer. The server is located on another machine. I am using the latest version of ActivePerl and the module.
Using an ADO.NET provider (in C#), I can make a successful connection with the connection string:
Data Source=1.2.3.4,1553;Initial Catalog=dbname;User Id=username;Password=pw;
In an effort to convert this in to Perl, I've attempted the following:
my $conn = Win32::SqlServer::sql_init();
$conn->setloginproperty('ConnectionString', 'Data Source=1.2.3.4,1553;Initial Catalog=dbname;User Id=username;Password=pw;');
print $conn->connect();
As well, I've attempted to set the server, login information, and initial database individually using setloginproperty().
These all fail with the message after the timeout period has been met:
SQL Server message 2, Severity 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Message 08001 from 'Microsoft SQL Native Client', Severity: 16
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Message HYT00 from 'Microsoft SQL Native Client', Severity: 16
Login timeout expired
Terminating on fatal error at mkadm.pl line 54
The reason the early example was failing is because the sql_init() method expects arguments passed in to it.
In order to use the setloginproperty() to inject settings, ->new() should be used to create an uninitialized SqlServer object!