Visual Studio 2010 and discovery of advantage server error - advantage-database-server

I installed VS 2010 on a Windows 7 64 bit machine. When I try and connect to an advantage database through the server explorer using the Advanatage OLEDB driver I get a cannot discover advantage database server error. I can connect to the database using the ARC just fine. I was able to connect in VS 2008 just fine. Any ideas on why I can't connect in VS 2010?

If you are trying to connect with "local server", then be sure that your connection string contains "ServerType=ADS_LOCAL_SERVER;". If using Advantage Database Server (remote server), then this link might have some ideas that help. It discusses various ways to provide the IP address and port number if discovery is failing. For example, you can include the port number in the connection path: \\servername:6262\path\dictionary.add.

Related

Connect to a ODBC DSN installed on a server

I am developing an application in Delphi 10.2.3 which connects to a Firebird database installed on a machine running Windows 2016 Server. The application also connects to QuickBooks Online using a third party ODBC driver. Since this application must be accessed by 12+ users in my company, it will not be cost effective to purchase and install individual ODBC drivers for each user.
The provider of the ODBC driver has a version which can be installed on a server. Is it possible to configure an ODBC DNS connection on the server which I can access from network clients? If not, can anyone suggest a workaround.
Server vs Workstation ODBC driver usually has to do with licensing not connection method. It is always running on the same machine as the software using the connection.
Web application used by many users running on a server connecting through an ODBC driver = server licensed version of the driver.
User loading data into Excel on their computer through an ODBC driver
= client / workstation licensed driver.
Some databases, for example SQL Server, can do a database link through an ODBC driver. This is linking / exposing another database to querying from a host database server. This would allow you to share one server licensed driver. The clients would connect to the host database.
One such driver is DevArt's ODBC Driver for QuickBooks which has a help topic on creating a linked database and testing it in SQL Server Management Studio / SQL Server: Using in Microsoft SQL Server Management Studio (SSMS). Might not be applicable if each user needs to use different credentials for the QuickBooks connection.

Firebird database connection by FireDAC after Windows 10 update

I have some delphi applications with connection to Firebird database by FireDAC technology. It works fine, but after Windows 10 update 1803, cannot connect to database when I call application stored in network path (example: \comp1\share\myapp.exe or Q:\myapp.exe, Q: is mapped server path). Error status is 335544721 with illegal parameter.
The same build of application stored on local path works fine. Can anybody help Me?
I've got the same problem!! The reason is the Firebird version 1.5.x (maybe 2.5 too?). Windows Update 1803 blocks the communication between client and server. The only solution is to migrate to Firebird 3.0.x (or to uninstall the update - not a really good option).
I had the same problem with my delphi application I developed a couple years ago, after an update to windows 10 in one of my machines it suddenly drops the connection to the firebird server (2.50 in superserver mode) installed on a windows 7 host, while my other hosts (win xp, win 2003, win 7 and 8.1) connects normally, when I ping or telnet to the server adresse from win10 (telnet 192.168.1.X 3050) the connection establishes, I have tried everything like enabling Smbv1 and disabling v2 and v3, run it under a VM (win 7) machine inside win10 I was surprised to not being able to connect too, then I realised that it wasn't a network hardware configuration problem, but for unexplained reasons WINDOWS DEFENDER, I just disabled it and then my app was able to connect.
And don't rely on firebird's returned error messages they don't discribe the real issue, and can mislead you.
I forgot to mention that I did enabled some services before disabling win defender, wich were disabled after windows update 1803:
Set both Function Discovery Services to Automatic and Start Them
SSDP Discovery set to automatic.
UPnP Device Host set to automatic.

Connecting to Firebird 3

I have installed Firebird 3.0.1 on a PC and on a VM client. I installed Flamerobin on both to test the connection.
I can connect to localhost on both PC and VM using Flamerobin, so I assume the Firebird server is running on both and Flamerobin is installed on both OK
I can connect to the Firebird server on the VM from the PC and open a database Ok
From the VM I can open a database on the PC, but when I try to retrieve the server version on the PC I get an error ISC_Service_attach failed (Unable to complete network request to host).
I have no idea what the problem is given that I can open a database ok, but cannot access any of the utility services.
I am using fbclient.dll 3.0.1.32591 on both VM and PC
If you can achieve network request to server, you need to check firewall setings on server and set fb default port as inbound acceptable. If you would had same problem after that, than you probably need proper fbclient library, for FB3 on client, VM. Hope this helps.

Cannot connect to TFS from Windows XP

I have a Team Foundation Server 2013 installed on a server on a domain. I can connect to this server from my domain account using VS 2012.
I also have a virtual machine which runs on Windows XP and NOT part of the domain (login as a local user). I have a VB6 project running on this VM and I want to connect to the TFS to share and control my VB6 code but I keep on getting The Request Failed with HTTP status 404: Not found.
I tried creating a local user on the server with the same name as the user I use for VM but it didn't work. I cannot join the VM to the domain as well.
Hope someone has tackled this and shed me some light.

Application Unable To Connect to SQL Server 2008

I've been running an ASP.NET MVC application on my IIS 7.5 localhost (on my Win7 Pro box) server with SQL Server 2005 Developer Edition.
I went to put the application on my production server (IIS 7, SQL Server 2008) and am getting SQL Server connection errors. Here is the error I get when I try to browse site root:
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)
I have triple checked my connection string. My host's connection string was in the format XXX.XX.XX.XX,XXXX. Is it normal to have a comma following the IP Address?
Does anyone have any suggestions for something I may be missing?
Thanks.
Take a look at this resource:
http://www.connectionstrings.com/sql-server-2008
A comma after the IP address indicates the port. It should be 1433 unless you have multiple instances.
First of all, make sure that the Windows Firewall (and any other firewall software) on that machine is configured to allow incoming connections to SQL Server. See here for instructions.
Second, check that the SQL Server Browser service in the database server machine is running. This is not necessary in all the connection scenarios, so you may need to provide more details. For example, are you using default listen ports for your server?

Resources