When I've sequenced the same application, on launching its giving the Activation window but when I'm selecting 30 days evaluation mode and click Finish its not opning the application instead client shutdown.

Comments

Answers

1

I would think that you'd need to be looking where the evaluation mode setting is stored - File or registry, machine or user area.

You could do this on a physical install using your favourite lightweight snapshot tool to catpure the information (InControl/PictureTaker/InstallRite).You could also use ProcMon to see if there are other processes spawned at this point that may not be launching in your sequence.

You could use ProcMon in the bubble too - to examine what is failing in your sequence at that point.

Once you know where it's being stored then look at your sequence to see if the location is marked as user or machine data, if you have security descriptors enabled - are there sufficient rights for the user on the location. You would hope that once you've identified the setting the cause will become obvious :)

Once you know what the setting is - you could incorporate it into your sequence so that the evaluation mode is pre-enabled. You would also need to test whether full activation works correctly if you plan to have users activating a licence at a later date.

It uses Flexnet licensing, and relies on the 'FLEXnet Licensing Service' being present and startable by the application.Check whether you've captured this in your sequence, otherwise you won't be able to get anywhere.There can be issues where you have mutilple licensing services (bubble and non bubble) - there are plenty of posts on the internet about that to help you.

When you launch the app for the first time it checks the service and then creates a file - mine is called 'fotoware_006ef600_tsf.data' in ..\All Users\Application Data\FLEXnet.

If I remove the file it prompts to enter licence or opt for 30 day trial again - if I put it back it asks if you want to continue the trial.

Take a look at these things and see if that points you in the right direction.

1. VFS 2. MNT3. VFS without launching the shortcut4. VFS with copied post config data in the package5. MNT with copied post config data in the package6. Checked the procmon but haven't got any clue in that.

I would also check in your sequenced app, have you set it to give users write access to the files. If the license files listed above by Dunnpy is machine based (not writeable for users) you might get the error you are seeing.

Wouldn't that be part of enforcing the security descriptors for the perms? AFAIK the 'user data'/'machine data' setting is more to do with upgrades. If tagged as 'user data' then an application upgrade doesn't replace the file (unless the override setting is enabled), but if it's 'machine data' then it is replaced as part of an upgrade - whether it was modified at application runtime or not.

May be its very late to reply you, but I got the solution for this , would like to share the same here.This issue is because our app-v package fails to detect\install\start Flexnet license service. So1. Capture the application as it is... to VFS. and make all VFS folders as 'Merge wit local key' in properties page.2. Verify Flexnet license service node is available in virtual registry and also verify 'Macrovision Shared' folder available in programfiles\common files folder.3. Install batch script in OSD tab under dependencies . under script body give the below statementsc create "FLEXnet Licensing Service" displayname= "FLEXnet Licensing Service" type= own start= auto error= ignore obj= "LocalSystem" binpath= "C:\Program Files\Common Files\Macrovision Shared\FLEXnet Publisher\FNPLicensingService.exe"4. Install another script body and give the below statement there:

Sc Start "FLEXnet Licensing Service". Note these two batch scripts are pre-launch events.5. save the package and launch it in client. 6. Application works successfully.