Hi folks
I have upgraded to 2022 R2 and am testing deployment of our appliications using the latest runtime in IDE AND in the projects.
Windows 10/64bit & 32 bit IDE/project
I try to connect to MS SQL Server (2014)
using the following transaction object parameters
it_systransobj:
autocommit = true
database ="dbname"
dbms="ADO.Net"
dbparm="Provider='SQL Server',TrimSpaces=1,CommandTimeOut=60, DataSource='servername,1433',Database='dbname'"
dbpass="password"
lock=""
logid="username"
logpass="password"
servername="servername"
userid="username"
This works fine in the IDE, but not in deployment.
when the deployed application executes :
messagebox("connect server", it_systransobj.dbparm)
connect using it_systransobj;
messagebox("connected to server","result")
then it shows the dbparm parameter , and on pressing OK it simply silently halts, never reaching the final messagebox, and it is not possible to pull any errormessage from that transaction object.
I have carefully collected all the listed runtime components supplied in the documentation for R2 and put them in our conventional runtimefolder on the clientside (included in the client's path). No change from previous versions here, just replaced the old sybase.xxx.xxx.xxx components. Every other runtime component is also updated to build R2 2819, of course.
Also, I have installed .NET Desktop Runtime 6.x on the test client machine and rebooted.
This looks like something is missing on the deployed client side, since it works in the IDE.
Any others with similar experiences? And solutions :)
Ijwhost.dll //add
pbDBDriver.dll
Appeon.DB.Proxy.dll
Appeon.DB.Proxy.runtimeconfig.json
Appeon.DB.Proxy.deps.json
Appeon.DB.Base.dll
Appeon.DB.Base.deps.json
Appeon.DB.SQLServer.dll
Appeon.DB.SQLServer.deps.json
Microsoft.Data.SqlClient.dll
Microsoft.Data.SqlClient.SNI.dll
Microsoft.Identity.Client.dll
Microsoft.SqlServer.Server.dll
System.Configuration.ConfigurationManager.dll
System.Security.Permissions.dll
Azure.Core.dll
Azure.Identity.dll
Microsoft.Bcl.AsyncInterfaces.dll
Microsoft.Identity.Client.Extensions.Msal.dll
Microsoft.IdentityModel.Abstractions.dll
Microsoft.IdentityModel.JsonWebTokens.dll
Microsoft.IdentityModel.Logging.dll
Microsoft.IdentityModel.Protocols.dll
Microsoft.IdentityModel.Protocols.OpenIdConnect.dll
Microsoft.IdentityModel.Tokens.dll
Microsoft.Win32.SystemEvents.dll
System.Drawing.Common.dll
System.IdentityModel.Tokens.Jwt.dll
System.Memory.Data.dll
System.Runtime.Caching.dll
System.Security.Cryptography.ProtectedData.dll
System.Windows.Extensions.dll
The exe file and several other resources are placed on a file server and the runtime files( dlls and others) in a folder on the client, available to the client users Windows Path. This is a structure that we have had for twenty years now.
We have also tried putting the DB-related dll components on the file server, together with the exe file. No change.