Run-time error '372':
Failed to load control 'DataReport' from C: \ WINDOWS \ SysWOW64 \ Msdbrptr.dll. Your version of the C: \ WINDOWS \ SysWOW64 \ Msdbrptr.dll may be outdated. Make sure you are using the version of the control That was provided with your application.
https://www.vbforums.com/attachment.php?attachmentid=167589&d=1555473527
my application work by vb6.
Msdbrptr.dll version 6.0.81.69 year 2018.
can anyone help me ?
Related
Hello I have created a installer package of my project build in Visual Basic 6.0. I have using Advance Installer for making package. every thing works perfectly on other systems but a minor problem in my project i am facing which is very hard for me to resolve is I am getting Run time error 372 when printing report i got this error every time
Run-time error '372':
Failed to load control 'DataReport' from C: \ WINDOWS \ SysWOW64 \
Msdbrptr.dll. Your version of the C: \ WINDOWS \ SysWOW64 \
Msdbrptr.dll may be outdated. Make sure you are using the version of
the control That was provided with your application.
I am using version 6.0.81.69 of msdbrptr.dll
and project is based on VB6 with Data report and MS Access
I don't know how to fix this issue please help me to resolve this issue
I have compiled the mono run-time from source on an Amazon Linux instance. After compiling, the 'lib' and 'bin' directories total 320MB. I would like to get this as small as possible. What (if anything) can I delete from there to save as much space as possible.
First, I would start here:
How to make a smaller Mono install / Small Footprint
For myself:
I do not strip the binaries or 're-link' the assemblies, but I do configure with a bunch of options turned off, of course, with the 4.x version of mono your mileage may vary:
My OS-X/Linux disk usage for the mono dir weighs in at about 174MB with about 60MB of that within the GAC (~~/lib/mono/GAC). If you are not using the GAC to resolve assemblies, which I do not, I am left with about 110MB for the full 4.5 framework. There are lots of items in the framework that I personally never use but I never found it worthwhile to create a delete list for it to try to save another 10-30MB...
FYI:
My 'small' OS-X configure:
./autogen.sh \
--with-tls=posix \
--enable-nls=no \
--with-mcs-docs=no \
--with-profile2=no \
--with-profile4=no \
--with-profile4_5=yes \
--with-moonlight=no \
--host=i386-apple-darwin10 \
--with-glib=embedded \
--prefix=${PlayInstallPath}
My 'small' Linux configure:
./autogen.sh \
--with-mcs-docs=no \
--with-profile2=no \
--with-profile4=no \
--with-profile4_5=yes \
--with-moonlight=no \
--prefix=${PlayInstallPath}
Updates for the comment:
Can I get rid of the 2.0 directory - I will always be targeting 4.5
framework. How do I go about using only the 4.5 directory and get rid
of the GAC? Can I just copy the proper dlls there?
Running without the GAC:
If you look at an app like Xamarin Studio/Mono Develop, it uses MSBuild to resolve the assembly locations and not the GAC. The GAC is not really needed and in the new MS .Net Core model of deployment all the .Net assemblies needed for an app/service/Docker/etc are just copied to the same deployment directory, versioning issues are not an issue as you can roll back directory changes to revert to a prior build or just sym-link to a different directory to change to a new version, etc... if you are doing this for production staging/version, talk to your DevOps to coordinate who/what/when/where...
In Mono, you can use MONO_PATH to skip the GAC and go directly to the lib directory, while this is NOT a best practice, it works in our environment for what we are doing (your milage will vary depending upon app type), but read the following Mono links to understand the pro and cons and how you should be doing it:
http://www.mono-project.com/archived/best_practices/#monopath
And:
http://www.mono-project.com/docs/getting-started/application-deployment/
As far as the net_2_0 directory, I never get one as I turn off that profile via "--with-profile2=no" in the autogen/configure step.
why I get error in VHDL for this? Also, sometimes: cannot do process as a process failed previously?
Many thanks.
Permanent solution 1: on win 10
Find the "installation directory\Xilinx\14.x\ISE_DS\ISE\gnu\MinGW\5.0.0\nt\libexec\gcc\mingw32\3.4.2\collect2.exe" and delete it and re-run the emulator, the problem resolved! !
Just delete this or cut and paste somewhere as else, now re-run the code or test bench it will work.
Please accept the solution if find working
No need to update any minGW
I found answer! Look at ningunos answer and put "fuse" file in: C:\Xilinx\14.x\ISE_DS\ISE\bin\nt
For the process failing part, it seems that Xilinx tool writers may have an issue try restarting them and if needed, your machine as well.
Download latest version of MinGW
Copy all the content from the MinGW folder into Xilinx\14.2\ISE_DS\ISE\gnu\MinGW\5.0.0\nt
Now it should be working.
just run the 64bit variant of ISE
This link worked for me.
Solved windows 10 issue with xilinx.
I tried this solution (as mentioned in link):
"ISE 14.7 64-bit - Turning off SmartHeap:"
1) Navigate to the following ISE install directory: \Xilinx\14.7\ISE_DS\ISE\lib\nt64\
2) Rename the file "libPortability.dll" to "libPortability.dll.orig".
3) Copy the "libPortabilityNOSH.dll" file to the same folder, and rename it to "libPortability.dll".
4) Repeat steps 1-3 in the following folder: \Xilinx\14.7\ISE_DS\common\lib\nt64\
The above steps substitute the original "libPortability.dll" with a "libPortability.dll" file that has SmartHeap disabled, the NOSmartHeap (NOSH) version.
This does not negatively impact the operation of the tools, and should successfully work around the ISE 14.7 crash documented above.
ofcourse the answer belowed is from **
Mr. Purohit Gaurav on dt of 11 jul 2016
**
i tried the same one on windows 8 it works perfect...........
i just cut the collect2.exe and paste it somewhere else
Permanent solution 1: on win 8 Find the "installation directory \ Xilinx \ 14.x \ ISE_DS \ ISE \ gnu \ MinGW \ 5.0.0 \ nt \ libexec \ gcc \ mingw32 \ 3.4.2 \ collect2.exe" and delete it and re-run the emulator, the problem resolved! !
Just delete this or cut and paste somewhere as else, now re-run the code or test bench it will work.
I had a problem with the compiler, but when I installed the compiler, I faced the error "failed to link the design"
The solution that worked for me is to cleanup the project files
On the taskbar click on Project > Cleanup Project Files
I want to install SSH on my PC (windows 7 64bits).
But I have a problem with the installation of libssh2.dll file
I saved in: C: \ Windows \ SysWOW64
and even in C: \ Windows \ System32
and when I execute this command "regsvr32 libssh2.dll" in cmd as administrator I get this error message:
Libssh2.dll "The module" "was loaded, but the DllRegisterServer entry point was not found.
Verify that "libssh2.dll" is a valid DLL or OCX file and try again. "
I downloaded from this site file:
http://windows.php.net/downloads/pecl/releases/ssh2/0.12/
The only good that contains the libssh2.dll is x86 (knowing that I have a 64bits), is what may be causing the problem?
If someone knows a solution, please, share it, it is very important that I find a solution as soon as possible and thank you.
You have to put that libssh2.dll somewhere on the %path% so then the PHP extension can find it. Logic were to put it into your PHP dir (if you use the standard zipball from windows.php.net).
well why have you downloaded a 32 bit file to a 64 bit system
am I missing something here
You can only run a 32bit type if your Apache PHP and MySQL have 32bit running versions or 64 bit in your case. So if you are running a 32bit OS on a 64bit system then this is fine, if you are running 64 bit script on a 64 bit system and are trying to use a 32 bit script which I suspect you are then this is not fine!
I would therefore suggest that if this is the case you may have a mix match of OS Versus Script.
There are a few brave people operating in the 64 bit world and you should only ever use the stable versions of the product and like Apache unless you do you will not get the support you want because you have not utilised a stable version only and Apache will not support 64 bit, hence Apache lounge.
If you are running off localhost or 127.0.0.1, then running a stable 32 bit OS and running the 32 bit stable version is the only way you will get support.
I am trying to build and link OpenSSL on Windows 8 and I've found it really daunting. I should mention that I am aware of following posts
OpenSSL Windows x64 Compilation error
How do you compile OpenSSL for x64?
Building OpenSSL VC++ Static 64bit Libs
but none of them addressed what I do really need to know. Therefore I decided to share my experience with you guys as a new post!
First, I can successfully build and link OpenSSL on a Win32 OS and it perfectly works. I know that Windows 8 comes with WOW64. “WOW64 is an x86 emulator that allows 32-bit Windows-based applications to run seamlessly on 64-bit Windows”, though when I run my app that is built on windows 7 32-bit, I receive an error “The program can’t start because libeay32.dll is missing from your computer…” while “libeay32.dll” is apparently there and not missing.
In order to avoid registry missing stuffs, I tried to build OpenSSL in 32bit mode on Windows 8. The build was successfully done and the app linked correctly with no error. Again when I run the app I received the same error message.
And then I tried to build it in 64bit mode based on the following steps;
set PATH=%PATH%;c:\perl\bin;c:\nasm;
call "c:\visual studio\2012\vc\vcvarsall.bat" x64
perl Configure VC-WIN64A no-shared no-idea
call ms\do_win64a
copy ms\libeay32.def ms\libeay64.def /Y
copy ms\ssleay32.def ms\ssleay64.def /Y
ssed -e s/out32/out64/g ms\ntdll.mak | ssed … > ms\ntdll-64.mak
ssed -e s/out32/out64/g ms\nt.mak | ssed … > ms\nt-64.mak
nmake -f ms\ntdll-64.mak
nmake -f ms\ntdll-64.mak test
nmake -f ms\ntdll-64.mak install
In this case, I received a lot of warnings mostly on “data conversion and possibility of data loss” during build but it was built and while “test” failed “install” generated outputs.
Now when I try to build my solution in Visual Studio using new “libeay64.lib and ssleay64.lib” I receive almost thousands of errors saying “unresolved external symbol”
So if possible please answer following questions;
Why I cannot run my 32bit app on Windows 8 (64bit)?
Why correctly built OpenSSL (32bit mode) on Windows 8, still
encounters same error?
In OpenSSL build (64bit mode), am I making something wrong?
I am using OpenSSL ver 1.0.1e, Visual Studio 2012 and nasm 2.10.07
Thanks
I am partially answering your question:
You can run 32-bit under 64-bit in WOW64.
For OpenSSL under 64-bit, there is a compiler option /WX under visual studio which means treat warnings as an error. Remove that compiler option from the makefile. You will get lots of warnings. But OpenSSL will get compiled.
Since, most of the modules are not compiled and their object file is not generated, that is why you are getting linker error. Please let me know if it solves your problem.