I've got a minidump from Windows Phone crash report. It contains a managed exception. I can open the minidump in VS2013, but when trying to debug as managed, I get the following:
Unable to managed debug this minidump. The matching version of
System.Runtime.dll could not be found on the Microsoft symbol server
or on the symbol search path. Make sure the computer has internet
access so the dll can be downloaded from Microsoft.
Additionally, in Output window, there's the following:
SYMSRV: e:\symbols\System.Runtime.dll\536B47F4a000\System.Runtime.dll not found
SYMSRV: http://msdl.microsoft.com/download/symbols/System.Runtime.dll/536B47F4a000/System.Runtime.dll not found
http://msdl.microsoft.com/download/symbols: Symbols not found on symbol server.
I have Microsoft Symbol Server enabled. There's a copy of System.Runtime.dll under C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\WindowsPhone\v8.1
Any ideas, please? Is there an alternative symbol server with WP8 symbols? I've tried excluding System.Runtime.dll from the list of modules to load symbols for; doesn't help.
EDIT: The bug report is here. If you're suffering from the same, please go there and place a "I can [reproduce] too".
Related
I am working with SDL2 and its add-on libraries SDL2_image and SDL2_ttf, using Visual Studio 2017. The libraries, and the .dll files that come with them, are in another folder (C:\SDL2.0\lib\x86), which is in the system path.
When I run, it fails, with this error message:
The procedure entry point InterlockedCompareExchange#12 could not be located in the dynamic link library C:\SDL2.0\lib\x86\SDL2.ttf.dll.
I can fix this by putting libfreetype-6.dll, which comes with SDL2_ttf, in the same folder as the .vcxproj file; or in the Debug folder. I can also fix it by putting the .dll into c:\windows\SysWOW64. But I want to distribute my code, and I don't want to put that file in each folder or require users to have admin access (to access c:\windows\SysWOW64); I want Windows to find it in the PATH, as it does with the other .dll files it's using here.
A few things I tried as I looked around the web for solution (to no effect):
Recompiling libfreetype-6.dll
Downloading the latest versions of all associated libraries
Rearranging the .lib files in Project Properties, Linker, Input, Additional Dependencies. Admittedly I may not have tried all possible arrangements as there are several dependencies
regsvr32 libfreetype-6.dll. This led to a different error message:
The module "libfreetype-6.dll" may not be compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe.
I saw here that maybe I should use the version of regsvr32 in the system32 folder; when I do that, I get
The module "libfreetype-6.dll" was loaded but the entry-point DllRegisterServer was not found. Make sure that "libfreetype-6.dll" is a valid DLL or OCX file and then try again.
So: is there a way to get the program to find libfreetype-6.dll in another folder in the PATH, and eliminate the error message about the procedure entry point?
The program I'm testing on now is from the TrueType tutorial from the LazyFoo website (source).
I'm struggling to find any meaningful information on this issue so any thoughts would be greatly appreciated.
I have a SSIS 2016 package that has a Visual Basic Script Component that requires connectivity to a remote Informix database via an ADO.Net connection. The necessary project reference to the IBM.Data.Informix.dll has been added and the project builds without error. However when the package executes a runtime failure occurs:
"Could not load file or assembly 'IBM.Data.Informix.4.0.410.02, Version=4.0.410.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208' or one of its dependencies. The system cannot find the file specified.":"IBM.Data.Informix.4.0.410.02, Version=4.0.410.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208"
I have tried some of the suggested solutions I have come across including setting the reference property, "Copy Local = False" as well as repointing the reference to the various versions of the installed dll. File locations include the GAC, "C:\Program Files\IBM Informix Client SDK\bin..." and "C:\Program Files (x86)\IBM Informix Client SDK\bin...". Both 32 and 64 bit versions are installed and the dll files do exist in the referenced locations. All attempted solutions failed.
Any suggestions where I can go to from here?
Thanks in anticipation.
After upgrading to Windows 10, I got a lot of errors relating to a broken ADODB reference in my VB .NET application. I performed the steps described in the answer from this topic and that seemed to fix the broken reference errors. That solution actually got the application working for some of my colleagues on their Windows 10 systems. Unfortunately, anywhere in the application where I'm using a Recordset, I'm still getting this error:
"Reference required to assembly 'ADODB, Version=2.5.0.0, Culture=neutral, PublicKeyToken=null' containing the type 'ADODB.Recordset'. Add one to your project."
When I investigated some more, I found that the reference's location was "C:\Program Files (x86)\Common Files\System\ado\msado25.tlb". With this path, I tried to register msado25.tlb type library using Tlbimp.exe but it didn't seem to help any.
I have a feeling that I'm missing something stupid but I have no idea what it is. Any help would be greatly appreciated. Thank you.
Here are some additional related screenshots that may help:
ADODB Reference Properties
Registry
I had this issue after the Windows 10 Anniversary update and I solved it by using tlbimp.exe. tlbimp generates a new adodb.dll and you can reference this in your project.
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\tlbimp.exe" "C:\Program Files (x86)\Common Files\System\ado\msado21.tlb"
The Type Library Importer converts the type definitions found within a COM type library into equivalent definitions in a common language runtime assembly.
I was using my command line on my Windows 8 pc, after I typed the ls command, then I got the following error:
ls.exe-System Error
The program can't start because cygintl-2.dll is missing from your computer. Try reinstalling the program to fix this problem.
Actually, I have googled it and watched some vids, I have tried download a cygintl-2.dll zip file, then extracted the dll file then copy it to the system32 folder. However, it still display the error. I also tried to reinstall the Microsoft Visual C++ Redistributable. it was failed also. I have no idea where I can find any help about this. Hope anyone can help me. Many Thanks!!!
It is because of the lack of cygintl-2.dll&cygintl-1.dll in OpenSSH/bin.
try finding and downloading the two dlls then copy them into OpenSSH/bin (usually it is installed in /program files/openssh/bin, or you can check the environment path to find the installation path)
I installed a newer version of OpenSSH and it fixed the problem thankfully. I was getting pretty worried! Specifically, I followed these two links (https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/lsexe-system-error-how-to-browse-directories/2dddf4a5-5958-4768-acd7-ab4cf816f57e?auth=1 and https://sourceforge.net/p/sshwindows/bugs/2/) and then installed the executable from this site: http://sshwindows.webheat.co.uk/
I'm struggling to get a simple COM Server running in Visual D 2010. These are the steps I did so far:
Clean Visual D 2010 solution of type Dynamic Library (DLL)
I've copied contents of dserver.d into dllmain.d
I've copied file chello.d and dserver.def into the solution's source folder, as well as advapi32.lib and ole32.lib from the <D install dir>\dmd2\windows\lib.
I've added the copied file into the solution by right-clicking the project in the solution explorer and Add->Existing item...
Renamed file dserver.def into dll.def, overwriting existing project's file.
Applied a patch to the chello.d and dllmain.d (originally dserver.d) as written on this forum thread
Build Debug. No errors.
Calling regsvr32 COMServer.dll returns these four message boxes:
then
then
and finally
I am still unable to access the COM object from VBA. And referencing the DLL directly (by Browse... button and pointing to the COMServer.dll) fails with "Can't add a reference to the specified file."
I took another look at the forums and the problem with the samples seems related to TLS on Windows XP. I posted a (somewhat hacky) solution to it here:
http://forum.dlang.org/thread/mqoxluonyjdtjxauaxnl#forum.dlang.org?page=2
I can't provide you with a working answer. It looks like this was a year ago, I was trying to get an example of using a COM server working. This uses Juno (not 64bit ready), has nothing to do with Visual D, and most importantly I couldn't get to work. The issue I hit was related to registering the server ("side-by-side configuration is incorrect").
My qualifications for COM are all there in the history of Juno (so not much of any). If you're more familiar with COM you may get further, if it doesn't compile for the latest DMD let me know (2.064 isn't out yet anyway).