SQLState=08S02
Microsoft native client 10.0
Physical Connection is not usable [xFFFFFFFF]
I have database on different server and application on different server.
it is security reason, so both database and application will not on same server.
Application is configured in window schedular which run every night round about 11 PM.
Hw to handle this in code or any other solution?
Related
Running Windows 2019 servers in my lab.
An application has a SQL client. But the client cannot find an ODBC connection.
Created a "System DSN" via the ODBC Data Source administrator (32-bit). As I usually do in my lab. I found some articles on registry placement, all appear OK. I compare another server and that machine has no issue.
Both 2019 servers are on the latest MS hotfixes.
I'm found no specific articles that can help me isolate the fault. I see no errors in the Windows Event Logs.
ODBC System DSN passes testing in the configuration window.
Can anyone help?
The overall picture that I am trying to achieve is for me and three other people to connect remotely to a client's network and use Lotus Designer 8.5.3 FP6 to access the client's Domino servers. We will each have our own logons to the client's Citrix environment which runs a Windows 7 desktop, then using Remote Desktop concurrently connect to PC(s) within the client's network to run Lotus Designer from there. (Lotus Designer is not available on the Citrix desktop.)
The issue is that the client is wanting to avoid having four separate physical PCs set up waiting for us to log in. They have Windows Server 2012 Standard virtual machines available.
First question: Can the Lotus Designer client 8.5.3 FP6 run on Windows Server 2012 Standard VM? I know that it is not officially supported, but is there any reason why it wouldn't work?
If it can run, then the second question: Is it possible for all four people to use remote desktop to concurrently log in to one Windows Server 2012 Standard VM, which has a separate instance of Lotus Designer 8.5.3 FP6 installed per user? (and of course run the separate instances of Designer concurrently) Or would we need four separate Windows Server 2102 Standard VMs?
Thanks for any light that can be shed on these questions.
First of all: Designer 8.5.3FP6 will run on Windows Server 2012 although not officially supported.
To start the designer concurrently you need to "fake" a multiuser- installation:
Before installing create an extra drive, e.g. by using "subst".
You might need to do this twice, once for the user himself, once in an elevated prompt, so that installer can access it.
e.g. subst D: C:\NotesUserA
Then you install program and data directory into D:
After that you copy C:\NotesUserA\IBM\Notes to C:\NotesUserB\IBM\Notes, C:\NotesUserC\IBM\Notes, and so on.
In loginscript make sure, that for every user the right Folder is mapped as "D:".
That way it should be possible to start Notes concurrently in different sessions.
Trying to setup an ODBC connection for UPS to access our SQL server, from our shipping client computer.
I have scoured as much as I can an ran across:
runas /netonly /user:domain\account "c:\windows\system32\odbcad32.exe"
Now, using this method, on my current client computer, I was able to setup an odbc connection successfully using SQL Native Client 11 (5058). I am using Win 10. Our shipping computer, with multiple manifest systems on it, is still using Win 7, but otherwise is setup the same on the domain.
Using the same process as above, the connection ultimately times out, and states that the server is not online/not available/not allowing remote connections.
Is there a step I'm missing? Both clients have same rules for firewall, both are using the same user/password in the runas cmd. The only difference between the two clients is Win 10 vs. Win 7, and the current logged in user is different (but that shouldn't matter with the runas cmd?)
Thanks!
So after several days/hours of trying various solutions and suggestions from all over the interwebs, I came across this solution/tips.
In SQL Server Configuration, checking the network configuration protocols/clients/aliases. In my case, there was an aliases established for 32-bit, and not 64-bit. I disabled the 32-bit one.
I then found suggestions to us the ip (which I had tried in the past, with no success), but this time, after ensuring all the tcp/ip protocols were enabled and the 32-bit aliases was disabled, I was able to connect the 32-bit to the 64-bit SQL server, using the xxx.xxx.xxx.xxx address of the server.
Test came back successful!
I had built an application to connect to MySQL DB and SyBase - SQL Anywhere DB using VB.NET and appropriate ODBC connections. This was working fine until we had to make this application a service which keeps running in the background irrespective of any users logged in.
I built the application into a service and after installation, the service was able to successfully connect to MySQL DB, but I am getting the following error when connecting to SyBase (please note the connection string is exactly same as used in the application)
ERROR [08001] [Sybase][ODBC Driver][SQL Anywhere]Database server not found
The project installer - service process installer 1 is configured as localsystem.
The creepiest thing here is, mysql connection is successful, when the same application was not a service, connecting to sybase was successful. Once it was made into a service it started failing. I have a Windows 7 64-bit workstation and VS 2010.
I have been trying to do every single thing for the last one week to fix it but nothing seems to be working. Any advice would be highly appreciated.
Looks like you are using a DSN to connect to SQL Anywhere.
First, make sure that you have configured it as a System DSN. Then, verify that you are using a TCP/IP connection protocol (ODBC Admin -> Select System DSN tab -> Select DSN in list -> Click Configure -> Goto Network tab) and NOT Shared Memory.
Using Shared Memory will NOT work from a Win Service that tries to connect to a SQL Anywhere DB Server.
I suspect that is the issue since you are able to connect from a desktop app using the same connection string.
One way to make this work is to start your SQL Anywhere db as a network server (Start -> All Programs -> Sql Anywhere 12 (or 11, depending on your setup) -> SQL Anywhere -> Network Server.
That should run the dbsvr12.exe, which will start listening for connections on a TCP port.
Then, add a Links=tcpip, or a Host=localhost to your Win Service connection string and give that a try!
Take notice that simple win app is running with credentials from logged user, while windows service is running on system account (in your case). You have two options, change connection string to connect with specific user (if you are now using trusted connection) or change windows service logon user to your user.
I have a Delphi application running on SQL Server 2000, but it's taking awfully long to connect to the database!
But when I run this application on my development server it connects pretty fast!
I am running on Windows 2003 server, SQL Server 2k personal edition, when I look on my MDAC version in the registry, I see version 2.8 already installed!
Any ideas why this happens on the production machine but not on the development machine?
There's a reasonable chance that this is down to a network level issue connecting to the database. Depending on whether you're running the application and database on the same box of course.
Try connecting to the database from the same machine using a different tool. You could set up a data source and test it from the control panel as an alternative. If the connection is slow from another tool test the connectivity between the servers for other types of connection (e.g. run a ping). It may be that it's resolving the server via broadcast rather than the domain, for instance. Or any number of other issues - firewall, switch, wins etc.
If you are connecting using integrated authentication also ensure that the database can resolve the application server as well as vice versa. This is part of the authentication process and I've seen it cause slow downs in creating database connections before.
In short, I'd be confident that this isn't a problem specific to delphi / sql, but something in the communications between your production servers.
Good luck!
Keep your connection open once you have established it. This is called connection pooling and will improve performance. I have no clue how to do it with a delphi application.
Your problem most likely is network or transport layer related
Are you connecting through TCP, Named Pipes or another mechanism?
Have you tried tracing opening a connection with Microsoft SQL Profiler?
regards,
Lieven
I had a problem a long time ago like this, and it came down to the workstation section of the connection string. its possible if you've copied the connection string from your dev machine that the workstation parameter is still in the connection string and pointing to your dev machine which probably does not exist on your deployment network.
In this case your connection to the database has to wait until the network tries to connect ot a non-existant machine (which obviously takes time). Remove the workstation cluse and it will speed up no end.