Hi Guys & Gals
I'm deploying to a brand new windows machine a pb2017r2 exe using ADO.NET.
Dot Net 4.5 is installed
I have run the msi installer generated by the package installer and copied over my exe and I'm getting the following error:
Sybase.PowerBuiIder .Db, Version=17.0.0.0, Culture=neutral, PublicKeyToken=98a699138181d746 was not Found.
It looks as though the Sybase.PowerBuilder... DLLs are not registered in the GAC, gacutil is not on the machine so I cannot check this theory.
Has anyone had this before or any ideas how to move forward?
*UPDATE*
Just tried dropping the exe in the folder with the sybase dll and turned on ado trace and I get:
/*---------------------------------------------------*/
/* 08/06/2018 12:39 */
/*---------------------------------------------------*/
(026B1A78): LOGIN: (33.785 MS / 33.785 MS)
(026B1A78): *** ERROR 999 ***(rc -1) : System.IO.FileNotFoundException: Could not load file or assembly 'Sybase.PowerBuilder.DataSource.Sharing, Version=17.0.0.0, Culture=neutral, PublicKeyToken=98a699138181d746' or one of its dependencies. The system cannot find the file specified.
File name: 'Sybase.PowerBuilder.DataSource.Sharing, Version=17.0.0.0, Culture=neutral, PublicKeyToken=98a699138181d746'
at Sybase.PowerBuilder.Db.Data.DbBlock..ctor()
at Sybase.PowerBuilder.Db.Block.SqlBlock..ctor()
at Sybase.PowerBuilder.Db.DbRoutine.Connect(DbDrivers type, Object[] input, Dbms& dbms, DBVersion& dbVer, String& user)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
(026B1A78): SHUTDOWN DATABASE INTERFACE: (0.000 MS / 33.785 MS)
Regards
David
In my case i had the sybase.powerbuilder.db and dbext.dll's in the path. I moved them to the EXE directory, it then gave the new error that datasource.sharing is missing.
My support guys will have built a release set that works and budled it themselves for deployment to get round the problems.
Hope you get it sorted :)
Cheers
David
just add those 3 dlls to the exe directory (or the gac)