Look in the event viewer for the component that is causing it to self-heal. This should be a starting point in identifying what files are causing this. You could find multiple components are an issue. You could also try moving all components to one feature as a quickie fix.
===>
kip
by the way is it possible to terminate a fiber as multimode when the current connector is monomode i.e cut out the mono and terminate a new multimode connector? the current backbone setup is mono mode but due to expansion,the new switches that arrived are mulimode.
===>
kip
Remember that there are different types of conflicts. If a file conflict is red flagged (!), then you have location conflict where 2 or more apps are writing a file to the same location hence will step on each other. A yellow flag (?) on the other hand means that the file exists but in different...
You probably have captured uninstall info in the registry under HKLM\Software\YourSoftware|Uninstall or something like that. To make sure that this is the issue, go to the Add/Remove Programs section of the Installation expert and check the "Do not display in Add/Remove Progs" radio...
Very true. Sounds like you have a dirty MSI. Look through the registry and remove entries that are not related to your app. Coomon instances are printer info, winlogon iinfo, drive mappings, etc. Also make sure that things like environment variables, etc are not being written through here.
===>...
If you are talking about the progress dialog box, then yes, you should be able to change that. Got to the dialogs section of the Setup Editor, look for the appropriate dialog and doubleclick on the label. It should bring up a pop-up whose label is typically -- [ProductName][_WiseDialogSuffix]...
Go to the setup editor and go to the dialogs tab. You should find that the ErrorDialog box is checked. Look and see whether all the associated icons/bitmaps exist for the dialog. Simplest thing would be to exclude from the package -- if the Install fails, the Windows installer will still pop up...
On top of what mmv said... Make sure that it is an advertised shortcut. On the other hand, you can create a wisescript that does nothing but is an entry point into the app, and just make sure that it is called everytime. I would also suggest making sure that you put all the components of the...
I think that this is more of an OS specific problem than a Wise issue as IE or whatever browser you are using is set to auto ask that question. You may want to use group policy to change that setting -- should be reg key somewhere so that it auto opens apps rather than prompting the user. Word...
I would also check the components table in the tables tab of setup editor. See if any of your component's attributes are set to 1, and if so, try changing them to 0 or 2, or 4 for HKCU entries. 1 tells it to install the component from the source while 0 specifically installs local, while 2...
Technically W2K through AD and group policy can also handle enterprise level deployment with inventory features (not just a small group) Cheers!
===>
kip
You can download it from http://www.microsoft.com/ntworkstation/downloads/Recommended/Featured/NTZAK.asp
==>However, if you are running 2000, Microsoft recommends the below from...
Group Policy will not run on machines that were recently added to OU (from 6 weeks ago to present)after installation. It's like Kerberos forgets them completely. When gpresult is run, I get a cannot authenticat error on them. I have checked time on the machines and it all looks good. One day I...
This is from Wise knowlegebase ==>
The Windows Installer enforces the following rules on components:
* No applications that share a component can require different versions of any of the resources (files, Registry keys, etc.) included in that component. This is another way of saying that...
Go to the Wise site and download all the merge modules available from http://www.wise.com/CustomerPortal/(zvtbhaeueq3ohn453aprkrrp)/Portal_DownloadFile.aspx?url=http://209.104.132.210/retail/PackageStudio/WPSModules.exe&fileID=28&desc=Wise%20Package%20Studio and put them in C:\Program...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.