My app used to connect just fine via .NET api to SQLAny version 2044, using srvPath Program FilesSQLAny11dbsrv11.exe and argStr -x tcpip -n BCFSHH29668 -c 20M "Storage CardSybasetrailer.db" and ConnectionString Data Source=SQLAnywhere 11 trailer; uid=dba;pwd=sql and commandLine -q -c eng=BCFSHH29668;dbn=trailer;uid=dba;pwd=sql -ot dbsync1.txt
Now I get following SAException with message "DB Failure, Ex: Cannot read .ini file."
at iAnywhere.Data.SQLAnywhere.SAInternalConnection.CheckException(Int32 idEx, Boolean freeConn) at iAnywhere.Data.SQLAnywhere.SAInternalConnection.OpenConnection() at iAnywhere.Data.SQLAnywhere.SAInternalConnection..ctor(SAConnection parent, Boolean pooled, Object dtcTran, String connectionString, SAConnectionGroup connectionGroup) at iAnywhere.Data.SQLAnywhere.SAConnectionPool..ctor(String connectionString, Hashtable connectionOption) at iAnywhere.Data.SQLAnywhere.SAConnectionPoolManager.AllocateConnection(SAConnection parent, Object dtcTran, String connectionString, Hashtable connectionOptions) at iAnywhere.Data.SQLAnywhere.SAConnection.Open() at TrailerMovement.Common.DatabaseManager.OpenDBConnection() at TrailerMovement.MainAppScreen.MainAppScreen_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form._SetVisibleNotify(Boolean fVis) at System.Windows.Forms.Control.set_Visible(Boolean value) at System.Windows.Forms.Application.Run(Form fm) at TrailerMovement.Program.Main()
I didn't change anything that I know of, and on some devices this saex is being thrown intermittently, depending on whne the debug version has been deployed to the device. I have compared/verified registry entries for Comm and Software. Is this permissions based? ConnectionPool? version of iAnywhere.Data.SQLAnywhere.dll?
Is there anybody out there?
The biggest mystery about this is the message "Cannot read .ini file". What .ini file is being referred to? There is no such file, nor has there ever been for this ap, and it used to run just fine. Now blocked. I have searcehd Sybase online documentation for ref to this .ini file or any similar cases, there's nothing. The iAnywhere help doesn't mention any cases like this either. It just feels wrong, like there must be some explanation why this exception is suddenly appearing. Any insight or advice would be appreciated! Thanks.
answered 28 Nov '11, 13:01
Which "debug" version are you referring to here?
I believe this is a result of CR #667441 and a temporary inability to access the DSN definition. The error message is not consistent with the actual error condition.
Have you tried a later EBF version to see if the behaviour is resolved? (See: Windows x86/x64 220.127.116.1113 EBF)
answered 28 Nov '11, 13:51