shawnnason
Programmer
I tried to ask this in Application Deployment forum, with no result. so, I am cross-posting here, hoping for some help...
When I use the Package and Deployment Wizard to create a package, I am getting an error. When I install the package and setup.exe is run on the target machine, I get the following three msgboxes:
Invalid command line parameters. Unable to continue
---
Setup was not completed successfully.
---
Runtime error '5':
Invalid procedure call or arguement.
I am able to run the actual executable without trouble, and a customer was also able to run the executable.
I looked on the Microsoft websitre and saw where it said that if the path name included spaces or dashes, these would be interpreted as command line arguments, so I checked and there were indeed spaces in the path. So, I changed both where the package was created and installed so that there were no spaces, but I still get the error. Are there other things that can cause this behavior?
- Shawn
When I use the Package and Deployment Wizard to create a package, I am getting an error. When I install the package and setup.exe is run on the target machine, I get the following three msgboxes:
Invalid command line parameters. Unable to continue
---
Setup was not completed successfully.
---
Runtime error '5':
Invalid procedure call or arguement.
I am able to run the actual executable without trouble, and a customer was also able to run the executable.
I looked on the Microsoft websitre and saw where it said that if the path name included spaces or dashes, these would be interpreted as command line arguments, so I checked and there were indeed spaces in the path. So, I changed both where the package was created and installed so that there were no spaces, but I still get the error. Are there other things that can cause this behavior?
- Shawn
