Boards /
Deployment /
Topic 818
No more "Opendcl" command after updating the runtime
Started by copter ·
2009-06-16 15:11 UTC ·
11 replies · SMF topic #818
copter
2009-06-16 15:11 UTC
Hello
Each time I upgrade the runtime, The command "Opendcl" no more works. ("Unknown command")
I have to un-install the run time, and the editor, re-install again in order to get again this command.
Today I installed 5.1.1.4 -> 5.1.1.6: Same thing. No more "Opendcl" command (Vista+ A2009 + A2010)
So my questions are:
How can I check, (in the registery ?) if the tis command is correctly implemented.
Is there any conflict between the run time and the editor ?
Have I to un-install first each time I make an update of the run time ?
Thanks
Copter
bazzacad
2009-06-16 16:32 UTC
author=copter link=topic=818.msg4020#msg4020 date=1245165104 wrote:
I have to un-install the run time, and the editor, re-install again in order to get again this command.
You don't need to install the runtime & the Studio\Editor. That's casing your problems.
Uninstall everything, then
ONLY install the Studio.
The Studio install includes the runtime.
copter
2009-06-16 16:41 UTC
Hello
Today, I installed only the run time. I did not installed the Studio. Am I wrong ?
Run time: 5.1.1.6
Studio: 5.1.1.4
Copter
owenwengerd
2009-06-16 16:41 UTC
Even though Studio includes the runtime, it should not cause any problems if they are both installed. Can you give me some step by step instructions for reproducing the problem, starting with a clean machine?
bazzacad
2009-06-16 16:45 UTC
Seams like these maybe related.
{2}
@copter I wouldn't have different versions of the Studio & the Runtime installed on my PC at the same time...
copter
2009-06-16 18:10 UTC
To Owen
On a clean machine (Run time and studio un-installed)
- Install OpenDCL.Studio.ENU.5.1.1.2.msi
- Install OpenDCL.Runtime.5.1.1.6.msi
- Install OpenDCL.Studio.ENU.5.1.1.6.msi
-> No more "Opendcl" command.
To BazzaCad:
I will do not install both studio and run times. I promess.
copter
2009-06-16 18:20 UTC
An other test:
On a clean machine (Run time and studio un-installed)
- Install OpenDCL.Studio.ENU.5.1.1.2.msi
- Install OpenDCL.Studio.ENU.5.1.1.6.msi
No more Opendcl command !
In this case there was not any runtime installed.
Copter
copter
2009-06-16 18:32 UTC
An other test: (The last one)
On a clean machine (Run time and studio un-installed)
- Install OpenDCL.Runtime.5.1.1.1.msi -> Works
- Install OpenDCL.Studio.ENU.5.1.1.6.msi -> No more works
- Install OpenDCL.Studio.ENU.5.1.1.6.msi again -> Works !!!!!!!!!!!!
Is this a VISTA joke ? I am pretty sure that there is not any trouble on XP ...
Copter
owenwengerd
2009-06-17 02:56 UTC
The upgrade install has to uninstall the previous version, and somehow the previous verion is being uninstalled *after* the new version is installed. I am investigating.
owenwengerd
2009-06-18 03:36 UTC
This problem should now be resolved for Beta 7. Note that the fix will not take effect until Beta 7 is upgraded. In other words, upgrading to Beta 7 will still execute the faulty uninstall code from Beta 6 and result in missing demand load entries -- but upgrading from Beta 7 to Beta 8 should work correctly.
copter
2009-06-18 13:21 UTC
Thanks Owen
In conclusion, for already deployed run times I should do: (In Inno Setup for example):
Filename: msiexec.exe; Parameters: "/x ""{tmp}\OpenDCL.Runtime.5.1.1.2.msi"" /qn"
Filename: msiexec.exe; Parameters: "/i ""{tmp}\OpenDCL.Runtime.5.1.1.7.msi"" /qn"
Am I right ?
owenwengerd
2009-06-18 14:35 UTC
Yes, you are correct.