Fix VB6 component warning when registering in COM+ - com

I'm supporting an old Web Application that has some VB6 components and I've found on certain servers I get the below warnings when I'm installing the components in COM+. I've seen some posts that say you need to run MMC with a -32 parameter but that doesn't seem to make a difference. It says to "check the registry value for the following key." But doesn't say what to check for or what to do. Anybody have any suggestions?
A registry value was changed while installing the following component
into a COM+ Application. If you are experiencing activation problems
with this component then please check the registry value for the
following key.
Component: C:\some path\my.dll
Registry Key: CLSID{some guid}\InProcServer32
Process Name: RunDll32.exe Comsvcs.dll file version: not loaded

This was a long time ago but for similar issues it might be caused because the VB6 components are 32 bits and the OS is 64 bits.
Try registering the component in 32 bits using: C:\windows\syswow64\regsvr32.exe
and also run the 32 bits version of the COM+ app C:\WINDOWS\SysWOW64\mmc comexp.msc /32

Related

microsoft.ace.oledb.12.0 provider is not registered error fixing from code behind

My application is working fine in 32 bit machine but when i rum my application from 64bit machine it is showing error like "microsoft.ace.oledb.12.0 provider is not registered". i searched for the solution and every one suggesting about installing 64 bit compatible OLEDB driver .I would like to know whether it is fixed from code behind.Any valuuble suggestion are appreciated.
Thanks in advance
Subin
My answer might look strange but have you seen this solution 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine solution?
I mean especially first approach.
You can change the target CPU to work on 64bit and 32bit
Go to the startup project of your program.
Open the properties window.
Click the compile tab.
Click advanced compile options.
Change the target CPU options to any CPU.

"Not Enough Memory available" exception while running windows phone 8.1 emulator

"Windows Phone Emulator is unable to verify that the virtual machine is running :
Not Enough memory is available in the system to start an emulator that uses 2048 MB of startup RAM"
I am a beginner to Windows Phone App developement.I was trying to Deploy a Hub App template and while executing the code for the emulator I got the above error message! Please help me out.
Probably its because your machine does not hove enough RAM? acording to this article there are some workarounds.
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To work around this problem in a system that is running many programs that are using lots of memory, try to close those programs and then restart the emulator.
If the emulator still does not start, you can disable the Hyper-V runtime memory monitoring functionality by adding a MemoryReserve registry. To do this, follow these steps:
Start Registry Editor.
Locate the following registry subkey:
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization
Right-click the Virtualization folder, point to New, and then click DWORD Value..
Type MemoryReserve, and then press Enter.
Double-click MemoryReserve, enter 2048 in the Value data box, select the Decimal option, and then click OK.
Close Registry Editor.
In systems that experience this problem and that have fewer than 8 GB of RAM installed, a MemoryReserve value of 2048 (2 GB) is recommended. A value of zero (0) causes this registry setting to be ignored.
Note You must restart the computer for this registry setting to take effect.
If this doesnt help give some more info about your machine haracteristics.
Also you can check this article

No error, but program won't start on WIn 8?

I have written a program in VB.Net and run it for a few years on Vista and Win 7 without issue. It is a requirements management tool front end to an Access or SQLServer backend database.
A few months ago I installed it on Win 8. It is a 64-bit version of my program running on a 64-bit laptop. It installs fine and runs OK initially. However, after a few weeks it stops running. This has happened twice, the last time after 28 days.
When I try to run the program nothing happens - no splash screen, no error message, no entry in the Applications Log in Event Viewer - just nothing happens. The only solution has been to re-install the program and then it starts working again.
I have tried: turning off all malware, firewall and anti-virus programs; running the program as Administrator; running in various compatibility modes. Nothing happens.
I also tried removing the license file from the program directory. When I did that I did get an error message in the Application Log in Event Viewer, so the program is trying to start. But when I returned the license file it still won't start and there is no error message in the log file.
Program was written in VS 2008 under .Net framework 3.5. I don't think this is an issue, since it runs fine for about a month after install. Also, it is not the license file. The license is perpetual, and anyway if it fails the license there is a splash screen that comes up, and that is not happening.
Can anyone suggest where I might look in Win 8 to try and work out what is going on when I try to start the program?
UPDATE: Through using the Reliability Monitor I have just noticed that at 2:30pm on the afternoon of the problem Windows Installer reconfigured my application. I had the app open all afternoon. but when I shut it at around 4:40pm, then tried to open it again, the problem above emerged.
Description
Windows Installer reconfigured the product. Product Name: Capability Architect. Product Version: 1.0.0. Product Language: 1033. Manufacturer: SDG. Reconfiguration success or error status: 0.
The reason for the reconfiguration was:
Detection of product '{221672D4-9B64-4550-8B8A-A13C4BE20780}', feature 'DefaultFeature', component '{4F120286-6AE1-5DFE-65E4-A4495CA3F296}' failed. The resource 'C:\Users\Public\Desktop\SDG\Capbility Architect Template v2.0.accdb' does not exist.
Now, that file is installed by default with the product. However, I had deleted it earlier that day because I never use it and that seems to have triggered the reconfiguration. Is that normal behaviour?? And why should a reconfiguration stop the program from running? And is it possible to see exactly what the reconfiguration actually did?
EXTRA UPDATE: If this is the problem then I can't replicate it :( I tried deleting the folder again but it has not affected program start up at all.
Thanks
Ian

WixUI_Advanced fails ACK for per-user test

I am creating an desktop app MSI that using WixUI_Advanced for dual scope support. However the production MSI causes a warning on Windows App Certification Kit:
WARNING Install to Program Files
* Warning: The install to Program Files test detected the following errors:
* Program xxxx fails due to install location C:\Users\user\AppData\Local\Apps\XXX
I was confused. The ACK being used is the Version 2.2, and the warning message shows the CORRECT behavior of a per-user installer (since install to Program Files requires privilege). But why it shows the warning? Are there any body have the same problem?
UPDATE
It seems like a bug of WixUI_Advanced. According to this article, the redirected folder name for per-user install is %USERPROFILE%\AppData\Local\Programs\XXX rather than %USERPROFILE%\AppData\Local\Apps\XXX.
Even you set the install location to %USERPROFILE%\AppData\Local\Programs\XXX the same warning still shows, the same thing happens for ACK version 3.0 (for Windows 8.1) as well.
Furthermore, when doing an x64 per-user test it also warns for the uninstall registry keys. There is no way to set those keys in other ways.
Microsoft confirmed this warning is ignorable and will not affect the certification result, but they did not say anything about weather it is a bug or not, not saying any plan to fix either.

Simple-OpenNI for Processing fatal errors with the Kinect

I have been using SimpleOpenNI, a wrapper for Processing, all summer now. I use it for the Kinect to make games and demos. Last week, I have been getting a fatal error in my processing window and none of the SimpleOpenNI projects will work. Here is the error:
SimpleOpenNI Version 0.20
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x72e8f955, pid=4596, tid=4624
JRE version: 6.0_24-b07
Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 )
Problematic frame:
C [OpenNI.dll+0xf955]
An error report file with more information is saved as:
C:\Users\mss042\Desktop\processing-1.5.1\hs_err_pid4596.log
If you would like to submit a bug report, please visit:
http://java.sun.com/webapps/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
It appears as if the new OpenNI/NITE/SensorKinect drivers do not work with the SimpleOpenNI wrapper. I have tried it with people using the old drivers and everything still works. Problem is, you cannot download the old drivers off of the websites so I cannot test if it's that or not. You can see everything I've downloaded from the simpleopenni site: http://code.google.com/p/simple-openni/
Any help with this error would be appreciated. Thanks.
Mike
It looks like there's a problem with OpenNI.dll. Make sure that:
You have the dll (It should be in Program Files where you've installed OpenNI)
Make sure you've got the Environment Variables for the Open NI paths and that the paths are correct, otherwise, you might have the .dll file, but the .jnilib wouldn't know where it is.
Had a Kinect Workshop in Uni, and my colleagues using Windows all had issues with the drivers,
so I'm just passing on what they did:
Even though they had 64-bit versions of Windows they used the 32-bit version, and used Brekel OpenNI Kinect Auto Installer - Developer Edition v1.3.2.3.exe(direct link via developkinect.com) after reading this message:
Comment 4 by tijmenva...#gmail.com, Oct 21, 2011 Hey all I have Solved
the unsatisfied link dll error on windows 7 64 bits by installing java
runtime (jre-7u1-windows-i586.exe)and (Brekel OpenNI Kinect Auto
Installer - Developer Edition v1.3.2.3.exe) I uninstalled everything
and than it worked :)
hope this helpes
in Issue#17 on the SimpleOpenNI project issues page.
Another colleague used Synapse and OSC in Processing instead of SimpleOpenNI, but she had loads of errors with the drivers (basically spent a few good hours uninstalling/installing different versions). In her case, uninstalling any previous partial or complete drivers from the machine and deleting any registry entries related to PrimeSense(Sensor, Nite) and OpenNI, then using the installers from the links on the Synapse page, worked for her.
HTH
This is a long shot, but that exact error is also given if the Kinect USB and/or power supply simply becomes unplugged. Thought it was worth mentioning as it is not obvious from the error message itself and it may help someone out if they kicked their power supply and started searching for the above exception :)