I'm using VBCCR14.dll Activex Common Control in order to support Unicode. In the developed machine it works perfectly but when the program is running from a different machine it gives an error saying that, "Error loading dll". I've also registered the dll in the other machine but still it gives the error. I've also tried to solve this problem, by referring this article.
http://www.vbforums.com/showthread.php?841929-VB6-ActiveX-CommonControls-(Replacement-of-the-MS-common-controls)
But still the error occurs. Could someone help me regarding this issue?
I've tried it with Visual basic 6.0 in Windows 10.
Related
Yesterday, I could work with Visual Studio 2010 without any problem. However, today after I turned on the computer and tried to open my project (Web application with Visual Basic.NET) on VS2010 again, I got a message box showing as below:
Later, I found out after I tried deleting suo file that this message box will show up whenever I open some file in Visual Studio so I tried to run the application. Then, I found another message box popped up as below:
And after I close the message box, I finally got this window
It says:
Compilation Error
Compiler Error Message: The compiler failed with error code -1073741511.
I have searched for the solution through the internet. I have found a few methods that might solve the solution such as scanning for virus, using clean boot. I have also tried repairing and uninstalling VS2010 and .NET framework but none still work. Right now, I have no idea what I should to do make it work again.
Anyway, I realized that there is Windows auto update when I turned off the computer. Not so sure if this related to the problem (I used Window 8.1).
After formatting Drive C to reinstalling everything again, I found out that the reason might be Windows update. I have started from reinstalling Windows 8, all necessary programs (except Visual Studio and SQL Management Studio) and all window updates required for upgrading to Windows 8.1.
When I successfully got to Windows 8.1, I created system restore point and try installing VS2010 and all windows update. The result had caused the same error I posted in this thread.
After that, I restored back to original state and installed VS2010 first. Then installed some of windows updates. This time, I decided to install all updates except the ones that have publish date after 10/11/2015. The result is satisfied. I don't get this error again.
Later, Hans Passant help me find the actual cause of this problem. Please see this link:
Why do I get an error for "__CrtGetFileInformationByHandleEx " when I try to compile
I am working on a project, when I deployed my project to a windows 7 workstation I am prompted with this error message. Any help is very well appreciated.. Thank you
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click QUIT, the application will close prematurely.
An error occured creating the form. See Exception.InnerException for details. The error is: Method not found: 'Void CrystalDecisions.Windows.Forms.CrystalReportViewer.set_SHowCopyButton(Boolean)'.
If you're making a report for a 32-bit machine, you should try using the 32-bit version of the software. There could be some incompatibilities between the two which is a frequent issue when sharing files between 32-bit and 64-bit applications. This isn't to say it's the only possible issue, but it's a decent guess anyway.
You could also make sure that you have all dependencies for CR installed. Things like Visual studios redistributables and VB\C++ redistributables. Also, make sure that all of the dependencies are 32-bit, although my understanding is this occurring on the 32-bit machine anyway.
I've been getting very frustrated by this :
Run-Time error '430' Class does not support Automation or does not support expected interface
I know there are a lot of people with this problem but there is always a Windows 7 in the middle.
I have an old VB6 code I have inherited (gasp) and I installed Visual Studio 6 to recompile this thing on my XP SP3 machine. On this machine it works like a charm.
When I try the app on another XP computer (which is as updated as the compiling machine) I get that darn error. I've really tried the works to get this to disappear but with no success. I know VB6 is outdated and not supported anymore but there has to be something!
Tried on many XP machines and none works. They all get the error. Does Visual Studio install some kind of run-time which is making it work on my computer?
Sorry if I am so verbose. Any help is welcome.
Well, this is awkward. My bad as usual... The application I was running opened ok, but when I clicked on a button I got the '430' error. Turns out it is caused by an OCX which is probably loaded at that point. I put the OCX next to my exe file and now it's working.
I would like to run a .exe file made with visual studio 2003 but I get an error every time I run it on a windows 7 machine, vista machine, and xp machine. The error on Windows 7 and vista says "application has stopped working" and then makes me close the error box.
In windows xp it's a little different error, "the application failed to operate (0xc0000135) Click on OK to terminate the application."
That error code seems to indicate the application failed to initialize correctly.
It is possible that the anticipated .NET version is not present.
As far as I know, VS 2003 by default compiles against the .NET 1.1 library. There is no straightforward way of installing this on a Windows 7 or Vista box. Do you need to compile it against the .NET 1.1 library, or can you load it in VS2005, change the output .net version to 2.0 or higher, and recompile the application?
If you have the source code to the application, try running the application in debug mode and stepping through line by line until you find the exception. If you do not have the source code, possibly try running the application in a couple different compatibility modes. Another option to try is to check the windows event log for anything more specific.
If you want to get really deep into it, you can use SysInternals ProcMon.exe and filter on the failing exe to view the WinAPI calls that are happening during the failure.
Also, a basic search of forums shows that error is usually accompanied with framework issues. Either recompile the application or check out what your required framework is in the VS2003 project settings.
I'm trying to move a classing ASP site to a 64-bit Windows 2008 server. The problem I have right now (there may be others if/when I get past this one) is that the site depends on an old VB6 DLL (32-bit), and I get the notorious "ActiveX component can't create object" error.
I tried taking IIS7 out of the equation by trying to get it to work with a simple VBS script file, and that's giving me the same thing.
The only dependency this DLL has is ADO 2.6, and from what I've read, this isn't supported and isn't needed for Windows 2008, as WDAC is included and has replaced MDAC.
I use the following to register my component:
C:\Windows\SysWOW64\regsvr32.exe "C:\MyVb6Com.dll"
I checked the registry, and everything appears correct there. My VBS file is also simple:
CreateObject("MyVb6Com.Session")
And it throws the error immediately:
ActiveX component can't create object: 'MyVb6Com.Session'
On the IIS end, I've already tried changing the application pool's settings to enable 32-bit applications, and that didn't help either (of course, if I can't get it to work w/ VBS file, this wouldn't make a difference either way).
Any help would be very much appreciated.
Make sure you use the 32-bit WScript to test your VB Script as well. Double-clicking it will use 64-bit - that will help go to diagnosing your issue.
In the app pool driving your IIS7 website, choose Advanced Settings and near the top, set Enable 32-Bit Applications to True.
IIS7 on a 64-bit machine will not use 32-bit DLLs unless this is set.