I'm trying to figure out why the simplest firebreath plugin wont install on a German Windows XP SP3. I'm running Windows XP as a virtual machine.
The event viewer in Windows XP tells me something about the Windows Installer aborting but not why. I'm logged in as the administrator.
The installer works on Windows 7.
For development I use Windows 7, Visual Studio 2010 and some one months old firebreath trunk.
Is this is known problem? What are the typical steps I could use to track down the issue?
Regards,
Christian
If you get an error saying module can't be found it means that you are missing a .dll file needed to make the plugin work. The most common if it works on most computers (or many) but not that one is that your .dll was compiled with a dynamic runtime, in which case you'll have to install the common runtime for whatever version of visual studio you compiled it with.
For example, the runtime distributable for vs2008 is at http://www.microsoft.com/en-us/download/details.aspx?id=29
Dependency Walker might help you to find out which dll is missing.
Related
Using VS 2010 Ultimate on my Windows 7 64-bit machine, I wrote a Windows Forms Application with Visual Basic and then compiled it with "Build" command specifically for x86 platforms ( I have tried assigning both "x86" and "Any CPU" on Active solution platform options in Configuration Manager). I have also made sure that TargetPlatform is set to x86 on Project Properties.
However, when I'm trying to run the .exe or the .msi file on my XP 32-bit machine, I get this message:
"This product is designed for x64 platform but is being installed on Intel. Obtain the correct setup from the manufacturer."
.NET Framework 4 client profile, which is a Prerequisite for my application, is also installed on the XP machine.
Does anyone have a clue for this? How can I fix this?
Thank you for your time.
I'm not sure about 2010, but in VS2008 it is sometimes necessary to go to Project Properties, Compile, Advanced Compile Options, and change the target CPU to from AnyCPU to x86.
Hope someone could help me..
I created a vb6 dll which suppose to use the printer.print method since i want an easier printer functions.. it runs smoothly in same computer using vb.net 2012 , the problem is after publishing it in newly installed OS with prerequisite installed computers
p.s. already tried installing vb6 IDE and tried the actual printer.print without a problem
Be sure your installer properly registers the DLL. Given your Title, this is probably the first culprit. But there will also be some (many?) VB6 runtimes which need to be installed as well. I am not sure if the standard .NET setup maker knows how to determine what they are and newer machines you install on may not already have them.
When you installed the VB6 IDE you probably fixed the runtimes issue for THAT machine, so it probably has to do with the DLL being registerd. For more installs, you may have to create a mini VB6 installer for the project to install the runtimes.
What is the target OS?
I'm trying to install Testacular (using nmp) on a Windows 8 Professional (64 bit) laptop, but it fails when it tries to install socket.io as part of this process. The error I get is
Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual
Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere.
I apparently have .NET framework 3.5 installed (it's checked under the add/remove Windows components bit in Control Panel), although I've not managed to find a vcbuild.exe. I tried installing an old copy of VS2005 but this resulted in a different error about an invalid project (.vcproj) file.
Can anyone suggest how I might get this working? Weirdly it installed fine on my work computer, which is very similar to the one on which it won't install (they're both 64 bit Win 8 Pro).
I ran into the same issue. I fixed this by adding this to environmental variable PATH: C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcpackages so that it can find vc build.
In Visual Studio 2010, the command line tool vcbuild.exe is replaced by msbuild.exe. So, please make sure you have right Visual studio.
My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server 2000 instance on another server.
On Windows 7, the installation works fine, however when you try to open the application, the error is given.
I have looked at the following:
Registering all the dll's and ocx files using regsvr32. Some will not register as they either are registered already or the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this: http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/0653f685-4526-45d9-89f3-8c479a6b4c62
Monitored the opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.
Reviewed the application according to this list and nothing seems to be against these guidelines
I've noticed two items in the knowledge base that relate to this
http://support.microsoft.com/kb/281848 - the comdlg32.ocx bundled with the application is version 6.0.81.69 and the one in the system32 folder on the dev machine (WinXP 32 bit) is 6.1.97.82. However if this was the issue then surely it would not work currently?
http://support.microsoft.com/kb/184898 - I'm not sure how to confirm that this is the issue
Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.
Update: I get the same error in XP Mode. That's a Win XP with SP3 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?
I got the same error but I solved by using regsvr32.exe in C:\Windows\SysWOW64.
Because we use x64 system. So if your machine is also x64, the ocx/dll must registered also with regsvr32 x64 version
The file msrdo20.dll is missing from the installation.
According to the Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7 this file should be distributed with the application.
I'm not sure why it isn't, but my solution is to place the file somewhere on the machine, and register it using regsvr32 in the command line, eg:
regsvr32 c:\windows\system32\msrdo20.dll
In an ideal world you would package this up with the redistributable.
This download fixed my VB6 EXE and Access 2016 (using ACEDAO.DLL) run-time error 429. Took me 2 long days to get it resolved because there are so many causes of 429.
http://www.microsoft.com/en-ca/download/details.aspx?id=13255
QUOTE from link:
"This download will install a set of components that can be used to facilitate transfer of data between 2010 Microsoft Office System files and non-Microsoft Office applications"
You say it works once you install the VB6 IDE so the problem is likely to be that the components you are trying to use depend on the VB6 runtime being installed.
The VB6 runtime isn't installed on Windows by default.
Installing the IDE is one way to get the runtime. For non-developer machines, a "redistributable" installer package from Microsoft should be used instead.
Here is one VB6 runtime installer from Microsoft. I'm not sure if it will be the right version for your components:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7b9ba261-7a9c-43e7-9117-f673077ffb3c
I tried to start developing for Microsoft Surface. For that I first installed Visual Studio 2008. Then I followed this guide:
http://msdn.microsoft.com/en-us/library/ee804897.aspx
However there it says that only Windows Vista is supported. I'm still running Windows XP on my laptop and old PC and I don't want to update if not absolutely necessary. So I wonder if it is really necessary to use Windows Vista or if it is just a recommendation.
I already tried to install it on Windows XP, but every time i start the Surace SDK installer, the following error message appears:
This installation package cannot be
installed by the Windows Installer
service. You must install a Windows
service pack that contains a newer
version of the Windows Installer
service.
So I was wondering if this is the problem because I don't use Windows Vista. And if not, how can I solve this problem?
Yep, probably.
You can try installing the latest version of Windows installer.
http://support.microsoft.com/kb/942288
Windows vista is definitely required. I can't tell you if this is an artificially imposed requirement, or a physical incompatibility, but vista has been a requirement to install the SDK since was first released to Microsoft partners.
surface has a number of hard Vista dependencies. DWM is the most obvious one