Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

"The Parameter is incorrect" error when running virtualized Office XP, 2003 and Visio 2003

Updated: 29 Jul 2010 | 18 comments
tjwest's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

When double clicking on a .doc, .xls, or .ppt file on a workstation with a Microsoft Office XP layer, the application does not open.  If I right click on the file and choose Open With....(the Office layer), I receive the "The Parameter is incorrect" error.  I can open the applications by clicking on the shortcut, but sometimes I receive an error that some Speech Recognition files cannot be loaded because of error 87....The parameter is incorrect.  I have tried using Single Program and Global Capture to package these three applications.  Has anyone else encountered this issue?  I can provide a vsa file if anyone wants to take a look.

Comments

Jordan's picture
04
Jun
2009
0 Votes 0
Login to vote

We don't test against office

We don't test against office XP (only 2003 and 2007).  That being said can you tell me what SVS version and what OS you were doing these captures on?

If a forum post solves your problem please flag is as the solution

tjwest's picture
04
Jun
2009
0 Votes 0
Login to vote

This was happening on Office 2003 Standard as well.....

SVS Version: 2.0.1407
Capture PC running Windows XP (clean machine)

Thanks for your quick response to this.  I even tried doing a complete install of Office 2003....still got the same error.

Jordan's picture
04
Jun
2009
1 Vote +1
Login to vote

1407?  wow.  You're about 3

1407?  wow.  You're about 3 years behind on SVS updates, actually I think that was the very first release of SVS, the current release is 2.1.3071 so go get an update from https://kb.altiris.com/article.asp?article=46118&p=1

If a forum post solves your problem please flag is as the solution

philbenson's picture
05
Jun
2009
0 Votes 0
Login to vote

Did you turn

off advertised shortcuts when capturing the application? If you did not, and then got rid of all of the Windows Installer registry / DB information, that that is a common error that occurs.

Cheers
Phil

tjwest's picture
05
Jun
2009
0 Votes 0
Login to vote

Back in time....

Yeah....after I posted the version I went searching for updates.  I will be out of the "Stone Age" of SVS agents once I push the new version down........LOL

Phil.......I did not turn off advertised shortcuts, but I did not remove anything from the capture, either.  I will try turning off adv shortcuts and repost on the success/failure.

Thanks for all of your help, guys....I really appreciate your quick responses.

tjwest's picture
05
Jun
2009
0 Votes 0
Login to vote

Some improvement....

After updating the SV agent on the capture and test machine and recapturing Office 2003 (Global) with the DISABLEADVTSHORTCUTS=1 command, I don't receive the error about the speech recognition files.  Still, however, when I create a Word doc, if I try to open the file I get the folowing error:

"C:\(Path to file)\File.doc"
The parameter is incorrect.

Is there anything else I should be doing to the package during or after capture?

Thanks sooooo much in advance......

Jordan's picture
05
Jun
2009
1 Vote +1
Login to vote

I wouldn't use global

I wouldn't use global capture, that's kind of a last resort feature, and try single capture.  You don't need to disable advertised shortcuts unless you're wanting to stream the package with SWS.

However I don't think global capture causing your problem, I can't ever remember hitting this problem, unless you have something else running that getting caught in the layer that's causing problems--like speach recognition software.

Also what else is installed on the machine in terms of AV or other security software (I know you said it was clean but some people consider this part of a clean image)? 

If a forum post solves your problem please flag is as the solution

philbenson's picture
07
Jun
2009
1 Vote +1
Login to vote

DISABLEADVTSHORTCUTS=1

Hi Jordan
regardless of using streaming or standalone, we ALWAYS use non advertised shortcuts. I know it's a question of "taste" but we also remove "ALL" traces of MSI technology from any VSA packages.

@tjwest
Have a look at the fle associations etc. more specifically the parameters passed (as the error suggests). What you could also do is have a look for a "recept" that ErikW posted on the old juice site for packaging Office as a VSA.

Cheers
Phil

tjwest's picture
08
Jun
2009
0 Votes 0
Login to vote

Update

Hey Jordan,

There is no AV software installed on the machine.  The only thing really installed is the Windows XP OS with SP2 and the video and NIC driver for the system.  I have disabled the speech recognition files from the package, but I don't know what could be causing the other error.  I started using global capture because I am out of ideas.

Phil,

I'm not quite sure what you mean by looking at the parameters passed (please clarify if you can), but I will look at the file extensions captured from the registry and see if I can figure it out.  Oh....and how do I get to the old juice site?  I never really went there, but I will try to look here to see what ErikW has posted in the past.

Thanks again....I REALLY appreciate your help on this.

tjwest's picture
08
Jun
2009
0 Votes 0
Login to vote

Yet another update....

I have discovered that after running a repair on Office (using the command in the uninstall key since there is no repair button) allows me to open doc files with no errors.  This does not seem like the correct way to fix the issue, however.  What would the repair be doing that was not already captured in the original package?

-Totally Stumped 

philbenson's picture
09
Jun
2009
1 Vote +1
Login to vote

OK,

after reading your last post, I'll ask this. Did you start the run all the shortcuts "DURING" the capture process? This sounds as if user specific information (obviously affecting the shorcuts) was not initially captured.

When capturing applications into a VSA layer, always run all of the (relevant) shorcuts. It also makes sense to "play around" with the application(s), as they normally save information (in a config file, or in th registry).

Cheers
Phil

btw, did you find the article written by ErkiW?

phil

tjwest's picture
09
Jun
2009
0 Votes 0
Login to vote

Indeed.....

During the Global Capture, I double clicked every shortcut on the desktop (Word, Excel, Powerpoint) and in the Start > Programs menu to ensure anything that needed to be captured was captured.  Something is getting missed....I'm just not sure how to get it. 

Some additional questions:  Should the install files for Office be on the capture PC, or does it matter?  Could there be something in Wise Package Studio (as opposed to SVS Admin) that could be causing this problem?

I did not see ErikW's article on packaging Office as a VSA.....though I did search through some of his more recent posts..........seems like a pretty knowledgeable fellow.   ;-)

Thanks again for your help, Phil...........if you have any ideas or suggestions, just let me know........I'm trying to be as much of a spounge as I can.   ;-)

-TJ

philbenson's picture
09
Jun
2009
1 Vote +1
Login to vote

As you are using

Wise Package Studio, it could be that your exclusion list is automatically removing all MSI specific information (which is best proactice anyway IMO).

The source files do not have to be on the PC on which you are capturing, so I do not think that is a problem.
If you can, use WPS over the Admin tool.

It might be prerequisites. I know that SVS "stumbles" over certain prerequisites (.NET, some assemblies) but perhaps Jordan could provide more info on that one.

Other than that, what I suggest is that when you force the self repair, (only do it for missing files or user specific information), and then have a look in the event viewer, you will see (eventually) which components are getting repaired, and then using the Windows Installer Editor, you could have a look which files / registry keys are present in the comßponents which are getting repaired.

Cheers
Phil

Jordan's picture
10
Jun
2009
0 Votes 0
Login to vote

There are certain things we

There are certain things we don't support like transactions or junction points and it depends on what the prereq is will determine the issue.

Sometimes, like if transactions are being used, the install goes to the base instead of the layer, others, like .Net, will fail out and not install at all.

However none of these are an issue with Office 2003 (or 2007) as SVS will capture it just fine.

If a forum post solves your problem please flag is as the solution

tjwest's picture
09
Jun
2009
2 Votes +2
Login to vote

I think it is fixed.....

I had nowhere else to turn, so I started looking at Wise Package Studio as being the problem.  I thought I had done it previously, but apparently I had never installed SP3.  I didn't do anything different during the capture process, except use the internal process for creating a .vsa, and now I can open office files when the layer is imported into a test pc.  I am still using global capture, clicking all shortcuts, and even opening office files before I complete the capture, but I think I will try single program capture to see if global capture is necessary.  Thanks again for your help Phil and Jordan!  If you have any advice, just let me know.

-TJ

Jordan's picture
10
Jun
2009
0 Votes 0
Login to vote

Wise creates VSAs in a

Wise creates VSAs in a different manner the SVS\SWV. 

We place a layer in capture mode and run the installer so it all the changes get made inside the layer.

Wise does something with the MSI and copies information (more or less) into the layer without using SVS's capture API.

There are two completely different methods and you can possibly have two layers that are different made from the same MSI.

If a forum post solves your problem please flag is as the solution

tjwest's picture
10
Jun
2009
0 Votes 0
Login to vote

Wise vs. SVS....

So which is better?  Does Wise's ability to have certain files and registry entries automatically excluded from the capture make it productive?

Jordan's picture
11
Jun
2009
0 Votes 0
Login to vote

I'm biased towards SVS since

I'm biased towards SVS since it's the product I work on so I'm really not the one to ask.  All I can really say is use the tool that makes you more productive.

If a forum post solves your problem please flag is as the solution