WSP 7 - Visio

Posted on 2009-05-04
Last Modified: 2013-11-14

I am attempting to repackage Visio 2K7 for deployment (Using Wise Packaging Studio 7). What we are looking for is a very basic installation.

While attempting to get a usable MSI or Wise Script I keep getting a Wise32.exe error when completing the capture process. Please see the attachement. While messaging the data for the completion process I have remove all the *.\installer\* entries from the registry. Is this wrong?

Also, we have attempted to use Altiris RapidInstall.exe to capture the image. While this process compeletes and deploys without error...Visio 2007 is not usable ... that is we get "The application failed to initialize properly 0xc0150002" ... which points to VISLIB.DLL not getting loaded.

In any case, any help or pointers towards getting an MSI or WiseScript to successfully capture would be helpful.

Thank you,


Question by:Naerwen
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2

Author Comment

ID: 24295628
Also, please note, this is on a base imaged pc ... not software (short of Sophos AV) is installed. The machine is up to XP SP 3.
Please let me know if you will need any other information regarding the PC.
LVL 40

Accepted Solution

Vadim Rapp earned 500 total points
ID: 24301291
There's not much advise can be given. If capture is crashing on particular scenario, the only way is to try to vary this or that and see what happens. Yes, removing Installer entries is right, actually this is one thing that you should configure in SetupCapture Configuration, among others.

If Visio installation is MSI-based, maybe there's no need to repackage it? maybe you could instead create a transform with whatever specifics you have? or even better, you can use Office Customization Tool,
LVL 13

Expert Comment

ID: 24303191
Not for points, just for clarification.  Vadimrapp1 is right, don't repackage an MSI - expecially Office.  When your repackage it, it's going to get a new GUID, which means that when patches are released, they're not going to work.  When a new version of Office comes out, you wont be able to (easily) upgrade.

You wont be able to create MSTs for Office, use the OCT that the previous poster linked to.
How Do You Stack Up Against Your Peers?

With today’s modern enterprise so dependent on digital infrastructures, the impact of major incidents has increased dramatically. Grab the report now to gain insight into how your organization ranks against your peers and learn best-in-class strategies to resolve incidents.


Author Comment

ID: 24306682
Vadimrapp1, usachrisk1983,
    doing a dry run with the OCT. I had looked at it before but didn't try it.
Thanks for the direction. Will let you know asap how it went.
LVL 40

Expert Comment

by:Vadim Rapp
ID: 24306975
some comments - not really to argue, just observations.

"don't repackage an MSI"

some MSI's are so badly authored that repackaging them actually improves. Adobe Reader is great example.

Usually this is the reason of the original installation authors' trying to be "smarter than Installer". They think their application is oh so special that usual rules and standards of course don't apply, so they begin writing ton of custom actions, write registry values directly instead of regular COM registration, destroying resiliency and advertising along the route, and so forth. Another reason is being simply unfamiliar with MSI authoring to begin with - it's known effect that when you are beginner in the area, you immediately discover that this is not implemented, and that is stupid; later, once you become more proficient, you realize that of course it's all taken care of, only not as you expected at once. But I'd imagine, installations are often made by developers for whom installations are not their main speciality, so they grab Installshield, run the wizard, then write custom actions for everything the wizard has missed.

The main problem with all this is that Installer naively handles big number of various scenarios of deployment - roaming, per-user, per-machine, advertising, managed, and so forth - while these authors only consider one-two most usual scenarios of the straightforward installation. As the result, the installation becomes uninstallable and so forth, and soon the original vendor is creating his own "cleanup utility" that is supposed to clean the mess left after the installation. There's Nero cleanup utility, and NVidia cleanup utility, and of course Microsoft who writes big articles in their KB "How to uninstall (yet another product)". In fact, every such article and every such utility is a sign of badly authored original installation.

And when we are dealing with such an installation, repackaging it actually improves - provided of course that in the resulting installation the standards are observed, and the ICE validation passes.

> You wont be able to create MSTs for Office

With the right authoring tool, MST can be created for any MSI. Though, because of the above-said considerations, it's possible that it won't work as expected if standard actions (handled by the MST) in the original MSI were then overridden by custom actions (not handled by the MST).

Author Comment

ID: 24314838
     Your suggestion of using the OCT was correct. I was able to use it and create a custome installation for my end users. However, there was one last thing that I could not get rid of and that was the prompts to use "Microsoft Updates for Office" and one other I cannot think of at the moment. So....kudos to for that. However, that was not satisfactory for the administration and as such I was pressured to make either WPS 7 or RapidInstall Rip work. I had to go with the latter because WPS 7 simply fails to execute a capture(Likely due to me being a novice to repackaging technologies). That said, I was successful in capturing a solid install with RapidInstall from Altiris.
I would like to point out one thing regarding OCT vs. a RIP. The OCT was better in that it has less overhead interms of the need for drive space during deployment. The OCT solution consumed @ 280MB on the server. Said 280mb MUST be copied to the client machine for deployment ... using Altiris, that is. The RapidInstall RIP is a 550mb .exe that also must be copied to the client to complete the install. I would prefer the former simply because it reduces a few factors in terms of overhead ... space and bandwidth.
I am awarding you the points.
Thank you for your help. I truly appreciate it.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Windows 10 8 68
deploy workstation 4 102
hp envy 4500 driver installation problem 5 78
load fans on Dell Precision R410 3 51
One of the frequent problems with the installations is when some file or registry entry is not removed from the system upon un-installation of the product. Clean removal is always highly desirable. One major reason for that is badly authored inst…
With User Account Control (UAC) enabled in Windows 7, one needs to open an elevated Command Prompt in order to run scripts under administrative privileges. Although the elevated Command Prompt accomplishes the task, the question How to run as script…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question