Getting error while runnning the build exe on another machine - delphi

I have createtd one application using Delphi 5 and BDE components. I have connected to database through ODBC connection. The application is running smoothly on my machine but its giving error while running the build exe on another machine. I have created the same ODBC connection on another machine also. but its giving error "An error Occurred while attempting to initialize Borland Database Engine". :( Any solution to this error? thanks for help. - Naren

Seems to me, that you haven't installed the BDE on the other machines you are trying to run your program. Without the BDE installed, running your program fails.

Related

Delphi - RPC server unavailable when debugging COM+

I have a COM+ application consisting of a client DLL and many middle-tier DLLs.
The application gets run by using an MSC application file.
When I am in die IDE and run my client DLL, I have the following run parameters to launch, run and debug my client DLL (this works great):
The theory is that I should be able to debug my middle-tier by running the DLL with the following parameters (I get the ProcessID from my COM+ Application in Component Services):
Once it is running, I should then be able to start my client MSC application and that should allow me to attach and debug my middle tier. I have seen this working before.
Running my Client DLL from the IDE or as an MSC application works without issues but when I try to debug my middle-tier, as described above, I get a "The RPC server is unavailable" error.
I am running everything locally so I am not sure what server it is referring too.
I have also made sure the following services are up-and-running:
DCOM Server Process Launcher, Remote Procedure Call (RPC) and RPC Endpoint Mapper
Any idea what else could cause this error or what server it is trying to connect too?
It turns out there were more than 1 version of the DLLs registered on my pc. I inherited the pc from a previous employee and noticed some install files of the application on the C drive (all my stuff is on the E drive). I ran the uninstall procedure on the C drive that also unregistered some DLLs and my RPC problem was resolved.

RAISERROR doesn't return correct error message using DB Express on Windows 10

I am running my application which is developed in Delphi 10.1 berlin Update 2 on windows 10 and it is accessing the Database through network (I am using SQL Server 2016 and it is installed on different machine), when stored procedure raises error using
`raiseerror(msg,16,1)`
application gets following message:
`SQL State: 42000, SQL Error Code: 50000`
but the message doesn't contain error string. If I run same query on SQL Management Studio, I get below error.
SQL State: 42000, SQL Error Code: 50000
MSG
I tried to run the same on windows 7 and windows Server 2012 R2 with same configuration, this time it give desired error message containing error string.
I am using dbexpress for handling queries in the application. (NOTE If I replace the implementation from dbexpress to BDE it is working fine in windows 10).
I tried to copy following .dll files of dbexpress and also dbxdrivers.ini file at the location where .exe is present
Borland.Data.DBXMSSQLDriver.dll
dbxadapter.dll
dbxasa.dll
dbxase.dll
dbxdb2.dll
dbxfb.dll
dbxinf.dll
dbxint.dll
dbxmss.dll
dbxmss9.dll
dbxmys.dll
dbxora.dll
Midas.dll
This looks like machine specific issue. Machines having windows 10 but don't have Delphi 10.1 berlin Update 2 installed, we are using these machines as Client machine where we install the application.
Also we observed these issues on application developed using Delphi XE2. So it doesn't seems to be Delphi Issue.
NOTE: Windows 10 client machines having Delphi and SQL server installed, this issue doesn't occur even with dbExpress.
Can someone please help me with this situation? Do I need copy any specify assembly files along with the package?

DBX error in Delphi XE3, when connecting to a SQL Server database

When I try to connect to a MS SQL Server database using DBX an error pops up saying that the driver is not properly installed, or missing. I tried with ADO driver and it worked like charm, but the thing is that I need DBX driver to work because I want to modify an app that has been developed with DBX technology.
I reinstalled Delphi XE3, and also asked a friend of mine to test it and the error is the same. Does somebody has any ideea on how to solve it ?
The exactly message was this:
Borland.Data.TDBXError: DBX Error: Driver could not be properly
initialized. Client library may be missing, not installed properly,
of the wrong version, or the driver may be missing from the system
path.
I must mention that I tried it on a local instance of MSSQL Server 2012 and on a remote MSSQL Server 2008 instance. My OS win8 x64;
Best regards,
This is most likely caused by the wrong version of the SQL Native Client installed on your system. DBX will only work with V10, while you probably have V11 installed. Try to install the V10 version of the client.

running oracle code on asp.net website causes "driver missing" error

running asp.net mvc website that has code that connects to oracle. Works fine on one machine but on another, I get the following Error:
System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.
Here is the line of code that it breaks on:
OracleCommand command = connection.CreateCommand();
This machine that is failing does have the 10.2 version of the oracle driver installed on the machine. Any suggestions on what could be wrong?
Found the same problem (and possible solutions) on asp.net

Files needed to deploy delphi 2010 dbxpress application

I'm having trouble deploying my delphi application. It uses dbxpress to access mysql 5.1 database. When i run the application from another computer, an error occurs. I've already included the midaslib.dll in my application and copied the dbxmys.dll and libmysql.dll in the same folder as my application.
Hope someone can help.
Can you make a connection with the ping command? Can you make a connection to the database itself? Just with the command prompt. Not with Delphi.
Maybe a firewall is blocking or the remote user is not authorized.

Resources