Problem in WinRunner application
Hi,
I am packaging WinRunner application version is 9.2. It is a demo version. If we install this application in the
specific environment it will take the license from the server and shortcut will launch work fine. But here it will show,
application will expire in 14 days. Source is showing this message both in Admin and Stadard user mode.
This is a legacy setup and I created MSI for this. I installed the application and checked in the standard user mode,
but it is showing as application as expired. But in Admin mode it is showing as application will expire in 14 days.
I have checked with the filemon and regmon and I have given modify permission to the folders & full control to the registries for the ACCESS DENIED. Still it is showing application is expired in the standard user mode.
Please give me the solution for this.
Regards
Sanjeev.V
I am packaging WinRunner application version is 9.2. It is a demo version. If we install this application in the
specific environment it will take the license from the server and shortcut will launch work fine. But here it will show,
application will expire in 14 days. Source is showing this message both in Admin and Stadard user mode.
This is a legacy setup and I created MSI for this. I installed the application and checked in the standard user mode,
but it is showing as application as expired. But in Admin mode it is showing as application will expire in 14 days.
I have checked with the filemon and regmon and I have given modify permission to the folders & full control to the registries for the ACCESS DENIED. Still it is showing application is expired in the standard user mode.
Please give me the solution for this.
Regards
Sanjeev.V
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
aogilmor
13 years ago
first, don't package the demo version.
second, if you insist on packging it what you may have to do is make the additional registry or file permission changes (keep regmon/filemon/procmon running when you launch as regular user), save the output, make the additional perm changes to your MSI/MST, retest as regular user.
wash, rinse, repeat until no more errors. I've had to do this half a dozen times or more for some apps because they don't create the required reg/files until the app is started?
Are you sure you wanna do this for a demo version? [:D]
second, if you insist on packging it what you may have to do is make the additional registry or file permission changes (keep regmon/filemon/procmon running when you launch as regular user), save the output, make the additional perm changes to your MSI/MST, retest as regular user.
wash, rinse, repeat until no more errors. I've had to do this half a dozen times or more for some apps because they don't create the required reg/files until the app is started?
Are you sure you wanna do this for a demo version? [:D]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
