I am trying to Connect to Sybase Database (on VM Server) using Sybase SQL Anywhere (JConnect) Driver but everytime it fails with following error:
Product: DbVisualizer Free 9.1.2
Build: #2072 (2013/10/28 18:25)
Java VM: Java HotSpot(TM) 64-Bit Server VM
Java Version: 1.6.0_21
Java Vendor: Sun Microsystems Inc.
OS Name: Windows 7
OS Arch: amd64
OS Version: 6.1
An error occurred while establishing the connection:
Long Message:
JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
Details:
Type: java.sql.SQLException
SQL State: JZ00L
1) Nested Exception:
Long Message:
SQL Anywhere Error -102: Database server connection limit exceeded
Details:
Type: java.sql.SQLWarning
Error Code: 1601
SQL State: 01W03
2) Nested Exception:
Long Message:
SQL Anywhere Error -102: Database server connection limit exceeded
Details:
Type: java.sql.SQLWarning
Error Code: 1601
SQL State: 01W03
Surprising part is my other colleagues tries to connect from their machine then its allowing but for some reason from my machine its not allowing. One more thing I observed is if I try again after 2-3 days it works fine without any changes in configuration.
I have also verified following stuff:
DB Server is running fine
Restarted my machine many times
Restarted DB Visualizer
DB Visualizer Version: 9.1.2 (Freeware)
Thanks in advance.
Related
We have a MS-Access front application using data from a SQL server back-end. We are using ODBC connections for the data communications. The application randomly getting frozen or crashes giving different errors as attached below which very likely seems to be issues related to ODBC connection. Problems can be recreated by running different queries in quick successions.
SQL Server Version: SQL Express 14.0.3356.20
Access Version: Microsoft 365 Apps for Business Version 2011 (Build 13426.20204)
Most common error codes:
10054, 10060, 3146, 3151
ODBC Data Source Type: System DSN
ODBC Driver: ODBC Driver 17 for SQL Server (Version 2017.176.01.01)
Example Connection String for a linked table: ODBC;Description=Test Description;DRIVER=ODBC Driver 17 for SQL Server;SERVER=MY-SERVER;UID=MyUser;Trusted_Connection=No;APP=Microsoft Office;DATABASE=TestDatabase;;TABLE=dbo.TableName
Largest Table Size: 53000 records (Doesn't really matter, fails for even smaller queries, but if you try faster getting results from different queries you can break it)
Error1 Error2 Error3
We have gone through hundres of searches/articles about these and applied the fixes listed below, but still couldn't get the problem solved.
We have tried below solutions as of now which didn't help.
Created firewall rules (Inbound - TCP Port 1433, Outbound - TCP all
ports)
Added TCP Port 1433 - TCP/IP protocol
Enabled Namepipe
Updated SQL Server Express from 14.0.3335.7 to 14.0.3356.20
Made IP4 and IP6 are both enabled
Enabled and checked ODBC Trace Logs
Checked Windows Event Logs
Hope I have included everything that might be useful to get some help resolving this issue.
Note: Not sure if it's related, but the SQL Server itself (in the backend) giving the below error in rare occasions if it helps.
Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=29278; handshake=26244; (.Net SqlClient Data Provider)
Thanks everyone who tried to help. This issue has now been fixed.
For anyone who will come here in future looking for a solution for a similar issue, below is what worked for us.
Added a new instance of SQL Server 2019 (in the same virtual machine
which 2017 sits on)
Enabled UDP Port 1434
Changed virtual port from blank to zero
2017 was still crashing before taking offline with the same settings.
No issues with the 2019 version.
I'm working on a university group project that was previously using MySQL but the team decided to move to MS SQL Server Express. I'm the only team member using a Mac, so I'm trying to get the project to connect to a docker container. I'm working in Visual Studio for Mac.
I've created and started an SQL Express 2017 container with this:
docker run -d --name sqlexpress -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=MSSQLContainer1' -e 'MSSQL_PID=Express' -p 1433:1433 -d mcr.microsoft.com/mssql/server:2017-latest-ubuntu
Which looks like this when running:
CONTAINER ID: e448f6e4df4
IMAGE: mcr.microsoft.com/mssql/server:2017-latest-ubuntu
COMMAND: "/opt/mssql/bin/sqls…"
CREATED: 21 hours ago
STATUS: Up 21 hours
PORTS: 0.0.0.0:1433->1433/tcp
NAMES: sqlexpress
And when I run SQL Server inside the docker and enter SELECT ##VERSION:
Microsoft SQL Server 2017 (RTM-CU16) (KB4508218) - 14.0.3223.3 (X64)
Jul 12 2019 17:43:08
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
I am able to connect to the to the container from both Azure Data Studio or DBeaver without any issues and create a database called HelpdeskSystem.
But I can't for the life of me get our .NET Core app to connect to the database.
This is my current connection string; though, I've tried different variations:
"Server=localhost\\sqlexpress,1433;Database=HelpdeskSystem;User=sa;Password=MSSQLContainer1;"
Also, this is what the connection string that my teammates are using on their Windows machines looks like (and I've tried including those extra properties in my string as well):
"server=localhost\\sqlexpress;Database=HelpdeskSystem;Trusted_Connection=True;Integrated Security=True;MultipleActiveResultSets=true"
When I attempt to run a unit test that requires database connectivity, I get this exception:
InnerException: {System.Net.Sockets.SocketException (0x80004005): Undefined error: 0 at System.Data.SqlClient.SNI.SSRP.GetPortByInstanceName(String browserHostName, String instanceName) at System.Data.SqlClient.SNI.SNIProxy.CreateTcpHandle(DataSource details, Int64 timerExpire, Object callbackObject, Boolean parallel)}
Message: "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: TCP Provider, error: 25 - Connection string is not valid)"
I'm not sure if my string is wrong or if there's some other underlying issue preventing the web app from connecting but I'm definitely able to to connect to the container using Azure Data Studio, so I don't see why the web app wouldn't be able to.
Use this connection string. You can mention tcp infront of loopback ip.
"Server=tcp:127.0.0.1,1433;Database=HelpdeskSystem;User=sa;Password=MSSQLContainer1;"
Getting connection error on oledb source from the SSIS package to import the data from oracle to sql server. It is failing after deploying to server but runs fine when being run from BIDS from local machine. The package is developed in 2008.
Is there any installation needed on server for oracle?
The following error is being displayed
Source: Connection manager Description: SSIS Error Code
DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider
MSDAORA.1 is not registered -- perhaps no 64-bit provider is
available. Error code: 0x00000000. An OLE DB record is available.
Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154
Description: "Class not registered". Code: 0xC020801C OLE DB
Source [1] Description: SSIS Error Code
DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The
AcquireConnection method call to the connection manager failed with
error code 0xC0209303. There may be error messages posted before this
with more information on why the AcquireConnection method call failed.
Code: 0xC0047017 Source: SSIS.Pipeline Description: component
"OLE DB Source" (1) failed validation and returned error code
0xC020801C. End Error Error: 2019-06-18 22:54:18.99 Code:
0xC004700C Source: Pipeline Description: One or more component
failed validation.
When I am validating the package, there it is giving ORA-01017: invalid username/password; but the same credentials are used while running from local machine.
I am running it in 32 bit but still the error persists
Also tried with ProtectionLevel as Dontsavesensitive but no luck
Yes, you need to install an Oracle client. The bare Instant Client should be sufficient as you use the deprecated MSDAORA OLE DB provider from Microsoft.
If you like to use the Oracle Provider for OLE DB (OraOLEDB.Oracle) then you must install the provider. It is not included in the Instant Client.
Ensure that the architecture (i.e. 32-bit or 64-bit) is the same as your application. Your question is not clear in that. You write "I am running it in 32 bit" but the error message "The requested OLE DB provider MSDAORA.1 is not registered -- perhaps no 64-bit provider is available." indicates 64-bit.
Note, old MSDAORA provider from Microsoft exist only for 32-bit. If you need a 64-bit version then you must take the provider from Oracle.
32-bit drivers can be downloaded from 32-bit Oracle Data Access Components, the 64-bit drives are available at 64-bit Oracle Data Access Components
You need to install Oracle drivers on the production machine. If I remember one way to do it is to install the x64 Oracle client software for Windows. Its enormous but it seems to work. This has worked for me.
According to this stackoverflow answer you can manually install the drivers but its a lot of steps:
https://serverfault.com/questions/175257/how-to-install-oracle-ole-drivers-for-use-in-sql-server-2008-r2-x64
I've been having a recurring issue when attempting to query large results from a linked server. I am using SQL Server 2014 and have a POSTGRESQL Server setup as a Linked Server. I have no problem querying against the Linked server on basic/small results or functions. But on the larger jobs the query will attempt to run for a few minutes and eventually the SQL Server will crash and SSMS will produce this error:
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)
Here is the version of SQL Server 2014 that I am currently on. I have found that there was a bug regarding this or at least something similar in Windows Server 2012 and had a hotfix but that doesn't apply to my build (Attempted to apply anyways). The OS being used is Windows Server 2016.
Microsoft SQL Server 2014 (SP1-GDR) (KB4019091) - 12.0.4237.0 (X64)
Jul 5 2017 22:03:42
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 14393: ) (Hypervisor)
Has anyone else had this issue? I have TCP/IP, Named Pipes, and Shared Memory enabled in my SQL Server Configuration Manager already and my Linked Server Provider currently has these options enabled: Dynamic parameter, Allow inprocess, Non transacted updated.
UPDATED INFORMATION:
I have checked through some additional potential causes including 32-bit registry key issues and local user issues. I am still encountering this same issue after these changes as well.
Date 8/28/2017 2:32:24 PM
Log Windows NT (Application)
Source Application Error
Category (100)
Event 1000
Computer DBM
Message
Faulting application name: sqlservr.exe, version: 2014.120.4237.0, time stamp: 0x595e7459
Faulting module name: ntdll.dll, version: 10.0.14393.1532, time stamp: 0x5965abad
Exception code: 0xc0000374
Fault offset: 0x00000000000f8363
Faulting process id: 0x13c0
Faulting application start time: 0x01d32034049e1344
Faulting application path: E:\Microsoft SQL Server\MSSQL12.ESCENTRAL\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3489af8e-639f-4a54-ac3e-fda719cf75dc
Faulting package full name:
Faulting package-relative application ID:
This is the application error that I am seeing in my SQL Logs when the crash occurs
I have a machine which has VS2010 and sql server 2005, 2008 installed.
I were able to connect every remote database server from my application prior to installing VS2012. After installing VS2012 I am getting "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." on code where i have database call.
If i try to connect local database it connects fine.
Also what i tried is connect via server explorer in Visual studio 2010. It connects to local source successfully.
But when i try to connect to remote source it crashes VS2010 and Get following error in Event viewer
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: netconfig.dll, version: 1.0.0.5, time stamp: 0x50a60f11
Exception code: 0xc0000005
Fault offset: 0x0000fdac
Faulting process id: 0xb40
Faulting application start time: 0x01ceae0dd4041a18
Faulting application path: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\system32\drivers\imonagent\netconfig.dll
Report Id: 5fec2d1f-1a01-11e3-bf8e-4c001050978f
I have read following post and downloaded utility but it also not indicates any error in my machine
http://social.msdn.microsoft.com/Forums/vstudio/en-US/81e1b380-afe1-46ad-9c91-a588e0a5aa4b/how-to-reenable-remote-sql-server-connections-after-installing-visual-studio-2012
Please help me what to do with this problem
Problem not only occurs while i am debugging but also if somebody trying to view hosted site in my machine which has some remote database server connection
Have a luck via running following command (netsh Winsock reset) from command prompt mentioned in
social.msdn.microsoft.com/Forums/vstudio/en-US/2d11b6f9-3ada-4682-b643-c721a97af4ba/cant-connect-to-database-after-installing-vs-11-pro-beta