Hi,
I am having a problem with AI not detecting the installed JRE on 64-bit windows 7 (see attached screenshot). A 32-bit build works fine. Both the java exe launcher and the install package do not detect the JRE. I had to remove the JRE prerequisite to get the package to install. If I select the ...
Suggested Articles
Search found 20 matches
- Fri Dec 18, 2009 1:45 am
- Forum: Common Problems
- Topic: JRE not detected on 64 bit windows 7
- Replies: 1
- Views: 6061
- Jump to post
- Wed Oct 28, 2009 1:39 am
- Forum: Common Problems
- Topic: Another instance of setup is already running
- Replies: 8
- Views: 66722
- Jump to post
Another instance of setup is already running
Hi,
One of my users has reported this error "Another instance of setup is already running" however they assure me that there is no other instance of setup running. They have tried rebooting and even redownloading the package but this message is alawys displayed. Any advice on how to get around this ...
One of my users has reported this error "Another instance of setup is already running" however they assure me that there is no other instance of setup running. They have tried rebooting and even redownloading the package but this message is alawys displayed. Any advice on how to get around this ...
- Fri Feb 06, 2009 10:12 am
- Forum: Common Problems
- Topic: failed to get the module path
- Replies: 23
- Views: 26625
- Jump to post
Re: failed to get the module path
Hi Paul,
I think this error message is a bit of a catch all so when the launcher fails this is what you get. I am getting this problem with only some of my Vista installs and I do not have any folders installed into APPDIR. I think my problem is also permissions related but I just havn't been able ...
I think this error message is a bit of a catch all so when the launcher fails this is what you get. I am getting this problem with only some of my Vista installs and I do not have any folders installed into APPDIR. I think my problem is also permissions related but I just havn't been able ...
- Mon Jan 26, 2009 11:58 am
- Forum: Common Problems
- Topic: failed to get the module path
- Replies: 23
- Views: 26625
- Jump to post
Re: failed to get the module path
Thanks cosmin, I have sent you an email with the details you requested.
This user did upgrade from a previous version however it appears that the install package does not work for them. They uninstalled this version and reverted back to the old version and it works fine. I then asked them to try ...
This user did upgrade from a previous version however it appears that the install package does not work for them. They uninstalled this version and reverted back to the old version and it works fine. I then asked them to try ...
- Sat Jan 24, 2009 10:47 am
- Forum: Common Problems
- Topic: failed to get the module path
- Replies: 23
- Views: 26625
- Jump to post
Re: failed to get the module path
Thanks cosmin, but I was hoping for a more technical explanation such that I can try to replicate this problem. eg: the path jvm.dll could not be found or perhaps an entry point is missing. From your description though it appears that this is some sort of catch all error.
I have recently released ...
I have recently released ...
- Fri Jan 23, 2009 4:37 am
- Forum: Common Problems
- Topic: failed to get the module path
- Replies: 23
- Views: 26625
- Jump to post
Re: failed to get the module path
Hi cosmin,
I originally reported this problem and since then I implemented your workaround and released my application. The majority of my users are working fine however there is small minority still getting this error. Can you please supply some more details as to the cause of this useless error ...
I originally reported this problem and since then I implemented your workaround and released my application. The majority of my users are working fine however there is small minority still getting this error. Can you please supply some more details as to the cause of this useless error ...
- Tue Jan 13, 2009 10:12 am
- Forum: Feature Requests
- Topic: Liceense Check Manadates Windows Registry
- Replies: 2
- Views: 4957
- Jump to post
Re: Liceense Check Manadates Windows Registry
Thanks Cosmin,
Spawning the reg executable is exactly what I previously did however it is plagued with problems. Many corporates have policies that prevent registry changes and also the Vista UAC is causing me no end of pain. I have sinced upgraded to use JNI and this has improved things but I ...
Spawning the reg executable is exactly what I previously did however it is plagued with problems. Many corporates have policies that prevent registry changes and also the Vista UAC is causing me no end of pain. I have sinced upgraded to use JNI and this has improved things but I ...
- Mon Jan 12, 2009 4:08 am
- Forum: Feature Requests
- Topic: Liceense Check Manadates Windows Registry
- Replies: 2
- Views: 4957
- Jump to post
Liceense Check Manadates Windows Registry
Hi,
One thing that has always annoyed me about AI is the fact that the license check mandates the use of the windows registry. Java has no API for the windows registry and now with the Vista UAC cracking down on it this has over complicated license checking for our Java app. It would be great if we ...
One thing that has always annoyed me about AI is the fact that the license check mandates the use of the windows registry. Java has no API for the windows registry and now with the Vista UAC cracking down on it this has over complicated license checking for our Java app. It would be great if we ...
- Sat Dec 27, 2008 3:04 am
- Forum: Common Problems
- Topic: failed to get the module path
- Replies: 23
- Views: 26625
- Jump to post
failed to get the module path
Hi,
I am having a problem with a java application built with AI 6.7.1. When I install the compiled package and run the executable I get a "failed to get the module path" error. If I replace the exe built by AI 6.7.1 with one built with a previous version (not sure which one) it works fine. Do I ...
I am having a problem with a java application built with AI 6.7.1. When I install the compiled package and run the executable I get a "failed to get the module path" error. If I replace the exe built by AI 6.7.1 with one built with a previous version (not sure which one) it works fine. Do I ...
- Tue Dec 02, 2008 10:38 pm
- Forum: Feature Requests
- Topic: Why bother with maintenance?
- Replies: 4
- Views: 12783
- Jump to post
Re: Why bother with maintenance?
Thanks cosmin,
I am more referring to major new features suchs as
List Websites and Virtual Directories
Prerequisites Repository
Advanced Licensing
ICE Validation
The minor enhancements you refer to are nice but do not add a lot of value. I have been a AI user now for nearly 2 years ...
I am more referring to major new features suchs as
List Websites and Virtual Directories
Prerequisites Repository
Advanced Licensing
ICE Validation
The minor enhancements you refer to are nice but do not add a lot of value. I have been a AI user now for nearly 2 years ...
- Tue Dec 02, 2008 10:27 am
- Forum: Feature Requests
- Topic: Why bother with maintenance?
- Replies: 4
- Views: 12783
- Jump to post
Why bother with maintenance?
Hi,
I am very annoyed to see that in the latest release of AI 6.7 all of the major new features are for the enterprise edition only. This is true of last couple of releases. When are the rest of us going see some value for our maintenance plans. I will be very reluctant to renew mine.
-Mark
I am very annoyed to see that in the latest release of AI 6.7 all of the major new features are for the enterprise edition only. This is true of last couple of releases. When are the rest of us going see some value for our maintenance plans. I will be very reluctant to renew mine.
-Mark- Mon Sep 01, 2008 3:42 am
- Forum: Common Problems
- Topic: MSVCR71.dll not found
- Replies: 1
- Views: 2868
- Jump to post
MSVCR71.dll not found
Hi,
Some of my users are getting the following message after having installed my application.
This application failed to start because MSVCR71.dll was not found. Re-installing the application may fix this problem.
I did a search and there appears to be some history on this problem however it was ...
Some of my users are getting the following message after having installed my application.
This application failed to start because MSVCR71.dll was not found. Re-installing the application may fix this problem.
I did a search and there appears to be some history on this problem however it was ...
- Thu Jan 17, 2008 2:21 am
- Forum: Common Problems
- Topic: Corrupt Installation
- Replies: 1
- Views: 3187
- Jump to post
Corrupt Installation
Hi,
I have a user who has a corrupt installation and I do not know how to fix it. When they try to uinstall the existing version they get an error that says there is a problem with windows installer package, program required could not be run to contact vendor. . When they try to install it again ...
I have a user who has a corrupt installation and I do not know how to fix it. When they try to uinstall the existing version they get an error that says there is a problem with windows installer package, program required could not be run to contact vendor. . When they try to install it again ...
- Tue Nov 13, 2007 10:13 pm
- Forum: Common Problems
- Topic: Package created with v6 will not upgrade packages created v5
- Replies: 2
- Views: 4471
- Jump to post
- Tue Nov 13, 2007 6:13 am
- Forum: Common Problems
- Topic: Package created with v6 will not upgrade packages created v5
- Replies: 2
- Views: 4471
- Jump to post
Package created with v6 will not upgrade packages created v5
Hi,
I have a major problem in which an install package created with advi6 will not upgrade a product that was created with advi5.
The adv6 created package correctly detects that a previous version is installed and then uninstalls it however it does not correctly install the new version. The ...
I have a major problem in which an install package created with advi6 will not upgrade a product that was created with advi5.
The adv6 created package correctly detects that a previous version is installed and then uninstalls it however it does not correctly install the new version. The ...
FOLLOW US