Software Deployment

Why have you packaged it? It's in MSI format already...

If you look up the errors 1401 and 1404 in MSI.CHM (most likely supplied with your authoring tool, or downloaded as part of the Windows Installer SDK) you'll see that 1401 is a registry write error and 1404 a registry delete error. The package is trying to write and delete registry entries and failing. I'll bet they're HKLM entries and your build is set with read-only permissions on those keys.

We had the setup and the files. As such we had to package it.

Yes you are correct. They are HKLM entries. How do I change the permissions for these keys. Please provide your feedback.

Regards,
Nilotpal.

If you just need to set permissions on a few keys (i would say less then 10).
Then you can use the below method.

In Wise, go to Installation Expert | Registry:
Go to the key that needs the permission, in the right window select the key | Details.
You'll see a tab permissions, click Add and set whatever permissions is needed.

If there are many reg.keys that need permissions then use Orca.

~Gizsha

With all due respect, no-one in their right mind uses native Windows Installer tools for permissioning, irrespective of how many files/keys there are. Use SetACL, SubInACL, XCACLS or similar in a Custom Action. Much more flexible and reliable and no worries about whether or not you managed to screw existing permissions.

Thank you all for your feedback.

Regards,
Nilotpal

Hi Nilo,
I am doing the same application.
Dont repackage this application ,since it has vendor msi.
Just Transforms will do.
Now to get the Vendor msi go to CrystalReports-XI R2 with SP1 and SP2_READY\win32\Setup.exe /a ,
Once u run this command all the files will br extracetd to a location which u ll provide.
That extracted msi will work fine.
Also i think u need to have dotnet frame work 2.0 and windows installer 3.1 as a prerequist for this app,just check out this.

I hope this will help u.
Thanks and regards
sumit

ORIGINAL: VBScab

With all due respect, no-one in their right mind uses native Windows Installer tools for permissioning, irrespective of how many files/keys there are. Use SetACL, SubInACL, XCACLS or similar in a Custom Action. Much more flexible and reliable and no worries about whether or not you managed to screw existing permissions.


Wow! That's a way of telling someone that their approach isn't the correct one.
You are not training anyone I hope?

~Gizsha

I figure that, as a 'Senior Member', you can take it. :) Didn't your trainer tell you the same thing? If he did, he didn't make much of an impression. As for the "correct approach", again I refer to your status as 'Senior Member': I'd expect someone in that position to know that LockPermissions has an "avoid at all costs" flag...

ORIGINAL: VBScab

I figure that, as a 'Senior Member', you can take it. :) Didn't your trainer tell you the same thing? If he did, he didn't make much of an impression. As for the "correct approach", again I refer to your status as 'Senior Member': I'd expect someone in that position to know that LockPermissions has an "avoid at all costs" flag...



Well, that's not it. I am wondering what you are trying to accomplish with these statements. I didn't have a trainer, was thrown in the deep, together with some other colleagues. Not that there is anything wrong with that, but the risk is present that one looks and finds the wrong solution.

As far as 'lock permissions' is concerned. I haven't had to use that for..........4 years (had to think about that), before that I/we didn't know better. I didn't package for 1 year and the two companies I worked for in the past 3 years...............believe it or not.........the first one, users are power users and at the current company i work for, they are even local admins (all users of this very very large company). Reg.key permissions or file permissions? Hasn't crossed my mind for a very long time. It did when I read that post and I should've read up on it before posting something that we did 6 years ago.

So........there.......little background of me.

~Gizsha

Thank you.

Regards,
Nilotpal