Defaulted to export symbols for cxlib-5-0.dll.
Defaulted to export symbols for clientdoc.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for rptcontrollers.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for sacommlayer.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for dtsagent.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for secSSO.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for cxlibw-5-0.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for etc-1-0-12-6.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for u312frko.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for cslibu-3-0.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for crpe32.dll -ĮRROR: Symbol file could not be found. Defaulted to export symbols for crxf_pdf.dll -ĮRROR: Symbol file could not be found. Please anybody help me what is root cause of the problems.ĮRROR: Symbol file could not be found. I attached the result of analyzing the dump file with Windbg.
my iis system occurred crash dump with event 5011. Having seen Paul Reeves comments, what actually does instclient do to fbclient.dll to make gds32.I'm dying. Could this be influenced by the machine where the GDS32.dll file was created originally? I understand that this is a renamed, modified version of fbclient.dll, could a path get messed up during the creation process for GDS32.dll ? The attached GDS32.dll was created by the binary installer. I have attached a copy of the specific v2.1.5 GDS32.dll if this can help diagnose the issue. Reinstalling the application may fix this problem (14001).Įrror: At least one required implicit or forwarded dependency was not found. This application has failed to start because the application configuration is incorrect. Having now checked it with DependencyWalker, the v2.1.4 version resolves currectly to use the 4053 version of msvcr80.dll but the specific v2.1.5 version of GDS32.DLL fails to resolve properly with the following error.Įrror: The Side-by-Side configuration information for "c:\program files\csy\vector7\GDS32.DLL" contains errors. If we drop in the v2.3 version of GDS32.dll everything works fine with no other changes so it would seem to be an issue with the v2.1.5 GDS32.dll. I am unable to attach the screenshots to this ticket, the text of the three errors are as follows:. where we do have Firebird installed it is running SuperServer with all default options set (not that I think this makes any difference). Usually we put the relevant GDS32.dll into our application folder on all machines and up to v2.3 this all works absolutely fine whether Firebird is installed on the terminal or not. We don't have Firebird installed on all machines, just the ones with databases on. If we drop in the v2.3 version of GDS32.dll everything works fine with no other changes so it would seem to be an issue with the v2.1.5 GDS32.dll itself.ĭescription: Our application requires GDS32.dll. Reference error message: The operation completed successfully. Source SideBySide, EventID: 59, Description: Generate Activation Context failed for c:\progra~1\csy\vector7\gds32.dll.
Reference error message: The referenced assembly is not installed on your system. Source: SideBySide, EventID: 59, Description: Resolve Partial Assembly failed for. Source: SideBySide, EventID: 32, Description: Dependant Assembly could not be found and Last Error was The referenced assembly is not installed on your system. I have attached screenshots of the system errors to this ticket and the text of the three errors are as follows:.
Now, with the latest update v2.6, if we just copy the v2.1.5 GDS32.dll from the Firebird server into our application folder, when we try to launch our application on a terminal without Firebird installed we are getting SideBySide system errors recorded in the Windows event log and our application fails to launch. Where we do have Firebird installed it is running SuperServer with all default options set (not that I think this makes any difference to this issue). Usually we only need to put the relevant GDS32.dll into our application folder on all machines and up to v2.3 this all works absolutely fine whether Firebird is installed on the terminal or not.