I am having a very frustrating issue which im not able to resolve.
I have created a database program on windows 7 which i am not able to run on Windows 8. The error i receive is "Error communicating with the OLE server or ActiveX Control".
To test out what is causing it i have erased VBA code and the program has started successfully. To test it out even further I have created an empty database with 1 form and vba code for a simple messagebox (Windows 7) and it has failed me on windows 8 again, same error message.
Any help would be appreciated , because google isn't helping me
EDIT: Computer language is English, Keyboard language English/Lithuanian, Region Lithuania, VBA font Arial(Baltic) tested all these as well but didn't seem to fix my issue
EDIT2: I have identified the problem , it actually is System Locale, Windows 7 computer is using system locale - Lithuania, Windows 8 is using English (US). Does anyone know how to solve this problem? my company has multiple windows 7 and windows 8 computers, changing locale is not an option
One possible problem is the versions of the various DLLs that your VBA code uses.
In the VB editor Go into Tools/References on Windows 8 and see if there any library references that it can't find. Then look at the list below and see if you can select a later version to fix it.
Related
The same day that the monthly Windows 7 Professional upgrade was performed, Delphi 7 refused to run, giving only this message:
Register Delphi
---------------
Borland licence information was found, but it is not valid for Delphi.
You can not run Delphi without this information
Click the Exit button to exit Delphi
No further help was provided as to how to register Delphi, and it cannot be done through this App as it simply provides an exit option.
I am re-installing Delphi 7 as I wait (it is a school academic licence - i.e. free), but I suspect that the licence was somehow damaged by the Windows upgrade (and the site admin for my system has no clue).
Does anyone know how to correct this?
There is a registration program called D7reg.exe in Delphi 7 installation directory (C:\Program Files\Borland\Delphi7\Bin if you used default installation location). You can use this program to change the registration information of your Delphi installation.
If you encounter a problem where registration screen has no text then download this patch from Embarcadero.
https://cc.embarcadero.com/item/28098
I have successfully built an executable with Visual Basic 6 SP6 in Windows 7 XP mode. This executable fails to access registry when run in Windows 7. A build of the very same sources made in Windows 7 works fine under Windows 7. Any ideas what can be the issue?
The error number would know. Why bother posting without the error number. Not real smart. Or maybe you are too stupid to read them.
Your post is a waste of time because you KNOW what the problem is (you are either turning off errors or refusing to look at the dialog with the error number printed in front of you).
We have an old Powerbuilder app running on Server 2000 and need to move it. I am having a problem with moving the Powerbuilder app ver 7.0, to a newer platform - Server 2003.
We basically moved the directory with the app in it and all the Dlls. Then I registered the ones that would allow it. We also had to set up Informix client-side software and verified that it was able to connect to the Database.
The app basically takes 2 parameters then checks for data in a remote database, then generates a return code to be used by another app. The return code we get is unexpected and I have no luck in looking up the number:
-1073741811
The app is run from the command line. When I run the app I get a Windows error that mentions Sybase and msvcr80.dll and a dump, and the return code mentioned above - Here is the error from the manifest text:
Server=watson.microsoft.com
UI LCID=1033
Flags=99088
Brand=WINDOWS
TitleName=Sybase Inc. Product File
DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
RegSubPath=Microsoft\PCHealth\ErrorReporting\DW
ErrorText=This error occurred on 2/14/2013 at 7:56:14 AM.
HeaderText=Sybase Inc. Product File encountered a problem and needed to close.
Stage1URL=/StageOne/cert_lsi_exe/7_0_3_10180/msvcr80_dll/8_0_50727_6195/0001e6d5.htm
Stage2URL=/dw/stagetwo.asp?szAppName=cert_lsi.exe&szAppVer=7.0.3.10180&szModName=msvcr80.dll&szModVer=8.0.50727.6195&offset=0001e6d5
ErrorSig=AppName: cert_lsi.exe AppVer: 7.0.3.10180 ModName: msvcr80.dll ModVer: 8.0.50727.6195 Offset: 0001e6d5
DataFiles=C:\DOCUME~1\smarkley\LOCALS~1\Temp\2\WER1.tmp.dir00\cert_lsi.exe.mdmp|C:\DOCUME~1\smarkley\LOCALS~1\Temp\2\WER1.tmp.dir00\appcompat.txt
Heap=C:\DOCUME~1\smarkley\LOCALS~1\Temp\2\WER1.tmp.dir00\cert_lsi.exe.hdmp
ErrorSubPath=cert_lsi.exe\7.0.3.10180\msvcr80.dll\8.0.50727.6195\0001e6d5
I am surprised by the msvcr80.dll request, because this app was written around 2003 and I didnt think that c compiler was at ver 8 yet. I have used Dependency Walker and see no complaints there. I am probably in DLLHell with this thing, though... does anyone have any ideas what to look for?
Thanks in Advance!
I still have a few PB 7 applications around.
Did you try Application Compatibility?
Navigate to the folder and right click on the executable and choose the Compatibility tab.
I suggest trying
Run this program in compatibility for Windows XP (Service Pack 3)
Privilege Level [x] Run this program as administrator
You may need to use Windows XP (Service Pack 2) or an earlier version of Windows.
I am trying to run an old Clipper application. It runs fine on Win 7 32bit but when I try using the DOSBox 0.74 it crashes with the following error:
Exit to error: CPU_SetSegGeneral: Stack segment zero
Are there some settings I forget to set when running the DOSBox?
I need to be able to run this app in DOSBox as it appears to be only portable solution that would work on any Win 7, being it 32 or 64bit.
If no apparent solution is known for this problem maybe you can tell me what alternatives I have to run a Clipper 5.3 application on a Win 7 64-bit Home edition?
EDIT:
I tried it on Win 7 Home 64 bit with the very same result. What can I do?
I used clipper many years ago, clipper does cause problems because incorrect config.sys configuration, specially the setting "FILES" must be big enough (let´s say 200) for your application, but "original" dosbox does not provide a way to adjust this setting.
Try the patch from http://www.shdon.com/blog/2009/09/05/adjustable-files-setting-in-dosbox
This patch allows to configure FILES adding a new setting on dosbox options file
Steps:
Backup dosbox.exe and replace it with the patched version
Edit the dosbox options file and add FILES=200 to the [DOS] section
Try it and post the results since i don't have clipper 5.3 to test.
Wanting to close this question I will write what was the only solution thanks to which I was able to run that aged application on Win7 64bit.
It was VMLite XP Mode.
I simply followed the steps described in their how to guide and it was up and running then I copied my application into the VMLite XP Mode, and it was running fine.
Finally I created, after some googling, a shortcut to my desktop and now I can easily start the application from my Win7 64bit desktop which then lunches the VMLite XP Mode which starts the application :) or something along this lines anyway, so far, it works great.
This is trouble shooting question.
Our application's development environment is VS2005 C/C++, VB6 based GUI.
we use also componentone for ActiveX control(vsflexgrid8).
application performed well in Windows XP, but in Windows 7, there is some problem in GUI.
rebuilded almost all C/C++ code and VB6 code in Windows 7
our build system is so poor and because I joined this team a month ago, building all codes are a bit hard
But this (maybe) last problem is not related to build, I think.
all other processes and GUI process are start well. but when click some menu in GUI, all user controls become invalid.
error message seems like this:
'-2147417848 (80010108)' occured
runtime error.
Automation error.
Invoked Object disconnected from
client.
above message is not identical to real message since real message is our native language(Korean).
when googling with this message, I'm able to gather some informations.
the most possible case is when using OLE Automation for Microsoft Office Objects.
But our GUI(VB6 developed) does not use Microsoft Office Objects.
And problem-causing page/control's are commonly use componentone modules.
So, if experienced similar problems, please help me.
In Virtual Machine Windows XP mode, there is no problem. But I'm strongly willing to develop in this environment.
Thank you for your help.
'Automation Error' just means that an error was raised from within the ActviveX control, but that the developpers did not add a description to it. So the cause could be anything.
A common source for this kind of errors are write errors to protected folder (The Program Files folder for instance) or forbidden Registry Read/Write actions. You could try installing the program to another location or to run it elevated.
Hope this helps at least a little.
As Dabbler says, this means there has been an error in the ActiveX component.
Does any of your C or C++ code run before this error happens?
Are you using the latest version of the ComponentOne control? Perhaps it's worth checking whether it is supported on Windows 7, and contacting their technical support?
You could debug the VB6 and C/C++ on Windows 7 to track down which bit of code triggers this problem. This is possible with Visual Studio 2005, which you say you have, or WinDbg which is free.
I solved this problem by Windows Updates.
Since about 20~30 updates are performed at once, I can't know what update solves this.
I guess Visual Studio 2005 security updates may the reason for this trouble.
Anyway, my application runs well in my Windows 7 machine.
Thanks to All.