Hi, I put together a msi using Admin Studio 8 for the IBM iSeries version 5 software. The msi works great but the uninstall is another story. If I reboot the pc after the uninstall the lsass.exe error message appears and I can’t log into the pc. I searched and found an old thread about this subject on another site. Some one recommended to remove any OS files or registry entries from the package. I’ve tried everything I can think of. Anyone have any ideas? Thanks for your help in advance.

Tony
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Was it a setup capture or snapshot used to create the MSI? that can get some really strange stuff.

Try segregating the files if you can unzip them from the setup and add them manually.
Answered 08/09/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
It was a snapshot. It's driving me crazy. I've been working on this for a couple days now.
Answered 08/09/2007 by: han891
Senior Yellow Belt

Please log in to comment
0
I'm sorry to say but I think the MSI is screwed. start over from scratch. Not sure about Admin Studio 8 but Wise has a snapshot configuration where you can exclude files normally "touched" by normal logon/reboot activity. Run that if you haven't already.

Reboot between snapshots; look very carefully at anything under the hive hklm\system, as normal apps will rarely change those.

good luck, let us know how it goes.
Answered 08/09/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
i suspect you are using wise.

check for a component marked RegistryXXX (where XXX is a numeric value)

simple fix is mark it not to uninstall. in reality you should move HKLM components to a separate component.

generally this component contains dll registration Wise cannot associated to a file. As such it gets removed during uninstall as its not ref counted in anyway.

This is a long standing wise issue often caused through the use of MM's with wise.
Answered 08/09/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
forget that I didnt see the admin studio bit sorry..
Answered 08/09/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
The lsass.exe error is common when repackaging IBM Access products with InstallShield. I resorted to using the well documented silent install options...
Answered 08/09/2007 by: KPrinz
Fourth Degree Green Belt

Please log in to comment
0
Lsass.exe

The error is in

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder]
"ProviderOrder"="Cwbnetnt,RDPNP,LanmanWorkstation,WebClient,hgfs"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]
"ProviderOrder"="Cwbnetnt,RDPNP,LanmanWorkstation,WebClient,hgfs"


Well it`s not an error, but if u try to remove these entrys from the package and then install it will work. Though they are probably usefull. I`m working on a solution round this problem.

Had the same problem. Got lsass.exe error during reboot after uninstall. But when i removed these entrys. Installed and uninstalled. Problem gone.

But as i said the application will probably not work correct with these missing.

Chiun
Answered 11/07/2007 by: Chiun
Yellow Belt

Please log in to comment
0
Those keys list the preference order for network providers. It seems likely that your capture included the whole string, rather than the addition of the iSeries provider, 'Cwbnetnt'.

You need to write a Custom Action to remove JUST the 'Cwbnetnt' bit. Easy to do in VBS, especially as the string is ripe for converting to an array using the Split function. You can then loop through the array and re-write anything which ISN'T 'Cwbnetnt' back to a new string and, when you've completed the loop, write that string back to the registry key. Then repeat for the other key.
Answered 11/07/2007 by: VBScab
Red Belt

Please log in to comment
0
Thanks, i will focus on that:-)

By the way, got a error 1406 error when trying to install /qb.

Workaround here is -
Administrator Options
Install for Profile: Determine by user access
Answered 11/07/2007 by: Chiun
Yellow Belt

Please log in to comment
0
Oops! I ought to have added that, if you use Split, remember to use Trim to remove any white space around the string.
Answered 11/08/2007 by: VBScab
Red Belt

Please log in to comment
0
The Custom Action was waaay to complicated for me. Will have another look at that if the package doesnt work.


Workaround for the registry:
Go to:
Setup Editor:
Tables tab
Then:
Registry
Locate the key you wish to keep.

Two solutions here:
1. Ad a new key under the original (dummy key) and in the name just add +. This makes a new string in registry.

2.(This is the one i went for). I just renamed the name ProviderOrder to +

And now it works install and uninstall

Not sure if this will affect the use of the software.

Warning: This solution is at your own risk!

And please comment in any changes you think wont work! Open for solutions.

Link Dummy key at microsoft:
http://msdn2.microsoft.com/en-us/library/aa371168.aspx
Answered 11/08/2007 by: Chiun
Yellow Belt

Please log in to comment
0
Your post reads as if you have renamed the ProviderOrder key. If you had read the MS article properly, you'd see that the thing to do is avoid the wholesale replacement of the entire value and instead just add the 'Cwbnetnt' string, using the ' [~]' suffix. Thus your registry entry would change from:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
Value:ProviderOrder
Data:Cwbnetnt,RDPNP,LanmanWorkstation,WebClient,hgfs

to:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
Value:ProviderOrder
Data:Cwbnetnt,[~]
Answered 11/08/2007 by: VBScab
Red Belt

Please log in to comment
0
Ahhh actualy i did read that. But didnt understand.

I will try that solution!

Thanks again VBScab for saving the day! :-)

May women throw underwear at you, wherever you walk!
Answered 11/08/2007 by: Chiun
Yellow Belt

Please log in to comment
0
The Custom Action was waaay to complicated for me. I would strongly advise you to learn about scripting/CAs sooner rather than later because, as messy as it is, that route is sometimes the only way to get stuff done.
Answered 11/08/2007 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity