Cannot load bridge interface functions and error code is 0?
Forum rules
The FAQ is a read-only forum which is in general updated only by employees of Dyalog Ltd. It replaces the FAQ page which existed under http://www.dyalog.com. Rather than rejecting other posts to this forum, such posts will be put in a moderation queue, and moved to a more appropriate forum.
The FAQ is a read-only forum which is in general updated only by employees of Dyalog Ltd. It replaces the FAQ page which existed under http://www.dyalog.com. Rather than rejecting other posts to this forum, such posts will be put in a moderation queue, and moved to a more appropriate forum.
1 post
• Page 1 of 1
Cannot load bridge interface functions and error code is 0?
You try to use a .NET interface class or method but it fails with a value error and this message appears in the Status Window: "Could not load bridge interface functions. (Error 0x00000000: "No error")".
1) Are the bridge DLL and the dyalognet.dll from the same version of Dyalog?
Right click on each and look at Properties->Details.
2) Are you running on a Windows on which you have not installed Dyalog?
Our installer will add the Visual Studio 2005 runtime package to the system. If you haven't installed Dyalog on the computer and those Visual Studio 2005 runtime files aren't there, our .NET interface will not work.
To resolve this, download and install one or both of the following packages from Microsoft.
For Dyalog 32-bit:
Microsoft Visual C++ 2005 Redistributable Package (x86)
http://www.microsoft.com/en-gb/download ... px?id=3387
For Dyalog 64-bit:
Microsoft Visual C++ 2005 Redistributable Package (x64)
http://www.microsoft.com/en-us/download ... x?id=21254
3) The other situation where this could happen is if the Dyalog and Dyalog .NET interface files are on a network drive. In that case, you could try adding this loadFromRemoteSources line to the dyalog.exe.config file:
<?xml version ="1.0"?>
<configuration>
<runtime>
<loadFromRemoteSources enabled="true"/>
</runtime>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0.30319" />
</startup>
</configuration>
4) Another tool to try is Dependency Walker.
https://support.microsoft.com/en-us/kb/256872
http://www.dependencywalker.com/
It can do Profiling while Dyalog is running.
In Dependency Walker, File->Open.
Find the dyalog.exe.
Next, Profile->Start Profiling
Untick any option that says “***May fail on WOW64***”
When Dyalog is up, try the simple date time test:
⎕USING←'System'
dtime←⎕NEW DateTime(2015 1 1)
dtime
Take a look at the resultant log and see if it suggests anything to you.
Please copy the log and email it to Dyalog Support if you have any questions.
[Edited on 6 Oct 2015 to add tip 4 about Dependency Walker]
1) Are the bridge DLL and the dyalognet.dll from the same version of Dyalog?
Right click on each and look at Properties->Details.
2) Are you running on a Windows on which you have not installed Dyalog?
Our installer will add the Visual Studio 2005 runtime package to the system. If you haven't installed Dyalog on the computer and those Visual Studio 2005 runtime files aren't there, our .NET interface will not work.
To resolve this, download and install one or both of the following packages from Microsoft.
For Dyalog 32-bit:
Microsoft Visual C++ 2005 Redistributable Package (x86)
http://www.microsoft.com/en-gb/download ... px?id=3387
For Dyalog 64-bit:
Microsoft Visual C++ 2005 Redistributable Package (x64)
http://www.microsoft.com/en-us/download ... x?id=21254
3) The other situation where this could happen is if the Dyalog and Dyalog .NET interface files are on a network drive. In that case, you could try adding this loadFromRemoteSources line to the dyalog.exe.config file:
<?xml version ="1.0"?>
<configuration>
<runtime>
<loadFromRemoteSources enabled="true"/>
</runtime>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0.30319" />
</startup>
</configuration>
4) Another tool to try is Dependency Walker.
https://support.microsoft.com/en-us/kb/256872
http://www.dependencywalker.com/
It can do Profiling while Dyalog is running.
In Dependency Walker, File->Open.
Find the dyalog.exe.
Next, Profile->Start Profiling
Untick any option that says “***May fail on WOW64***”
When Dyalog is up, try the simple date time test:
⎕USING←'System'
dtime←⎕NEW DateTime(2015 1 1)
dtime
Take a look at the resultant log and see if it suggests anything to you.
Please copy the log and email it to Dyalog Support if you have any questions.
[Edited on 6 Oct 2015 to add tip 4 about Dependency Walker]
- Vince|Dyalog
- Posts: 432
- Joined: Wed Oct 01, 2008 9:39 am
1 post
• Page 1 of 1
Return to Frequently Asked Questions (FAQ)
Who is online
Users browsing this forum: No registered users and 1 guest
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group