'The parameter is incorrect' error message on Installation Folder screen

[Steve_K]

One of our customers gets an

'The parameter is incorrect' error message when he clicks the 'Next' button on the 'Installation Folder' screen. The installation folder is set to the default "c:\Program Files\[Product Name]\" folder. We have not changed any code of the 'On Next' action.

Any idea? See attached screen shot.

[jassing]

One of our customers gets an

'The parameter is incorrect' error message when he clicks the 'Next' button on the 'Installation Folder' screen. The installation folder is set to the default "c:\Program Files\[Product Name]\" folder. We have not changed any code of the 'On Next' action.

Any idea? See attached screen shot.

does the system HAVE a C: drive?

[Steve_K]

Yep. C drive is there.

[jassing]

Rats, becuase I see that on suf installers that insist on C: (my boot drive is E: and there is no C

Next idea, is there any chance this user is installing from a network share or mapped drive?

[jcuster]

Rats, becuase I see that on suf installers that insist on C: (my boot drive is E: and there is no C

Next idea, is there any chance this user is installing from a network share or mapped drive?

At the risk of should starting a new thread, What have you seen with SUF installers requiring C:?

I have a SUF installer which ran flawlessly for over a year, our Network team upgraded the Network to Nevell OES (SUSE linux 10 SP2.) Now when the installer runs The network revokes rights to the user's Home Directory H:.

[Steve_K]

Next idea, is there any chance this user is installing from a network share or mapped drive?

I have to ask first. Dunno. Will reply as soon as I know.

I have also opened a support ticket with IR, but they do not seem to be able to help at the moment as I could not provide a setup log file yesterday. Have now sent them the log file, but as far as I can tell, it won't help much. Nothing in there that points into (any helpful) direction. The last line of the setup log file just logged the exit of the setup, and all previous lines do not show anything that might be related to the error:

[07/14/2009 21:03:45] Notice Exit setup process (Return code: 5)

Dunno what return code 5 means, though ... have to check that right now.

[jassing]

At the risk of should starting a new thread, What have you seen with SUF installers requiring C:?

That they don't work... various errors that change depending on when the installer attempts to access the non existant drive.

NOTE: Most installers properly use %ProgramFilesFolder% to fetch the system defined place -- which is not always a C drive.

I have a SUF installer which ran flawlessly for over a year, our Network team upgraded the Network to Nevell OES (SUSE linux 10 SP2.) Now when the installer runs The network revokes rights to the user's Home Directory H:.

I have seen mappings get hosed (files locked, even when they are no longer being used), the SUF installer generating errors about corrupted archives, the suf installer generating errors that indicate a rights issue, ....

IR has been unable to replicate the issues... I offered access to my machine so they could experience / debug it -- but the devs said they couldn't fix anything unless they could replicate it in house.. :(

Currious tho when you run and the network revokes rights -- is the installer being run from a mapped (novell) drive? what happens if you copy the file locally and run? If that doesn't hose the network rights; this would be inline with my experiences....

[jassing]

[07/14/2009 21:03:45] Notice Exit setup process (Return code: 5)

Dunno what return code 5 means, though ... have to check that right now.

exit code 5 means the user canceled the install.

[Steve_K]

OK, the setup file is not located on a network share, or on a mapped drive. It's on the user's desktop.

[jassing]

I'm out of ideas, at this point, I'd open a support ticket....

[jcuster]

That they don't work... various errors that change depending on when the installer attempts to access the non existant drive.

NOTE: Most installers properly use %ProgramFilesFolder% to fetch the system defined place -- which is not always a C drive.



I have seen mappings get hosed (files locked, even when they are no longer being used), the SUF installer generating errors about corrupted archives, the suf installer generating errors that indicate a rights issue, ....

IR has been unable to replicate the issues... I offered access to my machine so they could experience / debug it -- but the devs said they couldn't fix anything unless they could replicate it in house.. :(

Currious tho when you run and the network revokes rights -- is the installer being run from a mapped (novell) drive? what happens if you copy the file locally and run? If that doesn't hose the network rights; this would be inline with my experiences....

The Installer Hoses the User's H: drive from any place it is ran.

The installer Copies Files specifically from the User's Local PC to their H: To get around the issue I've written another SUF installer which does work to delete the existing folders where the offending SUF installer tries to write to.

When there is nothing there it works. when there is something there it doesn't.