Could not open output file c:\wise share point\projects\<projectname>\wsi12c8.tmp
Hi there, not sure if anyone has come across this issue before?
I am trying to create a package for the installation of an excel add-in (Analysis tool-pak), i have created a
setup capture for first use settings, once the initial capture is made, i then install excel add-in by opening up excel and navigateing to tools > add-ins > and checking the analysis toolpak add-in. Once the install completes then, i complete the capture in wise but receive the following error before the capture creates the project msi file
Could not open output file c:\wise share point\projects\<projectname>\wsi12c8.tmp ??
Anyone with any ideas??
I am trying to create a package for the installation of an excel add-in (Analysis tool-pak), i have created a
setup capture for first use settings, once the initial capture is made, i then install excel add-in by opening up excel and navigateing to tools > add-ins > and checking the analysis toolpak add-in. Once the install completes then, i complete the capture in wise but receive the following error before the capture creates the project msi file
Could not open output file c:\wise share point\projects\<projectname>\wsi12c8.tmp ??
Anyone with any ideas??
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Capturing Excel add-ins isn't a good idea. This is because the capture will record the registry settings "as is" (unsurprisingly).
Add-ins are recorded in a sequence of "OPEN" values (i.e. the first will be "OPEN" with the value's data set to the add-in's location, the second as "OPEN1" with the data set to that add-in's location and so on. Thus, if you produce an MSI with those settings, installation will overwrite and existing setting the user may have.
Search AppDeploy for "add-in". You'll turn up a couple of scripts which you can use as Custom Actions in your package. They use Excel Automation to add the add-in.
As for the error message you're seeing, who knows? Clearly the temporary file is no longer present. Did you reboot before completing the capture? If so, do you by any chance have a start-up task to remove TMP files?
Add-ins are recorded in a sequence of "OPEN" values (i.e. the first will be "OPEN" with the value's data set to the add-in's location, the second as "OPEN1" with the data set to that add-in's location and so on. Thus, if you produce an MSI with those settings, installation will overwrite and existing setting the user may have.
Search AppDeploy for "add-in". You'll turn up a couple of scripts which you can use as Custom Actions in your package. They use Excel Automation to add the add-in.
As for the error message you're seeing, who knows? Clearly the temporary file is no longer present. Did you reboot before completing the capture? If so, do you by any chance have a start-up task to remove TMP files?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
