When I try to upgrade from any version of OI to any other version I get the message:

"The installation of OpenInsight in the specified directory cannot be upgraded using this license."

This is an ongoing problem - we have 3 full developer licences - a fully paid up works membership.

What is the solution?

Bob Watson

John,

Haven't got a solution. Just know that others have had the same (?) problem. Search the site for the phrase "can not be upgraded using this license". (Be certain you spell it "can not" and not "cannot".)

- Oystein -

Bob,

Just a thought - the path is standard 8 character\no name space, no write protect, full rights?

Its not been unknown for there to be a fault in the engine - I'm sure that David Goddard (Revelation Software Australia [email protected]) would be able to help you. He must be just along the road?

Further thought - what client O/S? I ask because I vaguely recall some issue of upgrade not working from NT client O/S for some versions of OI - had to use Win98 etc to effect the upgrade. I may be wrong of cause….

Richard Bright

John,

I usually see this when the version number gets scrambled in a previous upgrade. If you send me a copy of your Oengine and tell me what version you are currently at, I will restamp your engine to that version, and then you should have no trouble upgrading.

Send it to [email protected], and I'll get it back to you shortly.

Kevin

Kevin,

Any thoughts on the upgrade issue that I have discussed with you earlier. That is, having a mixed enviornment – runtime and development. As you know, we're doing this to satisfy licensing requirments and give our clients the capability to easily fix problems, etc. I posted a message here, but haven't heard from RTI.

I'm hoping that RTI can modify it upgrade process to address this scenario. Otherwise, if we deploy our OI app in this manner, it will be pain to do any upgrade at our client sites.

Thanks,

Ray

[email protected] onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Ray-

Given:

You have the dlls (but no exes) in a root directory, and a runtime and development directory under the root containing the appropriate exe files.

Then:

Copy your dev exes up into the root.

Perform Upgrade

Copy exes into dev directory

Switch engine in root from Dev to Runtime

Upgrade runtime engine

Copy exes into runtime directory

Hope it helps-

Mike Ruane

Mike,

Question 1:

Well we know that and that's what we're doing now. However, my question is: Can't we (RTI) make the OI upgrade process more automatic to take into account this mix environment. We don't want to have to do go thru all this manual copying process for each client site. It's prone to error and time-consumming.

Question 2:

For my edification, your instructions were to copy only the exe files. Don't we have to also copy the DLLs or are they immune from change?

Thanks,

Ray

[email protected] onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Richard

Appreciate the help

The path is not the problem, nor is the OS - i've tried it on NT and 98.

I've tried the David idea as well!

Bob Watson

View this thread on the Works forum...